Skip to main content
TRW
TRWQuickstart

Docs

Quickstart

Review the current access flow, run the installer, choose your client surfaces, verify the setup, and start your first retained-context workflow. The goal is simple: wire the repo once, then let every later session inherit better context than the last one had.

Access status. TRW installs are currently approved through a gated beta. If you are still evaluating fit, read this page first. If you already know you want to try it, request access on the waitlist.

Fast path

Step 1

Request or confirm access

Current installs roll out through a gated beta. Approved users can authenticate during install or reuse an existing API key.

Step 2

Run the bootstrap

The shell bootstrap installs trw-mcp, downloads the full Python installer, and starts guided setup in your project root.

Step 3

Select your client surfaces

On first install, the Python installer now prompts you with a multi-select TUI so one repo can be wired for multiple clients at once.

Step 4

Verify and start

Confirm the generated files, open one configured client, call trw_session_start(), and finish with trw_deliver().

Prerequisites

RequirementVersionInstallVerify
Python3.10+ (3.11+ recommended)brew install python / apt install python3python3 --version
pip22.0+python3 -m pip install --upgrade pippython3 -m pip --version
git2.30+brew install git / apt install gitgit --version
AI coding clientlatest stable available to youClaude Code, Cursor IDE, Cursor CLI, OpenCode, Codex CLI, GitHub Copilot CLI, Gemini CLI, or AiderRun your client’s version command or open the repo in the client you plan to use

Installation

Run the bootstrap from the project root after approval or with an existing API key. The shell bootstrap installs trw-mcp, authenticates if needed, downloads the full Python installer, and writes the repo-local config automatically.

shell bootstrap
curl -fsSL https://trwframework.com/install.sh | bash

On first install, the Python installer now opens a guided client picker so you can wire this repo for more than one surface in the same pass.

installer client selection
Select the client surfaces you want TRW to configure

[x] Claude Code
[x] Cursor IDE
[ ] Cursor CLI
[ ] OpenCode
[x] Codex CLI
[ ] GitHub Copilot CLI
[ ] Gemini CLI
[ ] Aider

Use ↑/↓ to move • Space to toggle • Enter to confirm

Supported clients

The installer writes different instruction surfaces depending on what you select. Full profiles expose more automation. Light profiles keep the footprint smaller and rely more on instructions plus MCP.

Claude Code

Best-understood end-to-end profile for local, hook-heavy TRW workflows.

Ceremony: Full
What TRW writes: CLAUDE.md, .claude/INSTRUCTIONS.md, .claude/hooks/, .mcp.json
Automation: Deepest local hook, skill, and agent-team surface
Best fit: Users who want the fullest TRW surface in one CLI

Cursor IDE

Full TRW surface tuned for Cursor’s IDE-native rules and automation.

Ceremony: Full
What TRW writes: .cursor/rules/, .cursor/mcp.json, .cursor/hooks/, .cursor/skills/
Automation: IDE rules plus translated hooks, commands, skills, and subagents
Best fit: Interactive editor-first workflows inside Cursor

Cursor CLI

A lighter profile for headless Cursor runs where explicit permissions matter.

Ceremony: Light
What TRW writes: AGENTS.md, .cursor/cli.json, .cursor/hooks.json, .cursor/mcp.json
Automation: Headless-safe permissions and CLI hook subset
Best fit: cursor-agent, CI, and scripted terminal workflows

OpenCode

Instruction-first TRW integration with OpenCode-native commands and agents.

Ceremony: Light
What TRW writes: opencode.json, .opencode/INSTRUCTIONS.md, .opencode/commands/, .opencode/agents/
Automation: Curated commands, agents, and instruction-first guidance
Best fit: Lean terminal workflows with curated TRW surfaces

Codex CLI

A light TRW profile shaped around Codex’s workflow and context constraints.

Ceremony: Light
What TRW writes: .codex/config.toml, .codex/INSTRUCTIONS.md, .codex/agents/, optional .codex/hooks.json
Automation: Codex-specific config, agents, curated skills, optional hooks
Best fit: Codex users who want tighter context and lighter ceremony defaults

GitHub Copilot CLI

Full TRW support translated into Copilot’s GitHub-first surfaces.

Ceremony: Full
What TRW writes: .github/copilot-instructions.md, .github/instructions/, .github/hooks/, .github/agents/
Automation: Repo instructions, path-scoped guidance, hooks, agents, and skills
Best fit: GitHub-native repos adopting agent workflows and path-scoped guidance

Gemini CLI

Full TRW support adapted to Gemini’s native instruction and subagent surfaces.

Ceremony: Full
What TRW writes: GEMINI.md, .gemini/settings.json, .gemini/agents/
Automation: Gemini-native instructions, MCP config, and subagents
Best fit: Very large-context sessions and Gemini-native agent work

Aider

A light TRW profile for users who want compounding context without heavy scaffolding.

Ceremony: Light
What TRW writes: AGENTS.md and .aider/instructions.md-compatible guidance
Automation: Instruction-first, low-ceremony integration
Best fit: Minimal terminal workflows that still need durable project memory

Verification

CheckCommandWhat success looks like
trw-mcp is on PATHwhich trw-mcpReturns a path such as /home/you/.local/bin/trw-mcp
.trw/config.yaml existsls .trw/config.yamlThe repo-local config file exists
Selected target_platforms were writtengrep -n "target_platforms" -A8 .trw/config.yamlShows every client surface you selected during install
At least one client config existsls .claude .cursor .codex .github .gemini AGENTS.md 2>/dev/nullOne or more client-specific files or directories now exist in the repo

Your first session

Start the session

Loads prior learnings and recovers an active run if the work was interrupted.

trw_session_start()

Do the work

Checkpoint whenever you cross a milestone so the session can recover instead of restart.

trw_checkpoint("rate limiter merged, tests next")

Record a discovery

If you learn something the next session should not rediscover, persist it while the context is fresh.

trw_learn(summary="Cursor CLI needs .cursor/cli.json permissions baseline", detail="...")

Close the loop

Verify the work and persist the session state before you leave the task.

trw_build_check(scope="full")
trw_deliver()

Tip

The client surface changes. The TRW core loop does not: trw_session_start() first, trw_build_check() before delivery, and trw_deliver() last.

If something feels off

Need deeper debugging? Head to troubleshooting for client-specific startup issues, install errors, and runtime recovery steps.

Next: learn the model

Once the repo is wired, spend five minutes on the concepts page so the session, run, learning, and ceremony model feels obvious before the first serious task.

Read Core Concepts

Next Step

Quickstart gets TRW into the repo. Lifecycle explains what agents should do from research through delivery once the framework is live.