agentic-sidecar

Roadmap

Updated 2026-10-17 · Current version: 0.8.2. The root ROADMAP.md is the canonical plan with detailed deliverables and acceptance criteria. Future version targets describe priorities, not committed delivery dates.

Release history

Version Focus
0.2.0 Runtime, policy/risk, Intent Guardian, and LangGraph Govern BLOCK
0.3.0 Planner/Critic heuristics, Judge interface, and provider examples
0.4.0 Budget accounting, seven outcome types, escalation/provenance types
0.5.0 Narration and status/demo/version CLI
0.6.0 Combined runtime with optional evaluator pipeline and public exports

See Features for current capabilities and Limitations for their supported scope.

v0.6.x — Governance & Evaluator Enhancements

0.6.1 implementation prepared, with usage and validation evidence.

v0.7 — Live Status, Audit Lifecycle & Control Room

Implemented; see live operations and acceptance evidence.

v0.8 — Framework Adapters & Optional Integrations

Implemented in 0.8.0; see compatibility and usage.

v0.9 — Evaluation Evidence & Authority Boundaries

v1.0 — Stable Interoperability Contract

Shared & Exclusive context/intent and guardrails (v0.8 implemented). Users may choose context only, guardrails only, or both, independently Shared across a system/task or Exclusive to designated agent(s). Each agent receives shared plus assigned exclusive context; shared guardrails remain mandatory alongside exclusive rules. v0.8 provides scoped configuration, delivery and composition; v0.9 validates privacy, authority and lifecycle behavior; v1.0 stabilizes contracts. Host context delivery is explicit; it does not automatically rewrite agent prompts or provide process isolation.

See the canonical acceptance criteria.

Conditional follow-ups

Local-model risk classification, automatic framework usage extraction, caching, and sampling require measured need before scheduling. Core runtime remains independent of sibling packages; integrations and provider SDKs stay optional.

Planned operational safety acceptance criteria

Sidecar owns emergency braking (stop, block further dispatch and revoke task access through supporting access boundaries) and independent policy enforcement. See the canonical acceptance criteria for milestone dependencies and validation requirements. The v0.7 local stop, cancellation, audit and harness-revocation interface is implemented. v0.8 adds a separate-process enforcing MCP gateway demonstration and Lens native journal verification. Secure service deployment is a harness responsibility; delegated authority and end-to-end privacy validation remain v0.9 work.