Repository navigation
A short checklist for AutoGen teams that write to real systems #8471
Replies: 2 comments 2 replies
|
The single key reused on every retry is the item I would test hardest, because it is easy to claim and easy to break. My usual check: let the specialist issue the write, kill the process after the API accepts it but before the acknowledgement reaches the team, restart, and count tickets or charges on the other side. Run that ten times at different kill points and expect exactly one side effect each time. I would also test your first point directly by having the reviewer's sign-off message contain an instruction to delete something, and assert the manager logs it as data and runs nothing. |
|
stackyardweekstart Treat another agent's output as data, not instructions. When an LLM generates a JSON payload without strict schema validation, downstream executors often misinterpret string content as shell commands. This cascades into corrupted directories or unintended writes. Reusing a single key for retries directly addresses idempotency. Without it, network timeouts trigger duplicate charges or permanent data loss that cannot be rolled back. The system behaves as a state machine rather than a conversation. For human approval on irreversible actions, is there a standard way to enforce this without introducing significant latency in the handoff between manager and reviewer agents? |
Uh oh!
There was an error while loading. Please reload this page.
Disclosure: this is ours, from Stackyard. It's a free MIT set of small patterns for agents that touch files, money or APIs: https://github.com/stackyardweekstart/weekstart-starter-pack
For AutoGen teams, four of them sit naturally at the handoff between a manager, a specialist and a reviewer:
They're patterns to adapt, not a library. There's also a free in-browser setup check at https://stackyard.fyi if you want a quick gap list first.
How are others gating writes when one agent in the team has already approved them?
All reactions