Journey

A closer look at Journey

Journey is the free, open registry of tested agent workflows, where users browse kits, install them into an AI coding agent, and give the agent new capabilities instantly.

Editorial guidance based on published documentation. The workflow below is a suggested starting point, not a measured product result.

When to choose Journey

• AI coding agent users who want to install entire tested workflows instantly and give an agent new capabilities.
• Teams that want a free, open registry of reusable agent workflows, with kits for briefings, wikis, journals, and earnings previews.
• Developers who want to browse kits, use the CLI, API docs, or MCP server, and install kits globally with npm.

When to choose something else

• Users who have no AI coding agent, since kits are installed into Claude Code, Cursor, OpenClaw, Codex, Hermes, or another AI coding agent.
• Users who expect Journey itself to run workflows without an agent, since Journey is the registry where agents discover and install entire workflows.
• Users who need every kit to be easy to set up, since featured kits are labelled Easy or Moderate setup in the text read.

A practical starting workflow

1. Browse kits in the registry, such as a daily brief, personal knowledge wiki, food journal, or weekly earnings preview.
2. Install Journey with npm or paste the install prompt into an AI coding agent, or add the MCP server to an agent config.
3. Install a kit and let the agent use the whole workflow, with every kit scanned for malware and prompt injection before publication.

Check before committing

• No plan amounts appear in the text read, since the guessed pricing and FAQ paths return 404 pages, so no charge fact is recorded; the homepage states the registry is free for everyone, without a $0 figure, so no free fact is recorded.
• Kit setup difficulty varies: featured kits are labelled Easy or Moderate setup in the text read, so not every kit is one-click.

Common questions

Compare approaches for this task

• AIOProductOS — Product teams that want to build what pays, since the platform ties each customer record to feedback, revenue, work and code.; Companies that need enterprise controls, since the pricing page highlights EU and US data residency, BYOK encryption, SAML/SSO on Pro and 150+ compliance controls.
• AISOAP — Clinicians who spend too long on documentation, since AISOAP records, transcribes and generates SOAP notes from the visit conversation.; Clinics that need team controls, since multi-person plans add team management, template creation and an organisation-wide BAA.