In Development2026
Local Agent Development System
A connected local agent development workflow that carries work through policy, orchestration, shared execution, and observability.
Explore the wider architecture and technical reference for this connected local development system.
Agent Workflow is presented as one operating path, not four standalone products. Tritt drives cross-project work into Paseo workspaces, Metis supplies repository policy, Baton protects shared execution, and Nopi makes live state observable.
01 / Policy layer
mētis composes a canonical policy set into self-contained AGENTS.md files across projects. Composition, version, and hash metadata make repository policy state inspectable and allow drift to be detected before an update.
In the workflow, it supplies durable project instructions without making each repository depend on a shared runtime file. Its role is deterministic policy composition and synchronization, not task execution.
02 / Shared execution coordination
Baton coordinates the shortest shared-machine section of a workflow: a heavy regression command, foreground application or Computer Use session, or another operation that needs GPU or global state. Repository inspection, editing, and isolated tests remain outside the lease.
Explicit acquire, renew, release, and run semantics let cooperating agents wait for a busy machine instead of treating ownership as a failed build, while recovery handles expired or interrupted leases.
03 / Orchestration and task driving
Tritt evaluates an execution request, maps affected projects and dependencies, and routes work to the appropriate Paseo workspaces. Independent tasks can run in parallel; real dependencies, mutable-state conflicts, and shared-resource limits serialize only the affected work.
The current foundation is a documented, dogfooded orchestration contract rather than a standalone service. Paseo remains the execution runtime; Tritt does not add its own scheduler, database, desktop UI, or agent runtime.
04 / Monitoring and observability
Nopi collects Paseo agent, workspace, and session state into a live topology dashboard. It brings provider and model resource state together with Baton coordination status so the workflow can be observed without becoming its control plane.
The current setup pairs a loopback collector with the Windows UI, preserves source freshness and unknown states, and surfaces conservative stuck-workflow signals in full and always-on-top compact views.
