Fetching from the wire…
Public story · 2026-09-08 · high
Its relayd component reruns the agreed checks inside the task's own worktree and flags exactly what the agent got wrong.
Why now: Entente's repository appeared on GitHub on September 4, 2026.
Entente sits on top of Claude Code and Codex, requiring an agent that receives a task to accept a written contract or ask real questions before starting. Multi-agent handoffs usually end when the sending agent says it's done, and that self-report is what breaks down when the work is wrong. Entente removes that trust point by verifying the result itself, without relying on the agent's own account of it.
The enforcement comes after that handshake. A component called relayd reruns the contract's declared checks itself, inside the task's own worktree, and compares the real result against what the agent claimed. When the two disagree, relayd writes a delta repair naming only the criteria that failed. It attaches an explicit repair budget, so the agent fixes the gap instead of restarting from zero.
Every contract, check, human decision and repair gets appended to a JSONL log. A chain of agent handoffs leaves a written record, not a single pass-or-fail flag. The project is MIT licensed, needs Node 22+, and the repository went up on GitHub on September 4.
I haven't run it against a real multi-agent chain, so I can't say how the repair budget behaves when an agent can't clear the bar. The repo doesn't say what happens when a repair attempt exhausts its budget without passing.
Each link below shares sources, entities, or timing with this story.
affaan-m/ECC (36.3k forks, MIT) bundles 67 agents, 284 skills, 94 legacy command shims, and "instincts", patterns learned from prior sessions with confidence scores that auto-recall when relevant, plus a .ecc/memory/ markdown vault that's explicitly cross-harness, so context s...
modiqo/waggle (dual Apache-2.0/MIT, v0.5.3 on July 14, 762 stars since July 8) attacks token waste in multi-agent handoffs: each artifact gets a ~30-byte attributed token resolving into a consumer-specific projection sized to the reading model. Artifacts never auto-expand into...
Three frontier models shipped in a single week this month, and teams with a standing eval harness had a routing decision in hours. Anthropic's own agent-eval guidance says 20-50 tasks drawn from your real usage and real failures is enough to detect issues (DeepEval). DeepEval...
One number predicts whether your agent finishes the task, and it isn't the benchmark score. Shubhra Mittal's paper (arXiv 2609.01660) analyzed 10,664 trajectories across nine models spanning 1.2B to 671B parameters and found task success follows P(n) = p^n, where p is a single...
The trick is one line in a file you never read. Manifold Security published eight findings across seven coding agents (Claude Code, Codex, Cursor, Grok Build, Qwen Code, goose, Hermes Agent) that all reduce to the same mechanism. A repository's own .git/config sets core.fsmoni...
Runta published FrontierHarness on September 2 and it's the most directly useful benchmark I've read this quarter, because it controls the one variable everyone conflates. Nine agent harnesses (Codex, Claude Code, OpenCode, Pi, Oh My Pi, DeepSeek Harness, Kimi Code, Exo Harnes...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.