journey

Documentation

Connect Journey to your coding agent.

Install one CLI, initialize the repository, and let structured MCP tools preserve the engineering moments worth revisiting.

Get started

Journey configures a project-local MCP connection and adds concise instructions that tell your coding agent when an event is meaningful enough to record.

1. Install the CLI

npm install -g @tryjourney/cli

2. Initialize your repository

cd your-project
journey init

Choose Codex or Claude Code when prompted. Re-running journey init safely updates Journey-owned configuration while preserving unrelated project settings.

Current hosted boundary: the repository includes the CLI, API, and MCP implementation. Hosted authentication and publishing are still being completed.

What gets recorded

Your agent calls a focused tool only when the event adds durable engineering context:

  • Decision: a meaningful choice between alternatives, including context and reasoning.
  • Problem: a blocker or failure that changes the implementation path.
  • Resolution: the way a recorded problem was solved, linked to the original event.

Routine edits, every command, and autonomous implementation details do not belong in the trail.

Supported agents

Codex

Journey adds an MCP server entry to .codex/config.toml and a marked instruction block to AGENTS.md.

Claude Code

Journey adds an MCP server entry to .mcp.json and a marked instruction block to CLAUDE.md.

Privacy model

Journey stores structured events, not the underlying conversation. It preserves explicit provenance and does not invent a developer's reasoning when an approach originated with an agent.

For the broader product model, read about Journey or review the privacy policy.