Bind work to a selected project, task, policy context, and expected outcome.
AgenZync architecture
A runtime for teams,
not a wrapper around chat.
AgenZync separates mission ownership, agent collaboration, execution isolation, tool authority, evidence, and memory into explicit layers. That makes the system inspectable, replaceable, and recoverable.
Framework implementation
Explicit boundaries.
Composable capabilities.
The root agent operates through durable collaboration and policy services. Provider-specific execution sits behind adapters, while product modules build on the same runtime instead of bypassing it.
The owner recruits workers, routes context, observes attempts, and steers the live team.
Durable threads, batches, messages, leases, retries, fencing, and recovery preserve team state.
Provider adapters run agents in bounded targets; coding agents can receive isolated Git worktrees.
Capability families, specialist skill packages, and risk-aware approvals govern what agents can do.
Events, reports, source snapshots, ChangeSets, and evidence files remain available for inspection.
Hierarchical agent spawning
Delegate in a tree.
Control from the owner.
Spawned agents receive a parent identity, depth, role, assigned skill, model configuration, and bounded runtime context. Multi-agent skills declare their strategy and output in validated frontmatter and must describe the delegation contract in a Multiagent Setup. The metadata guides suitability; the owner still decides, observes, verifies, and synthesizes.
ROOTMission ownerdepth 0 · steering authority
messagesattemptsredirectinterruptretry / recover
Two-stage durable memory
Compress the context.
Curate the memory.
AgenZync treats context-window compaction and durable project memory as different jobs. One keeps a live conversation within its context budget. The other learns from retained, high-signal run evidence through a two-stage pipeline.
Context compaction
Selects persisted conversation history, creates a semantic replacement, and continues the active run without pretending that every compressed detail is durable project knowledge.
messages→validated replacement→continued turnTwo-stage consolidation
Discover retained run sources, assess signal, redact sensitive shapes, build bounded evidence, and register candidate claims and rollout summaries.
Reserve accepted inputs, compare the current generation, apply supported updates and forgetting, validate hashes, and promote a new durable generation.
redactionbounded evidenceinput hashesleases & fencinggeneration historysemantic no-op
Inspectable by default
The run leaves a trail.
Mission state is not trapped inside a provider’s hidden context. AgenZync persists structured state and bounded artifacts so operators can inspect what happened, recover interrupted work, and review the evidence later.
run/├─ events.jsonl├─ agent threads + attempts├─ messages + approvals├─ ChangeSets + verification├─ reports + source snapshots└─ completion + quality reviewContext engineering
Keep what drives the work.
Move bulk out of the active window.
AgenZync manages the model-visible context as a governed runtime resource. The goal is not to hide history, but to keep sampling focused while preserving inspectable evidence outside the active window.
Persist the actual model-visible conversation and prove gap-free replacement coverage before sampling.
Keep recent results, trim older bulk, and eventually replace stale outputs with a pointer while retaining the full material in events, state, or artifacts.
Reserve an exact source segment, validate its replacement, commit atomically, and refuse to continue when coverage cannot be proven.
When required work remains after a turn, continue from the durable Mission ledger instead of restarting or trusting a fading chat summary.
MCP-ready
Bring external tools and resources into the same governed runtime.
Configure local stdio or remote streamable HTTP MCP servers, namespaces, working roots, bounded output limits, retries, persistent sessions, resource discovery, and OAuth with PKCE and refresh support.
MCP SERVERS
knowledge-base
streamable HTTP · OAuthlocal-analysis
stdio · worktree rootprocurement-data
tools · resources · elicitation · bounded outputdisabledOpen-source operating layer
Inspect the architecture. Extend the system.
AgenZync is MPL-2.0 licensed so teams can understand the runtime boundaries, adapt specialist modules, and keep control of their execution environment.
Explore AgenZync