Docs
Configuration
TRW works with sensible defaults, but one setting matters more than any other on modern installs: target_platforms. That list tells TRW which client targets to record for this repo. Dedicated integrations write native client surfaces where the installer provides them; retired identifiers such as Aider are rejected rather than recorded as configuration targets.
Common config changes
Target more than one client
List every selected client under target_platforms. TRW writes each one’s native files and automation; which surfaces appear differs by client.
Record the checks your project actually runs
Run tests, builds, lint, and type checks with project-native commands first. Then pass their scope, counts, failures, and static-check state to trw_build_check.
Connect to the hosted platform only when you want to
Platform sync is optional. Local runs, checkpoints, and learnings work without it. Add platform_url only when needed and supply the key through TRW_PLATFORM_API_KEY or .trw/credentials.yaml.
Client profiles
The installer selects these profiles for you, but you can always edit target_platforms later. Every current profile has a dedicated integration, but the mix of native files and automation differs per client. The matrix also lists the retired Aider identifier, which current installs reject.
| Client | Support shape | What TRW writes | Support notes | Common workflow |
|---|---|---|---|---|
Claude Code End-to-end TRW integration for local CLI workflows that lean on hooks and durable instructions. | Hooks & agents | CLAUDE.md, .claude/INSTRUCTIONS.md, .claude/hooks/, .mcp.json | Hooks, skills, MCP config, and portable workstream guidance | Local CLI workflows that want repo-native hooks, agents, and guidance |
Cursor IDE TRW translated into Cursor’s IDE rules, hooks, MCP config, and editor-first automation. | IDE-native | .cursor/rules/, .cursor/mcp.json, .cursor/hooks/, .cursor/skills/ | IDE rules plus translated hooks, commands, skills, and subagents | Interactive editor-first workflows inside Cursor |
Cursor CLI TRW adapted for headless Cursor runs where explicit permissions and CLI-safe defaults matter. | Headless-safe | AGENTS.md, .cursor/cli.json, .cursor/hooks.json, .cursor/mcp.json | Headless-safe permissions and CLI hook subset | cursor-agent, CI, and scripted terminal workflows |
OpenCode TRW translated into OpenCode’s instruction, command, and agent surfaces. | Command-first | opencode.json, .opencode/INSTRUCTIONS.md, .opencode/commands/, .opencode/agents/ | Curated commands, agents, and instruction-first guidance | Terminal workflows built around commands and repo-local instructions |
Codex CLI TRW adapted to Codex’s workflow and context constraints without changing the core loop. | Codex-native | .codex/config.toml, .codex/INSTRUCTIONS.md, .codex/agents/, optional .codex/hooks.json | Codex-specific config, agents, curated skills, optional hooks | Codex sessions that want tighter context control and repo-local guidance |
GitHub Copilot CLI TRW translated into GitHub-native repo instructions, hooks, and agent surfaces. | GitHub-native | .mcp.json, .github/copilot-instructions.md, .github/instructions/, .github/hooks/, .github/agents/ | Project MCP config, repo instructions, path-scoped guidance, hooks, agents, and skills | GitHub-native repos adopting agent workflows and path-scoped guidance |
Antigravity CLI TRW writes Antigravity-native instructions, MCP registration, subagents, and supported hooks. | Antigravity-native | ANTIGRAVITY.md, .agents/rules/, .agents/agents/, ~/.gemini/config/mcp_config.json, .antigravitycli/hooks.json | Native instructions, MCP config, subagents, and supported before-tool hooks | New Google CLI workflows that need large context and native agent surfaces |
Grok Build CLI TRW registers its MCP server in the project Grok config and writes the shared AGENTS.md guidance. Start grok from the project root and trust the folder in grok so it runs the project-local server. | Grok-native | .grok/config.toml, AGENTS.md | Project MCP registration and the shared AGENTS.md ceremony block; hooks off | Grok Build CLI sessions that want TRW tools through a project-local MCP server |
Aider The Aider target was retired because it never had a native adapter. Current installation rejects the identifier. | Retired; manual only | Legacy identifier retained for cleanup; no Aider-native file is generated | No dedicated Aider integration; use explicit local CLI operations | Existing manual workflows that do not select Aider during TRW initialization |
Claude Code
End-to-end TRW integration for local CLI workflows that lean on hooks and durable instructions.
Cursor IDE
TRW translated into Cursor’s IDE rules, hooks, MCP config, and editor-first automation.
Cursor CLI
TRW adapted for headless Cursor runs where explicit permissions and CLI-safe defaults matter.
OpenCode
TRW translated into OpenCode’s instruction, command, and agent surfaces.
Codex CLI
TRW adapted to Codex’s workflow and context constraints without changing the core loop.
GitHub Copilot CLI
TRW translated into GitHub-native repo instructions, hooks, and agent surfaces.
Antigravity CLI
TRW writes Antigravity-native instructions, MCP registration, subagents, and supported hooks.
Grok Build CLI
TRW registers its MCP server in the project Grok config and writes the shared AGENTS.md guidance. Start grok from the project root and trust the folder in grok so it runs the project-local server.
Aider
The Aider target was retired because it never had a native adapter. Current installation rejects the identifier.
Example config
task_root: docs
runs_root: .trw/runs
build_check_coverage_min: 90.0
target_platforms:
- "cursor-ide"
- "codex"
- "antigravity-cli"
platform_url: "https://api.trwframework.com"
platform_telemetry_enabled: falseThe installer rewrites this file carefully. If you re-run install after choosing a new client mix, TRW updates target_platforms without clobbering the rest of your repo-local configuration.
Need a field reference?
This page covers common choices. For field types, defaults, nested settings, and environment overrides, use the complete configuration schema.
Next: tools and troubleshooting
Once configuration feels clear, learn which tools the runtime actually calls and how to debug client-specific setup issues.