Covendocs

Roadmap

Where Coven is headed.

OpenCoven Public Roadmap

Last updated: 2026-05-09

This roadmap is the public progress ledger for OpenCoven, Coven, CastCodes, Cast Agent, and Cast Codes.

It is intentionally written as a community-facing map, not an internal promise sheet. Items move when they are designed, implemented, tested, released, or deliberately cut. Dates are avoided unless a release is already scheduled.

For issue-ready docs work that has not been created in GitHub yet, see Docs Issue Plan.

North Star

OpenCoven is building a local-first agent workspace where autonomous coding harnesses can work inside explicit rooms.

OpenCoven product layers
LayerRoleMeaning
CovenRuntime substrateProject-scoped harness sessions, PTYs, logs, and local APIs.
CastCodesFirst-party workspaceVisible panes, files, diagnostics, agent lanes, sessions, review, and merge flow.
Cast AgentSubstrate and session backendCollects workspace context, streams gateway responses, and keeps Coven sessions visible.
Cast CodesPortable intent grammarRoutes switching, delegation, broadcast, status, resume, and handoff intent across clients.
OpenClaw integrationsOrchestration surfacesHand work into the same local runtime without hiding what happened.

The simple promise:

One project. Any harness. Visible work.

How to Read This Roadmap

Roadmap status legend
StatusMeaning
ShippedThe work exists in public code or public package/release artifacts.
NowActive stabilization or near-term implementation.
NextPlanned after the current stabilization slice.
LaterDirectionally important, but not allowed to distract from the local-first MVP.
LabExperimental work explored in public when possible, but not treated as a stable promise yet.

Current Snapshot

Coven

Status: early public MVP, usable by adventurous local-first developers.

Coven roadmap snapshot
ItemStatusArea
Public OpenCoven/coven repoShippedProject
Rust CLI command named covenShippedCLI
Beginner-friendly coven / coven tui entrypointShippedCLI/TUI
coven doctor setup checksShippedDiagnostics
Local daemon lifecycle: coven daemon start/status/restart/stopShippedDaemon
Project-root and cwd boundary guardShippedSafety
Built-in Codex and Claude Code harness adaptersShippedHarnesses
PTY-backed coven run codex|claude <prompt> sessionsShippedSessions
SQLite-backed session metadata and event logShippedStore
Session browser and rituals: Rejoin, View Log, Summon, Archive, SacrificeShippedSessions
Scriptable and human session output: coven sessions, --plain, and --allShippedSessions
Local HTTP-over-Unix-socket API for clientsShippedAPI
Versioned coven.daemon.v1 API contract with named apiVersion, capabilities, structured errors, and monotonic event cursorsShippedAPI
Compatibility tests for the external OpenClaw bridgeShippedCompatibility
First-run recovery hints for missing Codex or Claude Code CLIsShippedOnboarding
Real CLI smoke coverage for daemon restart, attach replay, kill, archive, summon, and sacrifice flowsShippedTesting
Install verification and release wiring for macOS, Linux x64, and Windows x64 npm package pathsShippedRelease
Published npm wrapper packages: @opencoven/cli, @opencoven/cli-macos, @opencoven/cli-linux-x64, and @opencoven/cli-windowsShippedRelease
Public install guide for npm, Cargo/source, macOS, Linux, Windows, WSL2, and planned container/Nix pathsShippedDocs
External OpenClaw bridge package kept outside OpenClaw coreShippedIntegration
Architecture, operational model, product spec, brand docs, and MVP planShippedDocs
Keep versioned daemon API contract and external-client compatibility alignedNowAPI
Keep public docs aligned with the actual CLI/API surfaceNowDocs
Turn the MVP checklist into linked GitHub issues/milestonesNextPlanning
Generic command adapter after enough real usageLaterHarnesses
Additional harness adapters such as Hermes, Aider, Gemini, OpenCode, or user-defined local harnessesLaterHarnesses
Policy/approval hooks for sensitive actionsLaterSafety
Richer session artifacts and attachmentsLaterSessions
Phase 1: Handoff protocol and context transfer between harnessesLaterMulti-harness orchestration
Phase 2: Capability discovery and intelligent task routingLaterMulti-harness orchestration
Phase 3: Multi-instance coordination across harnessesLaterMulti-harness orchestration
Phase 4: Audit dashboard and compliance toolingLaterMulti-harness orchestration
Optional cloud/team collaboration only after the local runtime is boringly reliableLaterCollaboration

CastCodes and Cast Agent

Status: early first-party workspace and substrate backend, becoming the visible CastCodes client for Coven sessions and agent work.

