Compatibility

Nylorun publishes two npm channels. Both channels may point to versions with a -beta suffix while the product is pre-1.0.

Latest

Use latest for the default npm release—the most recently promoted package set:

npm create @nylorun/agent@latest my-agent

Checked against the npm registry on 2026-09-24:

This family publishes manifest schema 4 and durable engine hosted-2. It does not include agents used as tools.

Before 1.0, a release on latest can still have a version such as 0.17.0-beta. The suffix describes product maturity; the npm channel describes whether the release is a candidate or the default install target.

Beta

Use beta to try the newest candidate stack while it is being tested and promoted:

npm create @nylorun/agent@beta my-agent

Checked against the npm registry on 2026-09-24 (matches harness main):

This family keeps manifest schema 4 and durable engine hosted-2, and adds subagents (put an Agent in tools). Public docs on this site describe that published beta set.

Beta releases may change before they are promoted.

Shared rules

Protocol version remains 1. Package versions are independent. Do not use an unlabeled shorthand such as “0.17 / 0.8.” Upgrade that set together.

npm never published @nylorun/harness@0.14.0-beta; the local-runtime and package-split work shipped as 0.15.0-beta.

Keep the stack compatible

Creator pins versions that are tested together. Prefer creating a fresh project with the channel you want. When upgrading an existing project:

1. Upgrade the Nylorun packages as a set rather than choosing unrelated versions.
2. Review migrations and generated-project changes.
3. Run typecheck and tests, then exercise agent discovery and a Studio session before treating the host as ready.

Next step

Use the Quickstart for the current latest flow, or migrate from 0.15 if you still have the 0.15 hook and nylorun start surface.