Skip to main content
TRW
Skip to content
TRWGetting Started

Docs

Install TRW, choose your clients, and start with the workflow that compounds

TRW is the engineering operating layer that sits above your coding client. Install it once, choose the surfaces you actually use, and keep every session grounded in durable project memory, structured execution, and verified delivery.

Read Quickstart Request Access
Tracked PRDs
350+
Repository tests
15000+
Recorded sprints
100+

Read in this order

QuickstartLifecycleRequirementsTools

1-line installer

Run the shell bootstrap first

It is still the fastest path into the gated beta and now sets up more than one client surface in the same repo.

shell bootstrap
curl -fsSL https://trwframework.com/install.sh | bash
  • Downloads the Python installer and authenticates when needed.
  • Lets you select more than one client surface for the repo.
  • Bootstraps the local TRW layer before you open your first session.

Client coverage

One repo can carry more than one client surface

TRW now supports Claude Code, Cursor IDE, Cursor CLI, OpenCode, Codex CLI, GitHub Copilot CLI, Gemini CLI, and Aider. The installer can wire one repo to several of them at once, so you can keep the clients you already rely on aligned from the same project state.

Claude CodeCursor IDECursor CLIOpenCodeCodex CLIGitHub Copilot CLIGemini CLIAider

8 supported clients

Claude Code, Cursor IDE, Cursor CLI, OpenCode, Codex CLI, GitHub Copilot CLI, Gemini CLI, and Aider are supported today.

No client switch required

Adopt TRW in the tools your team already uses instead of changing editors or CLIs just to get the workflow.

One repo can wire several

The installer can configure more than one client surface in the same repository when your workflow spans multiple tools.

32

MCP Tools

What each tool does, when it appears, and the edges that matter in real work.

Browse docs
24

Skills

Repeatable workflows for delivery, PRDs, auditing, review, and sprint operations.

Browse docs
12

Agents

Focused teammates for implementation, research, testing, review, and requirements work.

Browse docs
13

Hooks

Automation surfaces that save progress, gate delivery, and keep workflows honest.

Browse docs

What changes after install

Sessions stop resetting to zero

TRW persists the context you already paid to learn, keeps work inside a defined lifecycle, and records validation instead of asking you to trust narration.

  • Knowledge that compounds

    Session 50 starts with the decisions, fixes, and gotchas that earlier sessions already paid to discover.

  • Right-sized ceremony

    Quick fixes stay fast. High-risk changes get checkpoints, validation, review, and durable handoff.

  • Verification before narration

    TRW treats build results, review gates, and persisted state as the definition of done.

  • Recovery after interruption

    Checkpoints and run state survive context compaction, interrupted sessions, and handoffs.

Without TRW vs With TRW

See how work changes once project state survives the session

Without durable context, every session spends energy reconstructing state. With TRW, the repo keeps the learnings, checkpoints, and validation history in play.

Without TRW
  • Learnings lost every session
  • No checkpoints, rework from scratch
  • Skip tests, ship bugs
  • No quality gates, defects cascade
  • Context evaporates on compaction
With TRW
  • Knowledge compounds across sessions
  • Checkpoints survive interruption
  • Automated validation gates
  • Quality audit before delivery
  • Discoveries persist permanently

Install flow

From request access to first session

  1. 1

    Request access

    TRW currently rolls out through a gated beta. Start with quickstart if you are evaluating fit, or join the waitlist if you want access.

  2. 2

    Run the bootstrap

    The shell bootstrap installs trw-mcp, authenticates if needed, downloads the Python installer, and starts guided setup.

  3. 3

    Select your clients

    First-time installs let you select every client surface you want TRW to configure in this repo, including more than one.

  4. 4

    Start your first session

    Open any configured client, call trw_session_start(), and finish with trw_deliver() so the context keeps compounding.

What gets added to your repo

The local operating layer lands in the repo

  • .trw/config.yaml

    Project-local TRW configuration, including your selected target_platforms.

  • .trw/

    Runs, learnings, analytics, and the local operating layer that survives session boundaries.

  • Client-specific instruction surfaces

    Examples: CLAUDE.md, .cursor/rules/, .codex/INSTRUCTIONS.md, GEMINI.md, or .github/copilot-instructions.md.

Supported clients

TRW supports the clients you already use

You do not need to switch tools to adopt TRW. The installer translates TRW into the instruction, config, hook, and agent surfaces each client actually exposes, whether you wire one client or several into the same repo.

8 profilesNo client switch requiredOne repo can wire several

Claude Code

Hooks & agents

End-to-end TRW integration for local CLI workflows that lean on hooks and durable instructions.

Common workflow
Local CLI workflows that want repo-native hooks, agents, and guidance
Support notes
Hooks, skills, MCP config, and agent-team translation

TRW writes

CLAUDE.md.claude/hooks/.mcp.json

Cursor IDE

IDE-native

TRW translated into Cursor’s IDE rules, hooks, MCP config, and editor-first automation.

Common workflow
Interactive editor-first workflows inside Cursor
Support notes
IDE rules plus translated hooks, commands, skills, and subagents

TRW writes

.cursor/rules/.cursor/hooks/.cursor/mcp.json

Cursor CLI

Headless-safe

TRW adapted for headless Cursor runs where explicit permissions and CLI-safe defaults matter.

Common workflow
cursor-agent, CI, and scripted terminal workflows
Support notes
Headless-safe permissions and CLI hook subset

TRW writes

AGENTS.md.cursor/cli.json.cursor/mcp.json

OpenCode

Command-first

TRW translated into OpenCode’s instruction, command, and agent surfaces.

Common workflow
Terminal workflows built around commands and repo-local instructions
Support notes
Curated commands, agents, and instruction-first guidance

TRW writes

opencode.json.opencode/commands/.opencode/agents/

Codex CLI

Codex-native

TRW adapted to Codex’s workflow and context constraints without changing the core loop.

Common workflow
Codex sessions that want tighter context control and repo-local guidance
Support notes
Codex-specific config, agents, curated skills, optional hooks

TRW writes

.codex/config.toml.codex/INSTRUCTIONS.md.codex/agents/

GitHub Copilot CLI

GitHub-native

TRW translated into GitHub-native repo instructions, hooks, and agent surfaces.

Common workflow
GitHub-native repos adopting agent workflows and path-scoped guidance
Support notes
Repo instructions, path-scoped guidance, hooks, agents, and skills

TRW writes

.github/copilot-instructions.md.github/instructions/.github/agents/

Gemini CLI

Gemini-native

TRW adapted to Gemini’s native instruction, settings, and subagent surfaces.

Common workflow
Very large-context sessions and Gemini-native agent work
Support notes
Gemini-native instructions, MCP config, and subagents

TRW writes

GEMINI.md.gemini/settings.json.gemini/agents/

Aider

Instruction-first

TRW guidance adapted to Aider-compatible instruction surfaces.

Common workflow
Minimal terminal workflows that still need durable project memory
Support notes
Instruction-first guidance with repo-local project context

TRW writes

AGENTS.md.aider/instructions.md

Next stops

Read the docs in the order you will use them

Quickstart gets you in. Concepts explains the model. Configuration and troubleshooting answer the operational questions that usually show up next.

Quickstart

See the installer flow, the verification checklist, and the first-session walkthrough.

Core Concepts

Understand sessions, runs, learnings, ceremony, and the compounding memory loop.

Configuration

Learn how target_platforms, build thresholds, and platform settings actually behave.

Troubleshooting

Fix install issues, MCP connection problems, and client-specific startup failures.

Quickstart