hipvlady

6 ms·

1.
by hipvlady 1mo ago
I am the author and would like to point out that this mechanism is not new, since Kleppmann uses a similar approach with fencing tokens in his article "How to do distributed locking". The alternative I mention is also commonly emp
2.
The silent-data-loss taxonomy: four ways an AI agent's write disappears(agent-coherence.dev)
1 points by hipvlady 2mo ago|1 comments
3.
by hipvlady 2mo ago
Author here. Why do we need a taxonomy when we could just say "we stop lost updates"? Two of the four aren't mine to fix. Key mismatch (write to X, read from Y) and compaction drop (a summarisation step eats the fact) are app
4.
by hipvlady 4mo ago
Great review. If you use this program every day, there is one thing you should know. CLAUDE.md is doing a lot of the most important work here, and it's the most fragile piece of the stack. A rule like "always re-read X before edit
5.
by hipvlady 4mo ago
The title is very fashionable at the moment. Subagents are good at the part that can be broken down into separate tasks. The problem is that each subagent has its own understanding of the plan. When the plan changes, or if one subagent chan
6.
by hipvlady 4mo ago
A shared handoff file is better than implicit coordination. The problem to watch out for is the file becoming out of date: agent A reads Agents-Collab.md, agent B updates it mid-task, and agent A continues to act on what it has read. The pr
7.
by hipvlady 4mo ago
Saying "agents lying" isn't usually deception. It's the model telling a story about a gap that the runtime couldn't fill. This gap could be a rule or a state that the runtime was supposed to respect, but wasn't
8.
by hipvlady 4mo ago
It's really useful to have a clear list of who's on the team and what they do, because there isn't one at the moment. A static team definition doesn't show the runtime hazard. This is when two agents read the same artifa
9.
by hipvlady 4mo ago
It wasn't a crash that cost us the most time; it was a stale read. Two agents shared a plan file. One updated the file during the run and the other continued to work off the version that had been loaded at the start. Both produced plau
10.
Show HN: MESI cache coherence for multi-agent LLM context sync – 95% less tokens(github.com)
1 points by hipvlady 5mo ago|0 comments