Why nobody hands an agent its receipts
Every coding harness can resume a session. We read their docs to see what an agent actually gets back, and found two answers, both without evidence. That gap is why session_wake exists.
Writing
Notes from measuring our own agents.
Everything here comes from one index on one laptop, and every number has a spec or a pull request behind it. Where a measurement is narrow, the post says how narrow rather than rounding it into a claim.
The Cross-Domain Map
A thesis about three tools that each write down what happened but share no field to join on, and the return path we built for Archie so it can finally ask "this task, on that machine, produced this output."
What was I doing?
A coding agent that starts cold, or comes back from a compaction, burns thousands of tokens re-reading its own past. session_wake answers the four questions it is really asking in under 30 lines, from the local index, with no model in the loop.
The effort dial we can't read
A developer report calls reasoning effort a behavioral control, not a percentage of the model. We checked the load-bearing claims against Anthropic's and OpenAI's own docs, then asked what AgentWorth can actually see about it in your transcripts today.
Point it at your own machine.
npx -y agentworth@latest scan