Runtimes, memory, and proof that the agent did the work

herdrdev

The runtime your coding agents live on. Not another chat wrapper: a place agents persist, resume, and share a machine.

Use caseUse it when you want agents to survive a laptop sleep and pick up the same checkout, secrets, and tools.

stablyai

An ADE for a fleet of parallel agents. Run any coding agent against your repo in parallel panes instead of one blessed CLI.

Use caseUse it to fan the same failing test across four agents and keep only the patch that compiles.

mnemon-dev

LLM-supervised persistent memory for agents: graph recall, cross-session knowledge, no vector-store cargo cult.

Use caseUse it to give a coding agent a graph of the last two weeks of decisions so it stops re-deriving your architecture every session.

first-fluke

A multi-agent harness that checks the work by artifacts, not vibes. Stop-hooks verify diffs, tests, and files before the run is allowed to claim success.

Use caseUse it to stop a coding agent from declaring done when the test file was never written.

trycua

Open-source computer-use 2.0: drivers, cross-OS fleets, and benchmarks for training and evaluating desktop agents.

Use caseUse it to give a coding agent a real desktop when the job is a GUI installer, not an API.

Lilian Weng

Weng essay on the scaffolding around self-improving agents. The harness, not the next model bump, is where competence compounds.

Read

justrach

A fast agentic coding harness in Zig: multi-provider, MCP, workflows. Tiny star count, serious systems taste.

Shipped

Tikal

A public skills pack that encodes a team's coding standards as agent skills. The style guide becomes a tool, not a wiki page.

Shipped