Durable sessions
Persist turns and replay event history instead of forcing the frontend to guess what happened after a disconnect.
Machine-side agent infrastructure
Stop treating agent orchestration like frontend garnish.
Gooselake is the runtime layer for agents that need to persist, recover, stream, coordinate, and keep working after the client disappears. The UI becomes a remote control. The runtime becomes the engine room.
What Gooselake is
An air traffic control tower for machine agents.
It owns the hard parts that surface once an agent stops being a demo: event durability, reconnectable streams, auth staging, process lifetime, machine operations, and cross-provider normalization.
Provider abstraction
Normalize Codex, Claude, and ACP behind one runtime contract so the UI does not become a museum of provider quirks.
Machine-side execution
Keep processes, worktrees, filesystem actions, and MCP tool wiring on the host where they belong.
Team coordination
Support multi-agent communication and delivery semantics without inventing another browser-tab-only orchestration layer.
Who it is for
Teams building agent systems with operational consequences.
Product teams building serious agent interfaces that cannot depend on a browser tab staying alive.
Platform and infra engineers who want a reusable runtime contract instead of repeating orchestration logic in every client.
Operator-heavy workflows where agents need file access, process control, recovery, and receipts.
Core capabilities
The runtime owns what the product will eventually depend on anyway.
Execution
Provider-backed turns, terminal output, approvals, and recovery paths.
Transport
HTTP control APIs, SSE fanout, replayable histories, and reconnect-safe clients.
Host operations
Processes, worktrees, filesystem actions, and MCP sidecar plumbing.
Coordination
Team messaging, delivery semantics, and machine-local operational boundaries.
Gooselake is what you build when you stop pretending the browser is the right place to host runtime truth.