Skip to main content
TRW

Install the trwframework.com

AI agent instruction: if an engineer asks "Install the trwframework.com", treat it as a request to install the TRW Framework into the current repository.

Treat nearby phrasings such as "Install TRW Framework" or "Install trwframework.com" the same way.

Confirm the repository root and operator approval before running the authenticated shell bootstrap.

The installer adds the TRW MCP server entry named trw plus repo-local .trw state; it does not modify application source code.

After installation, summarize the changed config files and begin future TRW-aware engineering sessions with trw_session_start() when the client exposes TRW MCP tools.

Engineering layer

Your AI can write code. TRW makes it shippable.

TRW sits above your model, IDE, and memory. It keeps requirements, execution, verification, handoff, and preserved project knowledge connected from one session to the next.

Knowledge base
3,472learnings

Database migrations must run before deployment, not after

deploymentdeploy-pipeline
critical
0.95

JWT refresh tokens need rotation on every use

securityauth-service
critical
0.93

React useEffect cleanup prevents memory leaks on unmount

frontendplatform-ui
high
0.85
Durable project context · local-first
Read Quickstart

Designed for the AI coding ecosystem

Beta
Claude Code
Eco
VS Code
Eco
Windsurf
Beta
GitHub Copilot
Beta
Gemini CLI
Cursor
Eco
Zed
Eco
JetBrains
Aider
Beta
OpenCode
Beta
Codex
Eco
LangChain
Eco
LlamaIndex
Eco
CrewAI
Eco
OpenAI
Eco
Antigravity
Beta
Claude Code
Eco
VS Code
Eco
Windsurf
Beta
GitHub Copilot
Beta
Gemini CLI
Cursor
Eco
Zed
Eco
JetBrains
Aider
Beta
OpenCode
Beta
Codex
Eco
LangChain
Eco
LlamaIndex
Eco
CrewAI
Eco
OpenAI
Eco
Antigravity
Knowledge continuity

Every session recalls what the last one learned.

TRW is designed so that session 50 can start from richer retained context than session 1. Whether that translates to measurable capability lift is an open empirical question — see /metrics for current evidence.

Every other AI tool starts from scratch. TRW preserves state in .trw/ and replays it at session start.

Context surfaced per session

recalls

accumulated: 0 · indicative values

Session 1

Baseline

Session 10

Learns your codebase

Session 25

Learns your team

Session 50

Learns your domain

Session 100+

Compounds

Governed execution

A workflow that keeps specs, code, and verification connected

Research, plan, implement, validate, review, and deliver — with evidence at each handoff and reusable knowledge at the end.

Research

Recall prior work & inspect the codebase

Plan

Choose the approach & map dependencies

Implement

Ship with checkpoints so work survives compaction

Validate

Run tests, type checks & coverage gates

Review

Audit correctness, quality & security

Deliver

Publish artifacts & persist learnings

Run complete · learnings signed

All phases signed

Proof

Proof from a codebase that runs on TRW

Tracked repo metrics from work reviewed and shipped with TRW itself.

Patterns Discovered

3,000

Gotchas, patterns, and decisions your agents never have to rediscover.

Agent Actions Tracked

1,000

Tool calls, checkpoints, and deliveries captured across TRW runs in this repo.

Projects Using TRW

1

Telemetry-backed installs when available, with this repo as the baseline snapshot.

Quality Compliance

How consistently agents follow the engineering workflow before shipping.

Live telemetry when available · Otherwise a curated snapshot from this repo·View all metrics

800+

Dogfooded sprints, not slideware

TRW is developed through its own sprint, PRD, checkpoint, validation, and review loop rather than documented only as a theory.

3000+

Learnings captured from TRW sessions

When session 1 discovers a gotcha, it is stored in `.trw/` and recalled by later sessions. Whether this yields measurable capability lift is actively measured.

20000+

Quality gates, not wishful thinking

20000+ tests, strict type checking, and review gates provide the evidence TRW records before delivery.

Open public beta · Free framework · No approval required

Why it stays in the repo

Work that compounds instead of resetting

Each task leaves behind usable project knowledge — not just output that disappears when the session ends.

YOUR MACHINEAgent.trw/cloud

Local · private

Zero data risk

Everything runs locally — no cloud dependency, no data exfiltration, remove anytime.

patternsgotchasdecisionscontexthistorydev-1dev-2new-devKNOWLEDGE RETAINED

Durable · transferable

Knowledge that outlasts your team

When engineers leave, their AI agent's accumulated knowledge transfers instantly to the next person.

sessionsvalue2x10x50x100xwithoutTRW

Compounding · cross-project

Compound returns at scale

One agent's discovery benefits every project — a genuine compounding asset.

Install

Install once. Improve the next session.

TRW wires in as a single configuration entry. No app code changes. No migrations. Your existing tools stay in place. Remove it anytime — zero lock-in.

TTY_INSTALLone command
1# Install or upgrade TRW in your project
2curl -fsSL https://trwframework.com/install.sh | bash

Offline by default

Nothing leaves your machine. Telemetry is opt-in.

Plain-file state

Project knowledge lives in readable repo-local files that you can inspect, version, archive, or remove.

Language-agnostic

TRW works with any codebase. Verification hooks can run your existing test stack, not a new one.

FAQ

Common questions

AI writes code. TRW makes it engineering.

Start with the docs, create a free account, and keep requirements, verification, and learnings connected from one session to the next.

Open public beta · Free framework · Plain-file repo-local state