5 ms·
We should probably only interact with the agent by writing to the log, which it executes from, and the agent should probably only interact with the external env
by try-working 3mo ago
We should probably only interact with the agent by writing to the log, which it executes from, and the agent should probably only interact with the external environment by writing and executing code. That fixes a lot of issues with non-determinism.
- lmwnshn 3mo agoAgreed. While not directly applicable, I was a huge fan of Mozilla's rr [0] in undergrad. Quoting their site: > rr records a group of Linux user-space processes and captures all inputs to those processes from the kernel, plus any nondeterministic CPU effects performed by those processes (of which there are very few). I think the solution will resemble that. You don't control the LLM, sure. But you can control what it sees, and maybe that's good enough. [0] https://rr-project.org/ https://rr-project.org/
- DenisM 3mo agoWhat if a tool produced an error and a retry? Is retry loop now a part of the log?
- lmwnshn 3mo agoFlaky tools and unreliable systems aren't that different. "What if my database crashes while recovering? What if it crashes while recovering from a crash-while-recovering?" That's when you pull out database ARIES, UNDO / REDO.