Changes and status

This page is for developers who build on instruction.md or run its packages. It lists what is in beta, what keeps working when names change, each package's releases, the commands that were renamed, the protocol changes, and what is built but not switched on yet.

Status

instruction.md runs one MCP server, at https://instruction.md/mcp, and the editor, the docs and the pages at https://instruction.md. There is no public status page yet. If something doesn't work, check Troubleshooting first, then send a request.

A change to the service ships when it is ready. A change you have to act on, such as signing in again, is listed under its package below and, for people, in What's new.

What beta means

Beta means the feature is in production and you can use it, but it is not final: its behaviour can still change. The docs mark it with a Beta note.

Plans and prices are not marked beta, but their figures in billing/plans.json are defaults that can still change, and paid plans can't be bought yet (see Coming). Rate and size limits always shows the figures in force.

What keeps working

These promises come from how the code behaves today:

  • Old command names keep working. A renamed command or option value is still accepted under its old name. Hook settings and scripts written before a rename don't need to change. The old names are listed only on this page.
  • Moved commands are handed over. instruction passes a command that moved to @instruction.md/agents on to it, with the same arguments, standard input and output, and exit code. See Renamed and moved commands.
  • The renderer is stable within 1.x. render@1.js and render@1.classic.js always serve the newest 1.x release, currently 1.1.0. Nothing that works in an earlier 1.x release stops working. Each release also has an address of its own that never changes. See Embed and preview.
  • Library exports marked internal have no stability promise. instruction.md/cli and instruction.md/cli/registry exist for @instruction.md/agents to build on. Don't depend on them.

Package releases

Each package ships its full changelog as CHANGELOG.md in the npm package. This is a summary, newest first.

instruction.md

