Problem
Many agent demos collapse when the workload becomes multi-step and stateful. Reliability needs stronger substrate primitives.
Approach
Lago emphasizes infrastructure fundamentals:
- explicit session and workspace boundaries — every agent run operates in a scoped context with defined inputs and outputs
- reproducible tool execution — the same tool call with the same inputs produces the same result
- predictable event and state handling — state transitions are logged and replayable
- interfaces that support auditability — every action leaves a trace
Architecture overview
The design separates execution substrate from higher-level UX so each layer can evolve independently. The substrate handles sessions, tool dispatch, state persistence, and event streaming. Products like Arcan build operator-facing workflows on top without reimplementing these primitives.
Current status
Active OSS iteration with focus on developer ergonomics and testability. The session and tool execution primitives are stabilizing.
Why it matters
Lago helps define the baseline primitives required for practical, maintainable agent systems.