StepCode

Step Code runs in your terminal and handles the full task loop—reading code, making changes, and running tests. It works with the Step provider and discovers the available Step models after sign-in. MCP servers, Agent Skills, plugins, and multi-agent orchestration work out of the box; you can delegate long-running tasks to /goal and let Step Code drive them forward autonomously.

Step Code comes with built-in StepPage publishing. Once your local page is ready, you can publish it as an accessible static website with a single command—bringing development, debugging, and delivery all within the same terminal.

Why Step Code

- Token efficiency — tuned alongside Step models to consume fewer tokens for the same task; Long-horizon tasks are split across parallel subagents, each with its own isolated context, so redundant content never enters the main conversation.

- Static site publishing — the built-in steppage plugin publishes a local directory to a shareable static URL in one command, with version management and rollback.

- Long-running task delegation — /goal hands an objective to Step Code, which works toward it autonomously, and /cron runs on a schedule; the status line shows a live timer for the active task.

- Step provider access — sign in with a Step Plan account or use a Step Platform API key; switch among the models returned by Step in /model.

- Ecosystem compatibility — MCP servers and Agent Skills work out of the box, and most Claude Code plugins are directly compatible.