CastCodes roadmap snapshot
ItemStatusArea
CastCodes app with Coven-facing agent panel directionShippedProject
Visible panes for local parallel workShippedCockpit
Git worktree isolation per agent laneShippedWorktrees
Agent launcher registry with multiple coding CLIsShippedLaunchers
Multi-select agent launchesShippedLaunchers
Pane menu for inspect, merge, PR, attach, and cleanup flowsShippedReview
File browser, code preview, and diff-oriented review affordancesShippedReview
Project sidebar, pane visibility controls, and reopen flowsShippedWorkspace UI
Rituals for repeatable project setupsShippedAutomation
Lifecycle hook docs and generated hook referenceShippedDocs
Docs site and public README/spec/smoke docsShippedDocs
Cast Agent crate, runtime, gateway health, session list, click-through, streaming, and substrate collectionShippedCast Agent
Coven session visibility and launch integration through the local bridge pathShippedCoven integration
OpenClaw repair ritual direction started publiclyShippedOpenClaw
Public CastCodes to Coven demo loop documented: intent, session, pane, diff review, and finish/cleanupShippedDocs
Stabilize Coven session UX in CastCodes: list, open, launch, attach/rejoin, and unavailable statesNowCoven integration
Keep CastCodes useful without Coven installedNowFallbacks
Continue dogfooding CastCodes for branch/worktree hygieneNowDogfooding
Tighten review/merge flows so agent output stays explicit and inspectableNowReview
Demo step 1: open project in CastCodesNextDemo loop
Demo step 2: launch a Coven-backed Codex or Claude sessionNextDemo loop
Demo step 3: watch it as a visible pane/sessionNextDemo loop
Demo step 4: inspect files and diffsNextDemo loop
Demo step 5: merge, PR, archive, or clean up explicitlyNextDemo loop
Add public issues for rough edges discovered during dogfoodingNextCommunity
Improve onboarding for tmux, agent CLI detection, and Coven availabilityNextOnboarding
Make Discord updates easy to generate from shipped commits and roadmap issuesNextCommunity
Native macOS cockpit explorationLabDesktop
Desktop shortcuts and faster project/session switchingLabDesktop

OpenClaw Integration Path

Status: opt-in bridge direction, not bundled into OpenClaw core.

OpenClaw integration roadmap snapshot
ItemStatusArea
Technical OpenClaw bridge spike completed and intentionally parked before merging into coreShippedBridge spike
External @opencoven/coven plugin direction established so OpenClaw core stays cleanShippedPackage boundary
Local socket/API boundary makes Coven the authority layerShippedArchitecture
Treat the Coven API as the compatibility boundaryNowAPI
Keep compatibility tests and API versioning as the gate before encouraging broad plugin usageNowTesting
Keep OpenClaw copy honest: orchestration sits above Coven; it does not replace the runtime substrateNowMessaging
Publicly document the external plugin path, trust boundary, and compatibility gateShippedDocs
Add a demo showing a task moving from intake to Coven runtime to CastCodes reviewNextDemo

Milestone Map

Rendering diagram…

Colour coding mirrors maturity: filled lavender is shipped or stabilising; outlined slate is next/later. Edges show prerequisite direction, not a strict schedule.

Public Milestones

Milestone A - Local Runtime Foundation
ItemStatus
Public repo and docsDone
coven CLIDone
Project-root safetyDone
Codex and Claude adaptersDone
PTY sessionsDone
SQLite session/event ledgerDone
Daemon lifecycleDone
Local sessions/events APIDone
Versioned API contractDone
Compatibility tests for external clientsDone

Discord Transparency Model

We should keep Discord updates lightweight and repeatable.

Suggested Channels

Discord transparency channels
ChannelPurpose
#roadmap or forum-style RoadmapMilestone threads.
#dev-updatesWeekly summaries.
#help-wantedScoped issues that community members can actually pick up.

Weekly Update Template

## OpenCoven weekly update — YYYY-MM-DD

### Shipped
- ...

### Building now
- ...

### Next up
- ...

### Help wanted
- ...

### Links
- Roadmap: https://github.com/OpenCoven/coven/blob/main/docs/ROADMAP.md
- Coven issues: https://github.com/OpenCoven/coven/issues
- CastCodes issues: https://github.com/OpenCoven/cast-codes/issues

Rules for Honest Updates

Rules for honest updates
RuleReason
Do not promise dates unless we are already in release mode.Avoid turning direction into false commitments.
Link shipped work to commits, releases, issues, or docs.Make progress independently verifiable.
Mark experiments as Lab instead of pretending they are committed roadmap items.Keep explorations distinct from promises.
Separate Coven runtime, CastCodes workspace, Cast Agent backend, Cast Codes intent, and OpenClaw intake.Help people understand the architecture.
Prefer small public issues over giant vague tasks.Make contribution paths real.
Ask for help only when the task has a clear acceptance condition.Respect community attention.

First Public Discord Post

We opened a public roadmap for OpenCoven/Coven/CastCodes so progress is easier to follow.

The short version:
- Coven is the local runtime substrate: project-scoped Codex/Claude sessions, PTYs, logs, daemon API.
- CastCodes is the visible workspace: panes, sessions, substrate, review, merge/PR flows.
- Cast Agent is the substrate and session backend inside CastCodes.
- The next serious focus is hardening the Coven API contract and polishing the CastCodes + Coven demo loop.

Roadmap: https://github.com/OpenCoven/coven/blob/main/docs/ROADMAP.md
Coven: https://github.com/OpenCoven/coven
CastCodes: https://github.com/OpenCoven/cast-codes

We’ll start posting lightweight shipped / building / next updates here so the work is easier to follow and easier to help with.

Last updated on

On this page