Skip to content

Current capabilities

This documentation describes the current development tree. Local builds and package tests do not establish that a version is available from the public registry. Follow Installation for source use and release prerequisites.

Implemented framework behavior

AreaAvailable behavior
ProjectsInitialization, local service lifecycle, configuration, package installation and diagnostics
Workflow executionESM loading, Stage initialization, Code/Agent Steps, outcome routing, human interaction, cancellation
Execution pathsProject-configured service models and external MCP client Agent tasks
Formal StorageFile and SQLite backends, atomic operation batches, Artifact/Record queries
RecoveryCheckpoints, safe Step boundaries, and explicit Code interaction recovery
AuthoringYAML definitions, SDK contracts, Tools and Skills, compiled JS/declarations and assets
ClientsCLI, generic MCP, Codex profile, and trusted Node.js ProjectClient

The compiled Workflow protocol is 2026-10-08. It is separate from npm package versions. Rebuild and reinstall packages targeting an older protocol.

Boundaries to account for

  • Real model behavior must be validated with the intended provider, endpoint, model, and workflow. Configuration readiness does not call a model or prove successful reasoning or Tool use.
  • A real Codex MCP session has completed a four-stage package workflow. This does not establish desktop native-form usability, all MCP clients, or every model configuration. A separate real service-model attempt failed after output truncation.
  • Active client Agent tasks and uncertain in-flight effects do not resume after a host restart. Code waits need an explicit recover function. See Recovery.
  • Studio is planned. A Node.js client contract for a future UI is available; a finished Studio application is not.
  • Hot reload, automatic package upgrades, automatic storage-backend migration, and automatic replay of failed Runs are not provided.
  • Project file and command capabilities run with the host process's authority. They are not an operating-system sandbox.

Runtime compatibility

Package engines target Node.js 24 or later. Node.js 24 is the baseline used for the full local CLI/MCP acceptance. Verify the commands executed by your Workflow on the Node version actually inherited by the host. In particular, do not copy the Node 24 --experimental-transform-types option into a Node 26 command: Node 26 rejects it.

Use the installed CLI's --version and --help when comparing a deployed environment to these development docs. Restart an existing host after upgrading the CLI; an already running process continues using its loaded resources.