The instruction command (npm i -g instruction.md). Reference: CLI.

  • 0.11.2, 2026-11-21. The README was rewritten, and SECURITY.md and CONTRIBUTING.md ship in the package. It needs Node.js 20.19 or later.
  • 0.11.1, 2026-11-21. conversationSealer seals and opens a sealed deployment's conversation with the machine's key, for runners. It needs @instruction.md/seal 0.2.0.
  • 0.11.0, 2026-11-21. Sealed instructions. A version that arrives sealed is opened with this machine's key before anything follows it: INSTRUCTION_MD_SEAL_KEY_FILE, INSTRUCTION_MD_SEAL_KEY_COMMAND, or your own key with INSTRUCTION_MD_SEAL_PASSPHRASE or INSTRUCTION_MD_SEAL_RECOVERY. Without a key, the version is held back with the reason, and never passed on encrypted. instruction pull, instruction watch and the agents' hooks all work this way.
  • 0.10.2, 2026-11-21. instruction agents follow, install, run and check pass through to @instruction.md/agents.
  • 0.10.1, 2026-11-21. instruction agents <command> runs the @instruction.md/agents command: the installed instruction-agents, else npx --yes @instruction.md/agents. instruction agents list, create, rotate and revoke (an organization's agent credentials) stay in this package.
  • 0.10.0, 2026-11-21. The agent side moved to its own package, @instruction.md/agents. The moved commands are handed over (see below). The instruction.md/agent and instruction.md/pi exports moved to @instruction.md/agents/agent and @instruction.md/agents/pi. Plain instruction connect --host H, login, mcp, watch and the rest stay here.
  • 0.9.0, 2026-11-21. The runner became Claude Code's host for claude -p "…": permission requests and questions become cards for the people who answer for the agent, and their answers go back to Claude Code. Values that look like keys, tokens or passwords in a tool's input are masked before they leave the machine.
  • 0.8.0, 2026-11-20. Agents set up from their instruction: applying an instruction's MCP servers and skills into Claude Code's and Codex's own files, accounts, credential headers, signing in to MCP servers, and a check of what stops an agent. These commands are now instruction agents apply, accounts, credential, signin and check.
  • 0.7.0, 2026-11-19. One agent per deployment: the runner starts, stops and restarts agents as a deployment rule's deployments change. Now instruction agents run.
  • 0.6.0, 2026-11-19. pi, Amp and Agent Client Protocol agents; hooks for Gemini CLI, Antigravity, Qwen Code, Factory Droid, Devin, GitHub Copilot CLI, Cursor, Kiro, Cline, Junie, Crush and Goose; instruction watch --out FILE --rule for Cursor.
  • 0.5.0, 2026-11-19. Instructions in Claude Code and Codex: the hook, project setup with .instruction/follow.json, instruction watch --out, --block and --lines, instruction pull --out and --delivered, instruction mcp --follow, and writing an instruction as a Claude Code agent or skill or a Codex skill.
  • 0.4.0, 2026-11-11. The first release on npm. instruction login signs you in in your browser, or with a code on another device with --device. Everyone signed in once more, and older versions of the CLI can no longer sign in. Administering an organization asks for its permission only when needed (instruction login --admin asks up front). --issuer is no longer needed: the CLI finds where to sign in from the server.

@instruction.md/agents

The agent side: following, running and setting up agents (instruction agents …, or npx -y @instruction.md/agents … with nothing installed). Reference: instruction-agents command reference.

  • 0.4.3, 2026-11-21. The README was rewritten, with SECURITY.md and CONTRIBUTING.md in the package. It needs Node.js 20.19 or later.
  • 0.4.2, 2026-11-21. Sealed agent conversations. For an agent following a sealed instruction, instruction agents run seals every line, question, permission, error and subagent name it reports, and opens the answers and messages that come back, with the machine's key. The hook opens people's messages before the agent gets them. The server refuses such a conversation if it arrives unsealed.
  • 0.4.1, 2026-11-21. Sealed instructions reach an agent's hooks and run opened with the machine's key, or are held back with the reason.
  • 0.4.0, 2026-11-21. instruction agents run --remote-control -- claude -p "<task>": each agent is a Claude Code session you control in the Claude app. It needs a claude.ai sign-in (not an API key), Linux or macOS, and is not available with --once. See Deployments. Agents now start without Claude Code's own session variables, so a runner started inside a Claude Code session no longer hands its agents that session.
  • 0.3.0, 2026-11-21. The commands were renamed for what an agent does (see below). --host is always the agent's app and --as what the instruction becomes.
  • 0.2.0, 2026-11-21. Subagents: the runner reports each subagent an agent starts, and marks each line a subagent said or ran as its own.
  • 0.1.0, 2026-11-21. The first release, split out of instruction.md 0.10.0. Hook settings now run npx -y @instruction.md/agents hook <host>. Setting a project up again turns an earlier npx -y instruction.md hook <host> into this one, never a second hook beside it.

@instruction.md/mcp

The MCP server for sealed instructions (instruction-mcp). Reference: instruction-mcp command reference.

  • 0.1.1, 2026-11-21. The README was rewritten, with SECURITY.md and CONTRIBUTING.md in the package. It needs Node.js 20.19 or later. --allow-domain now counts only an email address the identity provider verified. 0.1.0 matched any email address an account had.

@instruction.md/seal

The cryptography of sealed workspaces. Reference: Sealed cryptography and threat model.

  • 0.2.1, 2026-11-21. The README was rewritten, with SECURITY.md and CONTRIBUTING.md in the package. It needs Node.js 20.19 or later.
  • 0.2.0, 2026-11-21. A new envelope kind, message, for one item of a sealed deployment's conversation. Envelopes made by 0.1.0 open as before. A 0.1.0 reader refuses a message envelope.
  • 0.1.0, 2026-11-21. The first release: X-Wing (X25519 and ML-KEM-768) HPKE key wrapping, envelopes with key commitment and author signatures, workspace keys in epochs, and unlock methods.

The Rust crate and the VS Code extension

The Rust crate instruction-md (0.6.1, 2026-11-21) and the VS Code extension (0.2.0, 2026-10-30) keep their own changelogs: sdks/rust/CHANGELOG.md and apps/vscode/CHANGELOG.md in the repository. See Rust and VS Code.

The renderer

The script that draws an instruction on any page (https://instruction.md/render@1.classic.js). Reference: Embed and preview. Its releases, from the renderer's own list:

  • 1.1.0, 2026-11-17. The renderer's own words (Contents, Parameters, a rule's label) in Ukrainian, French, Spanish and Arabic, chosen by the lang attribute or the page's own lang. The document's text is never translated.
  • 1.0.1, 2026-11-16. Right-to-left pages: the layout follows the direction the page runs, prose takes its own direction, and code stays left to right.
  • 1.0.0, 2026-11-09. The first immutable release, at its own address with its SRI hash beside it, and its own copy of Mermaid.

Renamed and moved commands

This is the only page that shows the old names. Use the new ones in anything you write.

Renamed in @instruction.md/agents 0.3.0

UseInstead ofNote
instruction agents follow <uri> --host Hinstruction agents connect --host H <uri> --with-hooks--write and --managed are the same on both
instruction agents install <uri> --host claude-code --as agentinstruction agents sync <uri> --as claude-agent
instruction agents install <uri> --host claude-code --as skillinstruction agents sync <uri> --as claude-skill
instruction agents install <uri> --host codex --as skillinstruction agents sync <uri> --as codex-skill
instruction agents runinstruction agents fleetthe same flags
instruction agents checkinstruction agents doctorthe same flags

The old names and values still work. instruction agents --help lists them under "Earlier names still work".

Moved from instruction.md in 0.10.0

These instruction commands moved to @instruction.md/agents: hook, acp, turn, sync, fleet, apply, doctor, accounts, credential, signin. So did instruction connect with --with-hooks, --write or --managed.

instruction still accepts them and hands them over: to the installed instruction-agents if there is one, else to npx --yes @instruction.md/agents. Arguments, standard input, standard output and the exit code pass through unchanged. It says once on standard error that the command moved, except for hook, turn and credential, whose output an agent's app may show or log. A hook or turn that can't be handed over exits 0, as it would offline, so it never blocks a prompt.

Write the new form in new settings: instruction agents hook <host>, or npx -y @instruction.md/agents hook <host> in a project's committed hook settings.

Protocol changes

  • MCP 2026-07-28 only. The server speaks the 2026-07-28 version of the protocol, with no sessions. A request on the older session wire (an initialize call, an Mcp-Session-Id header, or a 2025 protocol version) is refused with HTTP 400 and JSON-RPC error -32022 (or -32600). GET, HEAD and DELETE on /mcp answer 405.
  • Clients on an older version connect through the CLI's stdio server instead: instruction mcp, which instruction connect --host cursor and --host vscode set up. See Connect an agent.
  • Live updates on Community are refused for a second consumer with JSON-RPC error -32025, whose data is the limit_reached error. See Live updates, events and webhooks and Rate and size limits.

Coming

These are built but not switched on in production, or switched on with their developer pages held back until they are checked there. When one is ready, the pages named here are rewritten, and the item moves to its package or to Protocol changes.

WhatWhat turns it onPages to rewrite
Support-led recovery: our support checks who someone is and lets them back in after they lost every passkey and recovery codeThe server's IMD_SUPPORT_RECOVERY=on with its sign-in client secret, and the sign-in realm's recovery setting. Until then a recovery answers "not available yet".Lost your passkey?
Paying for a planThe payment provider's keys on the server (IMD_STRIPE_SECRET_KEY, IMD_STRIPE_WEBHOOK_SECRET). Until then nobody can pay, and the billing tools say so.Plans, limits and billing, Plans
Company sign-in (single sign-on) set up by an organization in Developer ▸ Single sign-onOn in production, for an organization whose plan includes sso. The developer page "Single sign-on and AI clients" is held until it has been tried there.Company sign-in (single sign-on), Domains
AI clients connected through the organization's identity provider without a sign-in (enterprise-managed authorization)The sign-in service's enterpriseManagedAuth switch, which is off. Until then a client's identity assertion is refused.Company sign-in (single sign-on)
Sign in with instruction.md (Developer ▸ Apps), and agent platforms built on itOn in production: the server's apps switch (IMD_APPS=on) is set. The developer pages "Sign in with instruction.md" and "Build an agent platform on instruction.md" are held until they are checked against production.Connected apps, Your organization's rules
The legal particulars: the company's legal name and address, governing law and courts, and paid plans' money termsThe owner's final textTerms of Service, Privacy

Questions

Will my old npx instruction.md hook settings keep working?

Yes. npx -y instruction.md hook claude-code hands over to @instruction.md/agents, with the same input, output and exit code, and exits 0 if it can't start it. Running instruction agents follow <uri> --host claude-code --write again rewrites the setting to npx -y @instruction.md/agents hook claude-code. See Renamed and moved commands.

Do I have to change scripts that run instruction fleet or instruction doctor?

No. Both still work: instruction hands them over, and @instruction.md/agents still accepts fleet and doctor. Change them to instruction agents run and instruction agents check when you next edit them. See Renamed and moved commands.

Why does my MCP client get error -32022?

It is using the older session wire, which the server refuses with HTTP 400 and -32022 (some such requests get -32600). Use a client that speaks MCP 2026-07-28, or connect through instruction mcp. See Protocol changes and Connect an agent.

Which renderer release does render@1.js serve?

The newest 1.x release, currently 1.1.0. To pin one release, load its own address with its SRI hash. See Embed and preview.

Last checked against the product:

Was this page helpful? Report a problem