right-agent 0.3.0 is out!
Most of it went into the parts you don't see until something breaks. Skill learning, dashboards, secrets, gateway recovery. The kind of thing that only matters when an agent runs for days. Showcase below.
right-agent 0.3.0 is out!
Most of it went into the parts you don't see until something breaks. Skill learning, dashboards, secrets, gateway recovery. The kind of thing that only matters when an agent runs for days. Showcase below.
@williewonder_ Small Haiku classifier at the end of every foreground turn. Inputs: user msg, assistant reply, skills already cited, this turn's cost/elapsed vs the agent's P50/P90/P99 baseline. Output: skip / patch existing / create new. Probe-writer only forks on patch or create.
Smaller fixes worth flagging:
- OpenShell gateway down at startup used to kill the bot. Stays up and recovers now.
- Silent background failures now emit a diagnostic.
- Idle 1M sessions bloating context. Auto-compact after 2h over 40%.
https://t.co/pig6btsFKs
Prompt cache was leaking. Per-turn chat context lived in the system prompt, and Hindsight recall changed it every turn, so the prefix was never byte-stable. Moved that block to a volatile stdin prefix. System prompt now stays stable per agent, cache hits across turns.
Everyone fights Codex vs Claude Code. I use both for different parts of a big milestone.
Claude Opus 1M context holds the whole thing. Specs, plans, decisions, open questions. All in one place. Including the review.
The actual coding goes to Codex. Headless, in an isolated worktree.
So I shipped codex-sprint to wire it into one sprint flow.
Per stage: brainstorm a spec. Write a plan. Isolate a worktree. Codex implements. Headless claude /code-review --fix loops the diff until clean. Verify. Commit. Land. Update the sprint doc. Next stage.
Main context only holds the doc. No diffs, no build logs.
Per stage: brainstorm a spec. Write a plan. Isolate a worktree. Codex implements with --write. Headless /code-review --fix loops. Verify. Commit. Land. Update the sprint doc. Next stage.
Main context only holds the doc. No diffs, no build logs.
Bigger thing is the pattern. AI infra is rebuilding crypto primitives. Opaque blobs, signatures, stateful protocols, replay protection. All shipped without 30 years of attack literature.
The two fields are converging in production. Fast.
Last week a cryptographer poked at an AI feature and found a leak. Normal news for crypto. Fresh news for the AI stack. He didn't break any math. He just looked at how much the model thought.
Second: the blobs replay. Same encrypted reasoning works across different sessions and different accounts. That's a textbook crypto bug shipped on top of a 2026 model.
https://t.co/7Hlr8oZ7H8