3 ms·
I’m building AgentOS [1], trying to experiment where agent substrates/sandboxes will head next. It's a deterministic, event-sourced runtime where an “agent worl
by lukebuehler 9mo ago
I’m building AgentOS [1], trying to experiment where agent substrates/sandboxes will head next. It's a deterministic, event-sourced runtime where an “agent world” is replayable from its log, heavy logic runs in sandboxed WASM modules, and every real-world side effect (HTTP, LLM calls, code compilations, etc.) is explicitly capability-gated and recorded as signed receipts. It ensures that upgrades and automations are auditable, reversible, and composable. The fun bit is a small typed control-plane intermediate representation (AIR) that lets the system treat its own schemas/modules/plans/policies as data and evolve via a governed loop (propose > shadow-run > approve > apply), kind of “Lisp machine vibes” but aimed at agents that need reliable self-modification rather than ambient scripts.
[1] https://github.com/smartcomputer-ai/agent-os https://github.com/smartcomputer-ai/agent-os
- saadn92 9mo agoHa. Nice name. Looks like we both are: https://github.com/saadnvd1/agent-os https://github.com/saadnvd1/agent-os
- schappim 9mo agoWe should talk! I have been doing pretty much the same, but have been leaning heavier on the context parsing and schema sharing between apps.
- CuriouslyC 9mo agoThis is definitely interesting, seems like the sort of thing Nix would do well.
- lukebuehler 9mo agoThanks! NixOS is great at building and configuring systems, while AgentOS is about running and governing long-lived, deterministic agent worlds. They share ideas like immutability and declarative state, but they operate at different layers. I would say if NixOS is about reproducibly constructing a system, AgentOS is about reproducibly operating one: tracking decisions, effects, and evolution over time.