Agentic runtime roadmap
OpenKyrozen now has one durable interaction state machine across the classic
CLI, Bubble Tea TUI, web UI, REST, and SSE. Ask and Plan are read-only; accepted
plans become evidence-gated TaskManager work in Agent mode. The following work
is intentionally deferred rather than hidden behind speculative abstractions:
- Consistent foreground turn steering — extend scoped sub-agent cancellation and assignment queuing to every foreground interface only when the UI can reconcile interaction state and durable receipts after interruption.
- Provider-native typed tool calls — add per provider after parity tests prove the native schema preserves the current fail-closed control protocol.
- OS-level sandboxing — add platform-specific process/filesystem isolation beneath capability tokens; capability labels are policy, not an OS sandbox.
- Long-run checkpoints and context compaction — add resumable checkpoints that retain plan/question versions, evidence, and outstanding approvals.
- Additional delivery channels — reuse the interaction envelope only where a channel can render questions/plans and correlate responses safely.
MCP remains intentionally non-interactive. Tool approvals remain distinct from clarification questions on every future surface.
Chat-owned sub-agent orchestration now supplies parallel jobs, independent sessions, cancellation between tools, structured results, automatic read-only peer review and parent receipt reconciliation. Interrupted jobs are reported on restart; mutations are never replayed automatically.
Release acceptance
Run make agent-acceptance for the deterministic plan-to-deployment workflow.
make wheel-smoke repeats the same check against a newly installed wheel from
outside the checkout. It verifies plan approval, Agent-mode execution, durable
receipts, generated files, and a real loopback HTTP deployment without using a
provider key.
Live-provider validation is optional and must be reported as unverified unless it is actually run. To exercise it manually, create a temporary project and state database, then run the installed UI with the configured provider:
work_dir="$(mktemp -d)"
mkdir "$work_dir/project"
KYROZEN_DB_PATH="$work_dir/state.sqlite3" kyrozen --project "$work_dir/project"
Select Plan mode, request a small locally served page, accept the proposal, and confirm the task receipts and deployment check before reporting a live pass.