Client boundary guide
Use Aider alongside TRW
Keep Aider as the editing loop and use TRW through explicit terminal operations or a separately supported MCP client. The retired Aider identifier is not selectable and there is no native Aider bridge.
Current support
Profile support is not tool integration
Earlier versions of this page promised generated Aider instructions, automatic startup loading, and direct trw_* calls. The current bootstrap source does not implement those surfaces.
Retired (2026-07-11)
Selectable profile
The aider profile was retired — the installer no longer accepts --ide aider, and prior configs carrying it are dropped with a notice on update.
Not implemented
Aider-native writer
TRW does not currently generate .aider.conf.yml or an Aider conventions file.
Not wired to Aider
TRW MCP registration
The generic .mcp.json scaffold is not an Aider registration surface.
Honest setup
Initialize TRW, then choose the handoff
- Install TRW using the normal package or guided installer path for your environment.
- From the repository root, run
trw-mcp init-project .. Do not pass the retired--ide aidervalue; choose an active client profile only when that client will consume the generated integration. - Decide whether TRW operations will happen through
trw-mcp localin a terminal or through a separate client with a dedicated MCP registration. - Review generated files before committing. Do not treat generic Claude-compatible scaffolding as proof of Aider integration.
Working model
Two explicit lanes
Lane A / Aider
Edit and test
- Give Aider only the files and context needed for the task.
- Review diffs and run project-native validation.
- Keep commits scoped when the worktree is shared.
Lane B / TRW terminal
Persist explicit state
- Start or inspect a local fallback run.
- Checkpoint milestones and record durable learnings.
- Close the fallback run after validation and review.
Local fallback
Commands you can actually run
These are operator-run commands, not hidden Aider tool calls. Confirm exact flags with trw-mcp local --help in the installed version.
01 / Start a run
trw-mcp local init --task "review-auth-flow"02 / Inspect it
trw-mcp local status03 / Checkpoint
trw-mcp local checkpoint -m "tests passing; review pending"04 / Record a learning
trw-mcp local learn --summary "Auth fixtures require UTC" --detail "Use timezone-aware timestamps."05 / Close the fallback run
trw-mcp local deliver -m "Aider edits reviewed and validated"Decision point
Use another profile when automation matters
Aider remains a fit
You want a focused terminal editor and are comfortable operating TRW explicitly in a second terminal or handing memory work to another client.
Choose a dedicated client
You need direct MCP tool calls, generated native instructions, client-specific hooks, or translated agents and skills inside the same session.