Skip to content

Nori Compare

Continue.dev is discontinued: what should your team use instead?

Cursor acquired Continue and its repository is now read-only. What that means for teams on Continue, the replacement options, and how to move team agent work to Nori.

Quick answer

Continue has joined Cursor, and its open-source repository is no longer maintained and is read-only. Teams that used Continue for shared, repeatable agent work can move it to Nori today: Jiro or any harness, from Slack, schedules and webhooks, on their own model keys, with shared skillsets and memories. Engineers who only want an editor assistant can move to Cursor or another IDE tool.

What happened to Continue

Continue's homepage says Continue was acquired by Cursor. The repository README says it "is no longer actively maintained and is read-only for all users". Its last releases are dated June 19, 2026.

Continue status, as of November 2026.
ItemStatus
CompanyAcquired by Cursor
RepositoryRead-only, not maintained
Last releasesJune 19, 2026
LicenseApache-2.0
DocsStill online, unmaintained

The Apache-2.0 code remains available, so a team can fork it. Whether Continue's former hosted features still work cannot be established from current pages, so this page does not describe them. Check recent commits before you rely on any of them.

What you need to replace

Teams used Continue for two different jobs. Decide which one you are replacing first.

  • An editor assistant. Chat, edits and autocomplete inside VS Code or JetBrains, chosen per developer.
  • Shared agent work. Rules, prompts and model settings that a whole team reused, and checks that ran on pull requests.

The first is a per-developer tool choice. The second is a team platform choice, and it is where a cloud agent workspace helps.

Replacement options compared

Continue replacement options, as of November 2026. Vendor facts were read from each vendor's own pages on November 21, 2026.
OptionWhere it runsTeam workflowModels and price
NoriIsolated cloud sandboxesSlack, Discord, web, CLI, cron schedules and webhooks; shared skillsets and memories; Jiro or any harnessYour Claude or ChatGPT subscription, API keys or gateway; no token charges. 30-day free trial, Developer $99/month, Team from $250/month
CursorEditor, plus cloud agents on Premium and upAutomations on schedules and app eventsPremium $30/month, Super $100, Ultra $200; Free and $8 Plus exclude cloud agents
GooseYour machine or a server you runCron-scheduled recipes on that hostFree, Apache-2.0, 85+ providers
Fork ContinueWherever you run itWhatever you maintainApache-2.0; you own fixes

For more cloud options, see cloud coding agents compared and Nori vs Goose.

When to choose Nori

  • Your Continue rules were team rules. Put them in an org skillset (AGENTS.md or CLAUDE.md, skills, subagents) and every session starts with them.
  • You ran checks on pull requests. Webhook automations start a session on each PR event and post the result.
  • You want model choice. Nori runs Claude Code, Codex, Gemini CLI, OpenCode or any ACP agent on your own keys or gateway.
  • You want a teammate. Jiro plans, works test-first and reviews its own changes.

Nori deploys the full stack, control plane included, into your own AWS VPC or Azure VNet, or on-prem, with your identity provider (SAML, SCIM, OIDC), your LLM gateway and your compute. On hosted plans, Nori gives each organization a dedicated, single-tenant control plane and data store, and every session runs in its own isolated sandbox.

When to choose an editor tool alongside Nori

  • Inline autocomplete stays in the editor. Each developer keeps the editor they like, Cursor included, and Nori takes the team's shared agent work.
  • Forking Continue means owning every fix. The Apache-2.0 code lets you keep it alive yourself, and you maintain it from then on.

Most teams run both: an editor tool for each developer and Nori for the team.

How to migrate team work off Continue

  1. Export your configuration. Copy the Continue config files and rule files from each repository and from shared setups.
  2. Separate personal from team settings. Keep personal editor preferences with each developer; move shared rules forward.
  3. Start the Nori trial. Thirty days, no card.
  4. Connect the same models with API keys, your gateway, or a Claude or ChatGPT subscription.
  5. Turn rules into skills. Each reusable prompt becomes a skill in the org skillset.
  6. Recreate PR checks as webhook automations, like the one below.
name:      pull request review
trigger:   webhook  github pull_request.opened
agent:     Jiro
prompt:    Review the diff against AGENTS.md. Comment on rule violations
           and missing tests. Do not push changes.
deliver:   PR comment and Slack #eng-reviews

Frequently asked questions

Is Continue.dev shut down?

Continue was acquired by Cursor, and as of November 2026 its GitHub repository says it is no longer actively maintained and is read-only for all users. The last releases are dated June 19, 2026. Existing installs are unmaintained code.

Can I keep using Continue?

The Apache-2.0 code is still available and can be forked, but it will not receive fixes from the original team. Whether its former hosted features still work is not established by current pages, so test before you rely on them.

What is the closest replacement for Continue?

For an editor assistant, Cursor, which acquired Continue. For shared team agent work such as rules, PR checks and scheduled jobs, Nori runs Jiro or any harness in cloud sandboxes from Slack, schedules and webhooks.

Can I bring my own model keys to Nori like I did with Continue?

Yes. Nori runs every harness on your own API keys, LLM gateway, or Claude or ChatGPT subscription, and never charges for tokens.

How much does Nori cost?

Nori has a 30-day free trial with no card. Developer is $99 per month for one person and three machines. Team starts at $250 per month for five machines with unlimited members. Enterprise is custom.

Sources

Vendor pages and repositories were read on November 21, 2026. Check the linked pages before you decide.