stagewise: the agentic IDE whose agent works inside a browser tab
The Open Source Agentic IDE. Create and orchestrate coding agents, show app previews and run git workflows. Use your favorite models across all providers.
At a glance
- What is it?
- stagewise puts a coding agent, app previews and git workflows into one AGPLv3 IDE. What it asks for in return is a model subscription or your own provider keys, and a set of Apple and Azure signing secrets if you build it yourself.
- Who is it for?
- stagewise is a reasonable fit for a web team that wants one agent with console and debugger access to the page it is working on, and that is willing to connect a subscription or paste a provider key for models. It is a poor fit if your code changes must land in a repository through a documented command line, or if an AGPLv3 licence rules out your deployment.
- Can I use it commercially?
- Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
- Is it still maintained?
- Yes. The repository last received commits 5 days ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- stagewise-io/stagewise6,836 ★ · +25
| Repository | 2026-09-12 | 2026-11-15 |
|---|---|---|
| stagewise-io/stagewise | 6.8k | 6.8k |
25 Stars in the last 64 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The agent gets the tab's console and debugger, not just the files
stagewise describes itself as an open source agentic IDE for developers with a coding agent built right in, and its README header calls it the Agentic IDE for Open-Source Models. The distinguishing claim is access: the agent has full access to the console and debugger of your tab, which is a different job from a chat window that edits text. Browse and build in the same tool is the other half, since the page you are inspecting is the page you are editing. The feature list includes reverse engineering any website's components, style systems and color palettes, which only makes sense if the agent can look at the rendered result. The repository description adds the remaining jobs: show app previews, run git workflows, and create and orchestrate coding agents. Orchestration is named there, though the README does not describe the interface for arranging more than one.
Two kinds of edit: temporary test changes, or a connected codebase
The README splits edits by lifetime. One option is to make temporary test changes, which is how the agent proves something on the running page. The other is to connect a codebase for permanent edits, where the change has to survive a reload. That split is the real constraint on the whole product: the browser tab is the working surface, and durable work has to be routed back into a source tree you point at. IDE integration is the third piece, described as the ability to view and apply code changes in your favorite editor, so the tab does not have to be the only place you read a diff. What the README never gives is the mechanism for any of it. No file layout, no watch command, no configuration file name. The repository does carry a .stagewise/ directory and an .agents/ directory at the top level, and neither one is explained in the text.
Three account tiers, five subscription imports, one key for the rest
Tokens arrive three ways. The README notes that the stagewise account service will be sunset at the end of November 2026, and tells users to bring their own subscription or API keys instead. The Easy Import table connects a subscription you already pay for with a single API key: Kimi from Moonshot AI, Qwen Coding Plan from Alibaba DashScope, MiniMax, Xiaomi MiMo and Mistral, each giving access to every model that provider offers inside stagewise. Then Bring Your Own API Key, where OpenRouter is singled out as the single key route to 345+ models from all major vendors. The README goes further than that: you can register completely custom providers, including local inference, and define custom models yourself.
The env file shows what a real build demands
The install instruction is one sentence: download stagewise from stagewise.io and follow the short onboarding guide. What sits behind that download is spelled out in .env.example, and much of the list is not yours to supply. Apple signing needs APPLE_ID, APPLE_PASSWORD and APPLE_TEAM_ID for signing and notarization. The Windows build goes through Azure Trusted Signing with AZURE_TENANT_ID, AZURE_CLIENT_ID, AZURE_CLIENT_SECRET, AZURE_ACCOUNT_NAME, AZURE_ACCOUNT_ENDPOINT_URI and AZURE_CERTIFICATE_PROFILE_NAME. Auth endpoints sit behind a Cloudflare Turnstile site key described as an invisible CAPTCHA, and PostHog keys cover analytics and source map upload. Three URLs decide where a build talks to:
API_URL=https://preview.api.stagewise.io
LLM_PROXY_URL=https://preview.api.stagewise.io/v1/ai
UPDATE_SERVER_ORIGIN=https://dl.stagewise.ioThe same file derives the OAuth callback scheme from RELEASE_CHANNEL: stagewise:// for release, stagewise-prerelease:// for prerelease and stagewise-dev:// for dev, while Google and GitHub OAuth callbacks still point at the API auth callback URLs.
Alpha, beta and release channels are one script apart
Nightly tags sit next to stable ones. [email protected] was published on 2026-11-02, and a tag named [email protected] was published on 2026-11-02 as well. The root package.json exposes the release script as one command:
pnpm version:stagewiseIt resolves to `tsx scripts/release/index.ts --package stagewise`. A fourth script, `pnpm version:karton`, targets a different package through the same file, so the release machinery is shared across packages rather than written for stagewise alone. Version state is kept in files at the top of the repository: .release-version, .release-tag and .release-notes.md, with a .release-notes/ directory beside them. The last push was on 2026-11-01, and the repository is not archived.
One pnpm workspace, turbo filters, and biome as the gate
The root package.json is named @stagewise/workspace and marked private, and every task runs through turbo over a pnpm workspace. Development is a watch loop with a concurrency of 20:
pnpm dev
pnpm check
pnpm typecheck
pnpm testThose four map to `turbo watch dev --concurrency 20`, `biome check .`, `turbo run typecheck` and `turbo run test`. Builds are filtered per workspace, with `./apps/*` and `./packages/*` given their own scripts, and pnpm dlx sherif --fix exists for dependency consistency. The tree shows where the code sits: apps/, packages/, agent/, scripts/ and locales/, alongside biome.jsonc, tsconfig.json, turbo.json, pnpm-workspace.yaml, commitlint.config.js and lefthook.yml. Cleaning is unusually thorough, with `git clean -xdf node_modules` and two browser data scripts that call `pnpm -F stagewise clean-data`, one of them with --isolated-only. That flag is the trace to follow when a browser profile is in a bad state.
AGPLv3, a GmbH behind it, and an email for everything outside
stagewise is developed by stagewise GmbH and offered under the AGPLv3 license, with a link to the GNU licence FAQ for how that model works. The README also names the path for use cases that fall outside the scope the licence permits: a contact address, [email protected]. That sentence is short and it does not enumerate the cases, so a team that needs a different arrangement has to ask rather than read an answer. Support runs on two channels, a Discord server for conversation and GitHub issues for dev support and bugs, with an issue link for anything else. The repository also carries SECURITY.md, CONTRIBUTING.md, CONTRIBUTORS.md, VERSIONING.md and THIRD-PARTY-NOTICES.md, so policy and process exist as files even though the README summarises none of them.
The setup text is one sentence, and the rest is a product page
Getting Started is the weakest part of the documentation. Download stagewise from stagewise.io, then follow the short onboarding guide. There is no command line install, no package manager instruction for end users, and no documented way to start the IDE from source, even though the repository is a full TypeScript monorepo whose package.json carries dev, build, test and release scripts. The link in that sentence points at ade.stagewise.io while the homepage listed for the project is stagewise.io, and the difference between them is never explained. Everything after it is written for someone evaluating the product: bullet features, two provider tables with featured models, and a note that the stagewise Account is being sunset. Eleven translated READMEs live under locales/, which is more translation effort than the setup section receives. The provider names change faster than any of that text, so a reader pinning a subscription should check the table rather than trust a cached copy of the page.
Editorial conclusion
stagewise is a reasonable fit for a web team that wants one agent with console and debugger access to the page it is working on, and that is willing to connect a subscription or paste a provider key for models. It is a poor fit if your code changes must land in a repository through a documented command line, or if an AGPLv3 licence rules out your deployment. Verify two things first: that ade.stagewise.io, the download link in the setup sentence, is the build you meant to install, and that the subscription or key you connect covers the models your agent actually calls, since the stagewise account service will be sunset at the end of November 2026.
Frequently asked questions
What is stagewise?
stagewise is an open source agentic IDE written in TypeScript and offered under the AGPLv3 licence by stagewise GmbH. Its coding agent has full access to the console and debugger of your tab, and the app is downloaded from stagewise.io.
How do I use stagewise?
Download it from stagewise.io and follow the short onboarding guide. Models then come from a connected subscription such as Kimi, Qwen Coding Plan, MiniMax, Xiaomi MiMo or Mistral, or from your own API key.
Is stage wise the same thing as stagewise?
The repository is stagewise-io/stagewise and the product is called stagewise. The homepage listed for the project is stagewise.io, while the download link inside the Getting Started sentence points at ade.stagewise.io.
How does stagewise compare with VS Code?
stagewise is a browser based agentic IDE whose coding agent reaches the console and debugger of your tab, and it separately offers IDE integration to view and apply code changes in your favorite editor. The README makes no comparison with another editor.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/stagewise-io-stagewise)Star history chart for your README
[](https://hysenlabs.com/projects/stagewise-io-stagewise)Was this useful?