Docs
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 in this order
1-line installer
It is still the fastest path into the gated beta and now sets up more than one client surface in the same repo.
curl -fsSL https://trwframework.com/install.sh | bashClient coverage
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 a terminal workflow, an editor workflow, and a lighter CI-friendly surface aligned from the same project state.
MCP Tools
What each tool does, when it appears, and the edges that matter in real work.
Skills
Repeatable workflows for delivery, PRDs, auditing, review, and sprint operations.
Agents
Focused teammates for implementation, research, testing, review, and requirements work.
Hooks
Automation surfaces that save progress, gate delivery, and keep workflows honest.
What changes after install
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.
Session 50 starts with the decisions, fixes, and gotchas that earlier sessions already paid to discover.
Quick fixes stay fast. High-risk changes get checkpoints, validation, review, and durable handoff.
TRW treats build results, review gates, and persisted state as the definition of done.
Checkpoints and run state survive context compaction, interrupted sessions, and handoffs.
Without TRW vs With TRW
Without durable context, every session spends energy reconstructing state. With TRW, the repo keeps the learnings, checkpoints, and validation history in play.
Install flow
TRW currently rolls out through a gated beta. Start with quickstart if you are evaluating fit, or join the waitlist if you want access.
The shell bootstrap installs trw-mcp, authenticates if needed, downloads the Python installer, and starts guided setup.
First-time installs now let you select every client surface you want TRW to configure in this repo — not just one.
Open any configured client, call trw_session_start(), and finish with trw_deliver() so the context keeps compounding.
What gets added to your 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
Use Full profiles when you want translated hooks, skills, and broader automation. Use Light profiles when you want a smaller surface area, headless-friendly defaults, or a stricter CLI boundary.
Full surface
Use these when you want deeper translation into the client: broader instruction surfaces, richer automation, and the most complete TRW shape.
Best-understood end-to-end profile for local, hook-heavy TRW workflows.
TRW writes
Full TRW surface tuned for Cursor’s IDE-native rules and automation.
TRW writes
Full TRW support translated into Copilot’s GitHub-first surfaces.
TRW writes
Full TRW support adapted to Gemini’s native instruction and subagent surfaces.
TRW writes
Light surface
Use these when you want a smaller footprint, explicit CLI boundaries, or headless-friendly defaults without dropping durable project memory.
A lighter profile for headless Cursor runs where explicit permissions matter.
TRW writes
Instruction-first TRW integration with OpenCode-native commands and agents.
TRW writes
A light TRW profile shaped around Codex’s workflow and context constraints.
TRW writes
A light TRW profile for users who want compounding context without heavy scaffolding.
TRW writes
Next stops
Quickstart gets you in. Concepts explains the model. Configuration and troubleshooting answer the operational questions that usually show up next.
See the installer flow, the verification checklist, and the first-session walkthrough.
Understand sessions, runs, learnings, ceremony, and the compounding memory loop.
Learn how target_platforms, build thresholds, and platform settings actually behave.
Fix install issues, MCP connection problems, and client-specific startup failures.