| ▲ | The Log Is the Agent(arxiv.org) | |||||||
| 34 points by iacguy 6 hours ago | 6 comments | ||||||||
| ▲ | lukebuehler 14 minutes ago | parent | next [-] | |||||||
Very cool. I settled on the same/similar design in my agent harness. All relevant events that affect the context window are stored in an event log. Forking agents and sessions is simply setting a pointer to the sequence number of another event log. So if you want to check an implementation of this pattern see: https://github.com/smartcomputer-ai/lightspeed | ||||||||
| ▲ | rufasterisco 11 minutes ago | parent | prev | next [-] | |||||||
The paper’s pip library can be tried here | ||||||||
| ▲ | bigcat12345678 an hour ago | parent | prev | next [-] | |||||||
This is true after learning this framing. It's more like the log is the only user/agent accepted consensus. It has to be the grounding base. Although extending it into an agentic system architecture becomes something not necessarily effective in practice. | ||||||||
| ||||||||
| ▲ | tern 13 minutes ago | parent | prev | next [-] | |||||||
Arrived at a version of this view as well and building one on Elixir/Ash. | ||||||||
| ▲ | corgihamlet 2 hours ago | parent | prev [-] | |||||||
My log has a message for you. | ||||||||