Agent identity
Role, ownership, authority, and history survive the session.
roleownerauthorityhistory
The thesis
A durable operating layer for agents.
Voxelbox is model- and agent-agnostic. It provides context, memory, orchestration, and durable state around replaceable models and harnesses—including its own—and coordinates work across Codex, Claude Code, Pi, and Goose.
System architecture
Models and agent harnesses are replaceable. Voxelbox owns the durable layer around them: identity, context, memory, orchestration, and the record of the work.
FoundryRuntime architecture
Durable operating state surrounds replaceable models and agent harnesses.
OperatingHuman requestScheduleEvent / webhookAgent signal
Voxelbox-owned operating layerlocal first · one Go runtime
Spaces + memory
The filesystem is the durable address for work and context.
/workspace.agency/memory/project files
Orchestration
dispatchjobsmailthreadsdeliberationevents
Built-in harnessCoordinate work. Delegate execution.Can act directly or hand the run to a connected harness.
CodexClaude CodePiGoose
Shared context and orchestration. Different agent runtimes.
Model boundaryLocal or hosted inference, selected by policyreplaceable beneath every execution path
Shared capabilities
ToolsoperationsSkillsknowledgeRoutinesresponsibilitySurfacesprojections
Evidenceevents · outcomes · corrections
Written back to spaces + memory for the next run
Runtime-owned boundary Replaceable dependency
Architecture adjacency
Buzz is a natural surface
Block's Buzz gives humans, agents, workflows, and repositories one signed event log and one shared workspace. It already speaks the protocols Voxelbox expects at the edge: ACP for harnesses, MCP for tools, and events for work that happens outside an open chat.
The clean fit is an adapter, not a merger. Buzz can own rooms, membership, approvals, search, and the human conversation. Voxelbox can own agent identity, context, delegation, schedules, and durable execution. A Buzz event creates or updates work; Voxelbox projects progress and results back into the room.
Proposed surface adapterShared workspace outside. Durable execution underneath.
Block / Buzz ↗Community surface
- signed events + identity
- channels, threads + approvals
- shared search + audit trail
Surface adapter
message · reaction · schedule · webhook
Buzz event → Voxelbox taskVoxelbox event → Buzz channelAgent operating layer
- context + durable memory
- delegation + harness routing
- background lifecycle + evidence
Architecture hypothesis, not a current integration. Buzz remains the source of truth for the room; Voxelbox remains the source of truth for delegated work.
Runtime integration
Native sessions become durable context
Claude Code and Codex remain the source of truth for their own transcripts. Voxelbox listens at lifecycle hooks when they exist, then reconciles local session directories on an interval so missed events and imported work still enter the same record.
Before compaction, a hook checkpoints decisions, active files, and open threads. At stop, another extracts intent, tools, files, and commits. The session bridge kicks off a derived summary only after capture; it never replaces or rewrites the underlying transcript.
Native session sources
Claude Code~/.claude/projects/*
Codex~/.codex/sessions/*
Voxelbox harness~/.voxelbox/state/*
Capture seamsImmediateLifecycle hookssession start · pre-compact · stop ReconcilePeriodic session syncdiscover · import · update · recover
Normalize
identityworkspaceintenttoolsfilesoutcome
Raw transcripts stay untouched.
Durable outputs
Session recordstatus + lineage
Activity logwork + evidence
Pre-compact factsdecisions + open threads
Memory pagederived summary
Eventually I would like Voxelbox to stop asking me questions it already knows how to answer.