Transcript formats can change
They are internal to both tools. The parsers skip what they do not understand. If weave analyze finds no sessions after an update, this is the likely cause.
Weave reads your real sessions, finds what you keep correcting, and turns it into reviewed changes to your instructions, skills and hooks. Then it checks whether they worked.
The examples on the left show patterns Weave can find in your sessions. On the right is what it becomes. Nothing crosses without your approval.
What your sessions say
src/legacy/api.ts no longer exists.misleads every sessionWhat your setup becomes
You wrote AGENTS.md once. Since then the codebase moved, you corrected the agent dozens of times, and none of it made it back into the file. Or you let a tool generate it, and now it is four hundred lines the agent skims.
AGENTS.md files, about half were never changed after the day they were created. arXiv 2510.21413AGENTS.md, generated once412 lines
The same repo, kept by Weave14 lines
# Shop API
## Commands
- Verify with `pnpm test` and `pnpm lint`.
- The e2e suite takes 20 minutes. Run it before a release only.
## Rules
- Use pnpm, not npm. The lockfile is pnpm-lock.yaml.
- Money is integer cents, never floats.
- `src/gen/` is generated. Change the schema, not the output.
- Named exports only.
## Ask first
- Migrations, dependency upgrades, anything in `infra/`.
Each line is something the agent got wrong once and could not have found in the repo.
Four steps. The first takes ten minutes, the second takes none, and the last two are what nobody does by hand.
WeaveI've read your manifest, CI config and README, so I won't ask about the stack. How do you know a change is good here?
Youpnpm test has to pass. The e2e suite is too slow, we only run it before a release.
WeaveWhat does every new teammate get wrong once?
YouThey edit the generated client in src/gen. It gets overwritten.
WeaveIs there anything I should always ask before doing?
YouMigrations. Always.
✓ AGENTS.md drafted, 14 lines. Every command in it was run and works.
session 14 · Claude Code you No, use pnpm here. you From now on, named exports only. ← noted agent npm test exit 1 → pnpm test ok session 15 · Codex you Write the release notes for the merged PRs. agent cat src/legacy/api.ts No such file session 16 · Claude Code you pnpm, like I said. you Write the release notes for the merged PRs. ──────────────────────────────────────────── tokens Weave added to these sessions 0 network requests Weave made 0 written to .weave/local/ (gitignored) 1 line
+ Use pnpm, not npm. The lockfile is pnpm-lock.yaml.
npm test failed in 4 sessions; pnpm test worked next each time. “No, use pnpm here.” · “pnpm, like I said.”- The legacy API lives in src/legacy/api.ts.
Try the buttons. In a real session you answer in chat; nothing is ever applied without you.
$ weave analyze Did earlier changes hold? holding Use pnpm, not npm (5 before → 0 after) holding Named exports only (2 before → 0 after) recurring Never force push (2 before → 3 after) too early src/gen is generated (1 before → 0 after)
“Never force push” was written down and broken anyway, so the next evolve proposed a hook instead of a louder rule.
The sessions and numbers in these panels are illustrative. The output format is the real one.
Most tools that learn from you can only append rules. Weave routes each lesson to the cheapest mechanism that works, and each kind of evidence has to clear its own bar first. Pick one.
goes to
weave doctor is a deterministic linter for everything an agent loads. This is a subset of it running in your browser. Nothing you paste leaves this page.
Setup health
Nine of the 19 rules run here. The others need your file system: dead paths, drift between the Claude Code and Codex copies of a skill, missing frontmatter. See all rules.
Nine of the 19 rules run here. The others need your file system: dead paths, drift between the Claude Code and Codex copies of a skill, missing frontmatter. See all rules.
Most of what makes agent setups worse is added with good intentions. These are decisions, not gaps.
Tools that add memory to every session cost thousands of tokens per session for recall that is rarely used. Weave adds nothing to a session. Its hooks talk to you, not to the model.
Planner, architect, reviewer chains multiply token use and do not make a single task better. Weave suggests a subagent only when evidence calls for one.
A skill appears when you have retyped the same request in several sessions, and it contains the steps specific to your repo. Not before.
Every change is a diff you approved, logged in .weave/history.jsonl with the evidence that justified it. You can read why any line exists.
Transcripts are read on your machine by a script with no dependencies and no network code. There is no account, no server and nothing to opt out of.
The output is plain files in the formats both tools already read. Remove Weave and your AGENTS.md, skills and hooks keep working.
Commit them and the whole team gets the same setup, including people who never ran npx. Select a file to see what it is for.
A tool that edits how your agent works should tell you exactly how far it has been proven.
| Claude Code | Codex | |
|---|---|---|
| Skills | tested live in real sessions, as project install and as plugin | discovery tested against Codex CLI 0.169 |
| Hooks | tested live in real sessions | from source config shape taken from the Codex source, not yet run live |
| Transcript analysis | real transcripts | fixtures parser written from the Codex source |
| Platforms | CI runs the suite on Linux and Windows with Node 18 and 22 | |
| Review | An independent adversarial review reproduced 29 defects before release. All are fixed, each with a regression test. | |
They are internal to both tools. The parsers skip what they do not understand. If weave analyze finds no sessions after an update, this is the likely cause.
Feedback detection is pattern matching in English and German. It proposes; the agent and you decide what is real.
Compressed Codex rollouts (.jsonl.zst) are skipped, because reading them would need a dependency.
You need Node 18 or newer and Claude Code, Codex, or both. Weave has no dependencies of its own.
For Claude Code and Codex. Works for the whole team once committed.
Run this in your repository:
It adds three skills, two hooks per tool and a copy of the CLI in .weave/runtime/. Use --claude or --codex to pick one tool.
Start the interview in your agent:
In Codex, approve Weave's two hooks once with /hooks.
Commit the result, work as usual, and run /weave-evolve in Claude Code or $weave-evolve in Codex after a week or so.
Just for you, across all your projects. Claude Code only.
In Claude Code:
The skills are then called /weave:onboard, /weave:evolve and /weave:doctor. Start with:
The complete package as one file. For offline machines, or if you want to read every line before you run it. It includes the CLI, skills and hook configuration.
Put the file in your repository folder and run:
Delete the .tgz afterwards. The installed skills, hooks and CLI now live in your project.
To remove Weave from a project, run node .weave/runtime/cli/weave.mjs uninstall in its root. This removes the bundled skills, hook entries and CLI. Your instructions and custom skills stay. More on uninstalling.
No. Weave is a local script with no dependencies and no network code. It reads Claude Code transcripts under ~/.claude/projects/ and Codex rollouts under ~/.codex/sessions/ for the current project only, and prints a report. That report goes to the agent session you are already in, the same way any file you open does.
The hooks cost none: they make no model calls and add nothing to the model's context. /weave-evolve is an ordinary session you start yourself, typically every week or two, and costs what a short conversation costs.
/init writes a first file from the code. Built-in memory lets the agent keep its own notes on your machine. Weave does the part neither covers: it maintains the shared, committed setup from evidence, routes lessons to rules, skills or hooks, prunes under a size budget, and checks afterwards whether a change worked. It complements both.
No. With existing files, onboarding keeps what you wrote, proposes removals for lines that no longer hold, and shows everything as a diff. weave init itself never touches your instruction files; it only adds skills, hooks and the .weave/ folder.
Weave merges two hook entries into what is already there and leaves everything else alone. If the file cannot be parsed, init stops before writing anything and tells you. Uninstalling removes exactly those two entries again.
No. Either one works. If you use both, they read the same AGENTS.md and the same skills, and weave doctor warns you when the two copies drift apart.
English and German. It looks for phrases like “from now on”, “no, use…”, “ab sofort” or “das stimmt nicht”. It produces candidates only. A quote becomes a rule when the agent and you agree that it is one.
Yes. weave doctor --ci exits with code 1 on errors, --strict on any finding, and --json prints machine-readable output. It is deterministic and takes milliseconds.
The test suite runs on Windows and Linux with Node 18 and 22 on every commit.
Nothing. Weave is MIT licensed and has no paid tier, account or server.