Stack
What I actually run
Not a leaderboard. This is the current loadout, with the honest verdict: what gets used every day, what is on trial, what I dropped and why. Revised when an experiment changes my mind - the revisions are the point.
Last revised · November 2026
Harnesses
4The thing that turns a model into something that can actually edit a repo.
| Tool | Role | Verdict |
|---|---|---|
| DeepSeek HarnessLocal agent runtime; tools, subagents, workflows, permissions. | Daily driver | dailyEvery experiment in the lab runs here first. The permission model and the audit trail are the reason. |
| Claude CodeTerminal agent, strong on long refactors and repo-wide reasoning. | Second opinion | trialUsed when a task needs a very long single-threaded session. Resumability is good; cost tracking still manual. |
| CursorIDE-native agent, fast inner loop on small diffs. | Editor | dailyStill the best place to review and steer a diff line by line. I do not trust it with anything wide. |
| AiderGit-native pair programming, tiny surface area. | Fallback | watchSurvives every tooling shakeout because it does one thing. Good for scripted, repeatable edits. |
Verification
2The part everyone skips and then pays for twice.
| Tool | Role | Verdict |
|---|---|---|
| Vitest + PlaywrightUnit/integration tests plus a real browser. | Ground truth | dailyIf the agent cannot make a test pass, it has not finished. Everything else is opinion. |
| mutation-style probesDeliberately break code, check the suite notices. | Trust check | trialThe cheapest way to find tests the agent wrote to match its own bug. |
Context & retrieval
3What the agent is allowed to know, and at what price.
| Tool | Role | Verdict |
|---|---|---|
| Repo docs as specARCHITECTURE.md, ADRs, task files in-tree. | Primary | dailyVersioned with the code, reviewed like code. Beats any external knowledge base I have tried. |
| MCP serversStructured tools over ad-hoc scraping. | Integration | dailyWorth it when the data is genuinely external. Not worth it as a way to avoid writing a script. |
| Vector search over the codebaseEmbeddings for code retrieval. | Dropped | droppedConsistently worse than grep plus a good file map. Revisit when the repo exceeds a few million lines. |
Orchestration
3More than one agent, or one agent more than once.
| Tool | Role | Verdict |
|---|---|---|
| SubagentsScoped children with their own context. | Daily driver | dailyThe single biggest quality win so far: the parent stays clean, the child can be wrong safely. |
| Workflow scriptsFan out N tasks, collect structured results. | Batch work | trialExcellent for audits and migrations across many files. Overkill for anything with one obvious path. |
| LangGraphGraph-based agent orchestration in Python. | Prototyping | watchFine for research code. I have not kept a production system on it. |
Observability
2If you cannot see the run, you cannot improve it.
| Tool | Role | Verdict |
|---|---|---|
| Transcript logsFull prompt/tool/result trails, kept on disk. | Non-negotiable | dailyRaw JSONL per session, committed next to the experiment. Every post in /lab links to one. |
| Cost + latency ledgerToken spend and wall-clock per task. | Decision input | dailyRecorded per task, not per month. A monthly bill tells you nothing about which workflow is worth keeping. |