Skip to main content
Version: Next

Roadmap

No dates have been set for any of these. For what already works, start at What Orion is; for what changed in each release, see the release notes.

Not built​

Operations​

Incidents from a shipped product do not reach Orion, and nothing turns a production failure back into a ticket. orion aiops reads only Orion's own run logs.

A shared service​

Orion runs on one machine for one user, with no high availability, team queue or multi-user mode.

Retention​

Nothing prunes watch logs, run transcripts or events.jsonl yet.

Partial​

Identity​

Approval rests on a Slack approver allowlist, and the web dashboard on a local, per-run token. There is no SSO and no secrets vault.

Audit​

The events log records every stage and every agent, but it is local, editable and not tamper-evident.

Evaluation​

Orion scaffolds eval cases and a harness when a spec has an agentic design, but its own eval set is a starter example. Until it holds real cases, keep unattended landing behind a named approver (Safety and limits).

Waiting on something​

Native ticket trees for other trackers​

The native Epic / Story / Task tree is built for Jira only. Linear, Notion and GitHub Issues work through the toolkit's /pm-plan stage.

Working on a sandboxed copy of an existing repository​

orion new --from <repo> is refused since orion new stopped creating workspaces, and orion plan has no equivalent yet. Adopt Orion in place with orion init meanwhile.

A curated agent configuration on macOS​

On Linux a supervised run gets only the toolkit's skills and no MCP servers. On macOS that configuration cannot sign in, so runs inherit your own Claude Code setup until a non-default configuration can authenticate there.

Deliberately not planned​

Commanding Orion from Slack​

A Slack app with socket mode is a long-running process with tokens to protect, too much attack surface for a single-user supervisor. Drive Orion from a Claude session with a Slack MCP server instead.

GitHub's merge queue​

Orion runs its own landing queue so it can batch, isolate a culprit and hand it back to an agent (ADR 0011).

spec-kit's workflow engine, extension hooks and bundles​

spec-kit's commands run inside Orion's stages; the parts that would decide what runs next do not (ADR 0021).

Superpowers as a dependency​

Its /execute-plan wants to drive the sequence itself. Three of its ideas, red before green among them, were adopted natively (ADR 0002).

A database for config and logs​

They stay plain files and Orion stays a single static binary (ADR 0004).

The reasoning is in the architecture decisions.