Let ideas reach the stars.
Windows x64 · Electron · React · TypeScript · MIT
A Windows desktop client for Step Code. It provides desktop workspaces, conversations, and session management; Step Code powers agent execution.
The original idea was to explore a community-built desktop client for Step Code while no official Step Code desktop app has been released. Given my love for StepFun, I also look forward to its official release.
- Streaming conversations, model and thinking-level selection
- Independent sessions and project workspaces, with session history and renaming
- Image attachments, tool-call confirmations, and recoverable session deletion
- Step account sign-in, MCP configuration, and resource discovery
- Chinese and English UI, with light and dark themes
The app keeps its data in a dedicated directory (%APPDATA%\Desktop for Step Code) instead of reusing a personal Step Code CLI profile. Agent execution stays with Step Code; this project does not add another harness.
Step login credentials are encrypted for the current Windows user in step-runtime/auth.dpapi. Existing desktop auth.json data is migrated on startup, and the plaintext file is removed after the encrypted copy is saved. Uninstall removes the desktop Step credential files while keeping sessions, settings and independent workspace files; signing out removes the Step credential as well. This protects against casual offline reading of the file, not software running with access to the same Windows account. Other configured MCP secrets are outside this credential migration.
If the app fails to start or the Step Code runtime exits unexpectedly, a crash-<timestamp>-<id>.log is written to %APPDATA%\Desktop for Step Code\logs\ with the app version, the startup phase, and the error. That data lives under %APPDATA% rather than the install directory, so reinstalling does not clear it; read the newest crash log before reinstalling.
The built-in StepPage MCP server cannot start on Windows: the command the upstream registers is a shell wrapper, which Windows cannot spawn directly, and the official installer is a shell script as well, which the upstream code explicitly skips on Windows. When the desktop app detects the official bundle under %USERPROFILE%\.steppage-mcp\bin\, it registers a working server on your behalf, with the command pointing at the bundled Node runtime and the argument at that bundle; authentication reuses your Step sign-in, so no extra key is needed. Publishing to StepPage has not been acceptance-tested.
This repository currently provides source code. There is no public installer on GitHub Releases yet. The installer and release timing will be decided after release acceptance; locally generated installers are not included in this repository.
Running from source requires Windows x64 and the development dependencies below. On first launch, sign in under Account Settings with your own Step Plan account or Step Platform API key, then open a local project. Git/Bash, project-specific CLI tools, and MCP server dependencies must be installed on the host separately.
Requirements: Windows x64, Git, Node.js 24.15.0 (or a compatible Node.js version >=22.19), and Corepack. Before building, fetch the pinned Step Code upstream revision in the repository root and apply the Windows/Desktop integration patch maintained here.
Run these commands in PowerShell from the repository root:
git clone https://github.com/stepfun-ai/Step-Code.git Step-Code
git -C Step-Code checkout 519e4de4ed2162d3667be1821cb92ada6b884e5a
git -C Step-Code apply ../patches/step-code-desktop.patch
Push-Location Step-Code
corepack pnpm install --frozen-lockfile
corepack pnpm build
Pop-Location
Push-Location Desktop
corepack pnpm install --frozen-lockfile
node node_modules/electron/install.js
corepack pnpm stage:runtime
corepack pnpm typecheck
corepack pnpm test
corepack pnpm build
node scripts/verify-electron.mjs
corepack pnpm devTo produce a Windows x64 installer:
corepack pnpm package
node scripts/checksums.mjsThis is a community preview; full public-release acceptance is still in progress. A disposable Windows VM exercised installation, credential migration and uninstall of a candidate build. Separately, a packaged build completed a step-5-preview coding task with desktop tool approvals on a real Step Plan account. See docs/VERIFICATION.md for the acceptance record and release scope. MCP status indicates whether configuration is enabled, not connection health.
Desktop for Step Code is licensed under MIT. Step Code and its Pi upstream components retain their respective licenses and notices.