AgenZync DocumentationTechnical referenceDevelopment branch · v0.1
Docs/Overview

Technical documentation

This section describes the current AgenZync implementation. It is intended for operators, contributors, integrators, and reviewers who need behavioral contracts rather than product positioning.

Scope

AgenZync is a local-first workspace for running root and child AI agents inside Projects. Product records, execution state, events, artifacts, repository observations, and optional memory are retained locally. Model providers, configured MCP servers, external sources, and user-owned repositories remain outside the AgenZync trust boundary.

The documentation distinguishes persisted authority from presentation. A status shown in the WebUI is derived from stored product and runtime records; URL state, folder names, model text, and worker completion messages do not override those records.

System model

01WebUI / CLI / protocolUser and automation entry points
02Product servicesProjects, Chats, Jobs, modules, and access policy
03Controlled runtimeTurns, tools, agents, Missions, and approvals
04Durable stateCatalog, run database, events, files, and artifacts
05External boundariesProviders, MCP servers, sources, shell, and repositories

Reading paths

Reference

Architecture & stack

Process boundaries, framework versions, storage authorities, and the division between the product layer and runtime.

Open section →Reference

Agent runtime

The controlled turn lifecycle, child-agent attempts, Mission continuation, steering, interruption, and recovery.

Open section →Reference

Code collaboration

Repository registration, isolated Git worktrees, Write Intents, ChangeSets, reconciliation, and verified integration.

Open section →Reference

Context & memory

Why live context compaction and cross-run memory are separate systems, and how both retain evidence.

Open section →Reference

Skills & packages

Validated skill metadata, Multiagent Setup contracts, package recipes, tool routing, and immutable dispatch policy.

Open section →

Status language

TermMeaning in these docs
currentObserved in the present source tree and its tests.
optionalImplemented but dependent on configuration, a module, provider, or rollout boundary.
plannedDesign metadata or roadmap material that is not described as an available capability.
authoritativeThe record or subsystem that owns a decision when representations disagree.
advisoryUseful evidence that cannot independently grant authority or weaken a stronger check.