Skip to content

See what changed—and what is actually ready.

Skopos separates implemented behavior, verified host support, and future direction so a roadmap item is never mistaken for a shipped capability.

01Source-linked changes

02Explicit verification state

03No silent compatibility claims

01
In progress

Codex-certified first release preparation

The core operating model, CLI, MCP surface, self-hosted workflow, and public website are converging toward a Codex-certified first release. Other host projections remain explicitly unverified until real-host proof exists.

02
Verified

Codex child-Task delivery

Approved splits can create real Codex tasks, bind returned thread identities to Skopos Sessions, wait for completion, and return control to the originating reviewer.

03
Verified

Fresh-session continuation

A source-linked self-hosted Codex cohort recorded three successful bounded continuations out of three eligible attempts. The result is explicitly Codex-only.

Follow the release from source to proof.

Every public claim should have a shipped artifact or a clearly stated readiness limit behind it.