Skip to main content
Step Code works with files in your project directory to complete development tasks. See Step Code overview for capabilities and use cases.

​
Prerequisites

  • A Step Plan account or Step API key, and network access to the model service.
  • A project containing a README.md that you are authorized to share with the selected model service.

​
Installation

The commands execute a remote script. Verify the source first. To pin a version or uninstall, see Updates.
Open a new terminal and run step --version. Confirm that it prints the installed version.

​
First launch

Open your project, replacing the example path with its actual location:
Follow the startup prompts to sign in and choose a theme. If Step Code detects MCP configuration from another tool, it offers to import it. See Migrating from other tools for reuse options.

​
Login

  1. Enter /login in the interactive input box.
  2. Select the Step sign-in option for your account and billing channel. Choose Step Plan for a subscription on platform.stepfun.com, or Step Plan Oversea for one on platform.stepfun.ai, and authorize in the browser. For API keys, choose the Step account option that matches the key.
  3. Run /model and select a model available to the account.
In an SSH, server, or container terminal, run step login --no-browser to get an authorization link, then complete sign-in in a browser on this or another device. The command still requires an interactive terminal and does not depend on a local callback port. Subscription and pay-as-you-go requests use separate channels. See Authentication and models for endpoints, sign-in details, and other providers.

​
Check permissions

New interactive sessions without a configured permission mode default to Approve for Me: routine operations run automatically, while detected dangerous or unanalyzable commands still require confirmation. When you want confirmation before file changes and commands, run /permissions and choose Ask. Permission modes are not an OS sandbox; run Step Code only in directories you trust. See Permissions and safety for mode behavior and project access boundaries.

​
Your first conversation

Reference README.md in the input box and send a task:

​
Check the result

Compare the answer with the README. Confirm that it identifies documented commands rather than inventing missing setup steps, and inspect tool activity for actions outside the task. In a Git project, use git diff to inspect file changes. Use /quit to exit. To continue the same task later, see Sessions and context.

​
Next steps