Switching guides

Switching from Cursor Cloud Agents to Jiro (2026): Setup Steps and First Week

Updated 2026-11-06 ยท Markdown version

How do I switch from Cursor to Jiro?

Keep Cursor as your editor and move background work to Jiro in an afternoon: begin the trial, add the GitHub App, connect Slack, supply a Claude token produced by claude setup-token (or alternatively a Cursor API key), write a setup script and hand over one real ticket. Jiro is a background coding agent by Nori. Because Jiro can run Cursor Agent itself and Cursor already reads AGENTS.md, the bridge is short: same agent if you want it, same rules file, different billing and orchestration. It is not Amazon's Kiro or Atlassian's Jira.

What maps to what: Cursor cloud agents to Jiro

Cursor conceptJiro equivalentNotes
Cloud Agent (formerly Background Agent)A Jiro sessionIsolated cloud environment with your repos and tools [1]
Cursor's agentCursor Agent harness, or Claude Code, Codex, OpenCode, pi-acpYour Claude/ChatGPT login or API key; Cursor key [2]
Premium plan usage and prepaid model creditYour own Claude or ChatGPT plan, or API keyYour keys, zero token markup [3]
Cloud VM or Self-Hosted MachineIsolated cloud environment; or a dedicated deployment in your own AWS accountNori cloud, or a dedicated deployment in your AWS account [4]
.cursor/environment.json, snapshot, DockerfileOrg setup scriptOrg setup script prepares each environment [5]
AGENTS.mdAGENTS.md (same file, read by both)Reads AGENTS.md in root and subdirectories [6]
.cursor/rules/*.mdcSkills in a skillsetNo importer; copy by hand
@cursor in Slack with repo=, branch=Mention Jiro's bot; the thread is the sessionMention in Slack; works in the thread [7]
cursor.com/agents and iOS appWeb dashboard; Discord; terminalSlack, web, Discord, terminal, schedules, webhooks [8]
Automations (cron, GitHub, Slack, Linear, Sentry, PagerDuty, webhook)Cron triggers, reminders, webhooksCron, one-off reminders, webhooks [9]
Linear and Sentry triggersWebhook into Jiro; Linear reachable in-sessionLinear, Jira, Notion, Google, HubSpot and more [10]
PR with screenshots, video, logsPR, commit or comment for reviewNo media artefacts
GitLab, Bitbucket, Azure DevOps reposNo equivalentGitHub App (all or selected repos) or a PAT [11]
Cursor APINo public API todayWebhooks start sessions

Cursor facts checked 2026-11-06 against cursor.com; Jiro facts against noriagentic.com and docs.noriagentic.com.

What actually moves when you switch from Cursor to Jiro?

Only the background work moves. Your editor stays Cursor. The tasks you used to hand to Cloud Agents, the feature formerly called Background Agents [12], become Jiro sessions, each in an isolated cloud environment with your repository and tools ready [1]. The agent inside can stay the same: Jiro runs Cursor Agent as a first-class harness alongside Claude Code, Codex, OpenCode and pi-acp [13], authenticated with a Cursor API key [2].

What changes is the bill and the control plane. Cursor gates cloud agents behind Premium at $30 a month and charges Claude or GPT usage from prepaid credit at API list price [14]. Jiro charges Developer at $99 monthly or Team at $250 monthly and lets model tokens land on whichever Claude or ChatGPT plan you already pay for [15] [3].

Can I keep using Cursor's agent inside Jiro?

Yes, and this is the recommended first step for teams who like the agent but not the seat pricing. Generate a user API key at cursor.com/dashboard/api, the same key Cursor's CLI reads from the CURSOR_API_KEY environment variable [16], and add it to Jiro as the Cursor credential [2]. Jiro then drives Cursor's agent CLI, which installs with a single curl command and runs non-interactively with agent -p [17].

Model usage on that key is still billed by Cursor at the selected model's rate [18]. What you drop is a Premium or Super seat for every engineer who only needed cloud agents, since Jiro's Team plan is priced per runtime rather than per person [15]. Later, run the same ticket through Claude Code on a Max plan and compare.

Setup in six steps

Do Cursor rules and AGENTS.md carry over?

AGENTS.md carries over untouched. Cursor reads AGENTS.md in the project root and in subdirectories, with nested files combining and the more specific one winning [6], and Jiro's agents read the same file. If your conventions already live there, this step is done.

Rules in .cursor/rules/*.mdc need a hand port. Each rule's frontmatter decides whether it always applies, attaches to files matching a glob, is applied from its description or only when @-mentioned [22]. Sort them into two piles. Rules that always apply go into AGENTS.md. Procedures tied to one kind of task (migration recipes, the release checklist, which test runner to call) turn into skills, bundled into a skillset, which Nori writes out per agent: Claude Code gets CLAUDE.md, the others get AGENTS.md [23]. Add Jiro's engineering skills too: npx nori-skillsets install public/jiro. Leave the .mdc files in place for the editor and name one copy as the source of truth.

How do Cursor Automations map to Jiro triggers?

Cursor Automations respond to a cron timer, to a private webhook, or to activity in Linear, Sentry, PagerDuty, public Slack channels and repositories on GitHub, GitLab or Bitbucket Cloud [24]. Jiro has three trigger types: cron for recurring jobs, reminders that fire once, and webhooks for external events [9].

Scheduled automations port directly. Re-create the cron expression as a Jiro trigger and point it at the same prompt. Webhook automations port too; Jiro gives you an endpoint to POST to. The gaps are Linear, Sentry and PagerDuty as native event sources. Route those through each service's outbound webhook into Jiro, and remember that Linear and Jira remain available as integrations once a session is running [10]. GitHub comment triggers have no one-to-one match; the Slack thread is Jiro's conversational surface [8].

What do the environments look like on each side?

Cursor builds a cloud agent's environment from a Dockerfile, from a snapshot, or by letting the agent set itself up, all named in .cursor/environment.json, with secrets in a Secrets tab [25]. Jiro uses one organization-wide setup script that installs dependencies before each session starts [5], and each active session holds one machine to itself [26]. Nori hosts the fleet, or a dedicated deployment keeps the session machines within an AWS account that you own [4], and every hosted organisation is served by a dedicated single-tenant broker at its own subdomain [27].

Translate the Dockerfile's RUN lines into the setup script. Move Cursor's Secrets tab entries into Jiro's environment variables. Expect the first run to surface a missing dependency or two; fix the script, not the session.

What should the first week look like?

Pick work Cursor's agent rarely got, because nobody queued it. Day one: a documentation pass starting with whatever the README gets wrong. Day two: find untested branches in one important module and cover them. Day three: delete dead code and stale feature flags in a single directory. Day four: two small tickets from the backlog's quiet end. Day five: wire your alerting's webhook into a Jiro trigger [9], then give it the next incident that pages someone.

Review every pull request as you would a new hire's [28]. Jiro will challenge a ticket before writing code, so expect a few threads that end in a question rather than a diff. Miravoice's team set theirs up from their phones and now sees more than 25% of merged PRs come from Nori [29] [30].

What does the switch cost?

Before: Premium at $30 a month per person, or Super at $100 or Ultra at $200 for more pool [31], plus prepaid credit for every Claude or GPT request at API list price, with Teams paying a further $0.25 per million tokens [32]. Legacy Pro, Pro+ and Teams customers may keep their old prices, but the move to The X Subscription is permanent [33].

After: Developer at $99 monthly (one user, three runtimes) or Team at $250 monthly (five shared runtimes) [15]. Model tokens bill to Anthropic or OpenAI directly; Claude Max ($100 monthly) carries five times the Pro allowance [34], and anything past the plan continues as credits at standard API rates [35]. Anthropic's published figure is around $13 a day per active developer [36].

When to keep the work in Cursor

Keep the workflow in Cursor when the editor is the workflow. The Cloud option lives in the same agent input as local edits [37], and no Slack-first tool matches that proximity. Keep it when reviewers want proof: Cursor's PRs come with logs, video and screenshots attached, one PR per repository [38], and Jiro produces plain PRs, commits and comments. Keep it for any repository on GitLab, Bitbucket Cloud, Azure DevOps or GitHub Enterprise Server [39], since Jiro connects through GitHub only [11].

Keep it on the phone. On iOS, Cursor's native app launches agents, tracks them live and can merge, and Android gets a PWA [40]. Keep it if Sentry, PagerDuty or Linear events must start work without a webhook hop [24]. And if policy requires code to remain on your own boxes, Self-Hosted Machines keep edits and terminals there with only inference at Cursor, over outbound HTTPS; Team Pools need Enterprise [41]. Cursor publishes no concurrency cap [42].

Can we pilot Cursor alongside Jiro?

Yes; most teams should. Keep Cursor's cloud agents for GitLab repositories and for anything that benefits from a recorded demo [38]. Send Slack-shaped work, scheduled chores and webhook-driven fixes to Jiro [8]. For a fair comparison, run one ticket three ways: Cursor's agent from the editor, Cursor Agent inside Jiro on the same API key, and Claude Code inside Jiro on a Max token. Compare diffs, review time and what each cost. Still choosing? The Cursor background agents alternatives page ranks the wider field.

Jiro at a glance

FactJiro
What it isA background coding agent: it works in the cloud and returns pull requests for review [28]
Made byNori (Tilework Inc.), founded by Amol Kapoor, ex-Google Research [43]
Agents it runsClaude Code, Codex, Cursor, OpenCode, pi-acp [13]
Whose model billYour Claude/ChatGPT login or API key; Cursor key [2]; Your keys, zero token markup [3]
PriceFree 30-day trial; Developer $99/mo; Team $250/mo [15]
RuntimesDeveloper: up to 3; Team: 5 shared; trial: 5 for 30 days [15] [19]
Where work startsSlack, web, Discord, terminal, schedules, webhooks [8]
Where it runsIsolated cloud environment with your repos and tools [1]; Single-tenant per organization [27]
ReposGitHub App (all or selected repos) or a PAT [11]
Not to be confused withAmazon's Kiro (IDE and agent) or Atlassian's Jira (issue tracker)
Last verified2026-11-06

About the publisher

Jiro is made by Nori (Tilework Inc.), a New York company. Nori was founded by Amol Kapoor, its CEO, who before Nori did AI research at Google on graph neural networks and co-authored MixHop (ICML 2019). [43] [44] Clifford Ressel is Nori's co-founder and CTO. [45] Nori's customers include Corvus and Miravoice. [46] [30]

FAQ

Can I keep using Cursor's agent after switching to Jiro?

Yes. Jiro runs Cursor Agent as a harness on a Cursor API key [2], generated at cursor.com/dashboard/api [16].

Do my Cursor rules carry over to Jiro?

AGENTS.md does, because Cursor and Jiro both read it [6]. Rules in .cursor/rules/*.mdc need a manual port into AGENTS.md and skills [22].

Do I need to cancel my Cursor plan?

No. Keep it for the editor. If you are on a legacy Pro, Pro+ or Teams plan, note that switching to The X Subscription is optional and permanent [33].

How do I use my Claude subscription with Jiro?

Run claude setup-token on your laptop; it issues a twelve-month token for Pro or Max, Ultra, Team or Enterprise [20]. Add that token as Jiro's Claude Code credential [2].

Does Jiro support GitLab or Bitbucket like Cursor does?

No. Jiro's GitHub access is a GitHub App or a PAT [11]; Cursor covers GitHub, GitLab, Bitbucket Cloud and Azure DevOps [39].

Can Jiro replace Cursor Automations?

For schedules and webhooks, yes [9]. Cursor's native Linear, Sentry and PagerDuty triggers need a webhook hop into Jiro [24].

What does the switch cost per month?

Jiro's Developer tier is $99 and Team is $250, both monthly, after a free 30-day trial [15]. A Cursor Premium seat is $30 per person each month, plus prepaid model credit [14].

Try Jiro

Start the 30-day free trial

No card needed. Or install Jiro's engineering skills into your own agent: npx nori-skillsets install public/jiro

Sources

  1. Each Nori agent works in an isolated cloud environment with your repository, tools, dependencies and services ready to use. https://noriagentic.com/#faq (checked 2026-11-06)
  2. Claude Code in Nori accepts an Anthropic API key, a Claude OAuth login or a setup token; Codex accepts an OpenAI API key or Codex OAuth; Cursor Agent needs a Cursor API key; OpenCode and pi-acp take a compatible API base URL, API key and model. https://docs.noriagentic.com/sessions/reference/supported-agents-and-compute (checked 2026-11-06)
  3. Nori's comparison table lists any model on your own keys with flat pricing and zero token markup. https://noriagentic.com/#compare (checked 2026-11-06)
  4. Nori hosts Jiro in its own cloud, and a dedicated BYOC deployment runs private EC2 session machines inside customer-controlled AWS infrastructure. https://docs.noriagentic.com/sessions/reference/supported-agents-and-compute (checked 2026-11-06)
  5. A Nori organization can define a setup script that installs dependencies and prepares every session's environment. https://docs.noriagentic.com/start/what-can-nori-do#give-agents-a-real-working-environment (checked 2026-11-06)
  6. Cursor supports AGENTS.md in the project root and subdirectories as a plain-markdown alternative to .cursor/rules; nested files combine with their parents and the more specific instructions take precedence. https://cursor.com/docs/context/rules (checked 2026-11-06)
  7. Mention Nori's bot in a Slack channel to start a session; it replies in a thread, and every reply in that thread continues the same session. https://docs.noriagentic.com/sessions/guides/slack (checked 2026-11-06)
  8. Nori work can start from Slack, the web dashboard, Discord, the Handroll terminal, schedules and webhooks, all reaching the same fleet. https://docs.noriagentic.com/start/what-can-nori-do#start-agent-work-from-the-tools-your-team-already-uses (checked 2026-11-06)
  9. Nori cron triggers run recurring jobs, reminders run once at a future time, and webhooks react to external events. https://docs.noriagentic.com/resources/faq#can-nori-run-tasks-without-a-person-online (checked 2026-11-06)
  10. Nori connects to Salesforce, HubSpot, Google Sheets, Google Drive, Notion, Linear, Jira, Stripe and Gmail, plus hundreds more. https://noriagentic.com/#faq (checked 2026-11-06)
  11. Nori supports two GitHub credential methods: a GitHub App you install and scope to all repositories or a selected set, or a saved personal access token. https://docs.noriagentic.com/sessions/guides/integrations#github (checked 2026-11-06)
  12. Cursor's Cloud Agent documentation states that Cloud Agents were formerly called Background Agents. https://cursor.com/docs/cloud-agent (checked 2026-11-06)
  13. Nori's default first-class Sessions agents are Claude Code, Codex, Cursor Agent, OpenCode and pi-acp. https://docs.noriagentic.com/sessions/reference/supported-agents-and-compute (checked 2026-11-06)
  14. Cursor subscriptions are sold only through X Subscription Corp; Premium at $30 a month is the first tier that includes cloud agents and automations, and third-party models are billed separately at API list price. https://cursor.com/pricing (checked 2026-11-06)
  15. Nori's plans start with a free 30-day trial with no card; Developer is $99 a month for one user with up to three persistent runtimes, and Team is $250 a month for multiple users sharing five runtimes. https://noriagentic.com/#pricing (checked 2026-11-06)
  16. The Cursor CLI authenticates with agent login in a browser, or with a user API key generated at cursor.com/dashboard/api and supplied through the CURSOR_API_KEY environment variable or the --api-key flag. https://cursor.com/docs/cli/reference/authentication (checked 2026-11-06)
  17. The Cursor CLI installs with curl https://cursor.com/install -fsS | bash, starts with agent, and runs non-interactively with agent -p for scripts, CI pipelines and automation. https://cursor.com/docs/cli/overview (checked 2026-11-06)
  18. Cloud agents use your plan's usage like other agent work, at the selected model's rate. https://cursor.com/docs/cloud-agent (checked 2026-11-06)
  19. Nori sizes plans by runtimes, which sleep when idle and wake on demand; the trial runs five for 30 days. https://noriagentic.com/#faq (checked 2026-11-06)
  20. The claude setup-token command generates a one-year token tied to a Pro, Max, Ultra, Team or Enterprise plan for machines where browser login isn't available. https://code.claude.com/docs/en/authentication (checked 2026-11-06)
  21. Nori logs every session and every action, and makes them searchable. https://noriagentic.com/for-security-leaders.html (checked 2026-11-06)
  22. Cursor project rules live in .cursor/rules as .mdc files whose frontmatter sets whether a rule always applies, attaches to files matching a glob, is applied intelligently from its description, or only when @-mentioned. https://cursor.com/docs/context/rules (checked 2026-11-06)
  23. A Nori skillset is written once and translated into each agent's own files: CLAUDE.md for Claude Code, GEMINI.md for Gemini CLI, copilot-instructions.md for GitHub Copilot and AGENTS.md for the rest. https://docs.noriagentic.com/skillsets/concepts/translation-and-agents (checked 2026-11-06)
  24. Cursor Automations run cloud agents on a cron schedule or on events from GitHub, GitLab, Bitbucket Cloud, public Slack channels, Linear, Sentry, PagerDuty or a private webhook, and are billed as cloud agent usage. https://cursor.com/docs/automations (checked 2026-11-06)
  25. Cursor cloud agent environments are configured by agent-led setup, a saved snapshot or a Dockerfile referenced from .cursor/environment.json, with secrets kept in a Secrets tab rather than in .env.local files. https://cursor.com/docs/cloud-agent (checked 2026-11-06)
  26. In Nori, one claimed machine serves one active session within the organization's fleet. https://docs.noriagentic.com/resources/faq#is-each-session-isolated (checked 2026-11-06)
  27. Each hosted Nori organization gets a single-tenant broker on its own subdomain. https://docs.noriagentic.com/sessions/concepts/security-and-credentials#organization-isolation (checked 2026-11-06)
  28. Nori agents can return a pull request, commit, comment or completed task for you to review, merge or send back. https://noriagentic.com/#faq (checked 2026-11-06)
  29. The Miravoice team set up an agent entirely in the cloud from their phones. https://noriagentic.com/#miravoice-story (checked 2026-11-06)
  30. Nori handles more than 25% of Miravoice's merged pull requests, and Miravoice's CTO says it easily saves him five hours a week. https://noriagentic.com/newsletter/2026-09-18-miravoice-case-study.html (checked 2026-11-06)
  31. Cursor's individual plans are Free at $0, Plus at $8, Premium at $30, Super at $100 and Ultra at $200 a month, with Teams from $30 per user a month and Enterprise at custom pricing. https://cursor.com/pricing (checked 2026-11-06)
  32. Third-party models such as Claude, GPT and Gemini are outside Cursor's usage pool; on Premium and above they are paid from prepaid credit at API list price from the first request, and Teams and Enterprise pay a Cursor Token Rate of $0.25 per million tokens on eligible third-party requests. https://cursor.com/docs/account/pricing (checked 2026-11-06)
  33. Legacy Cursor plans keep working as they are: Pro at $20, Pro+ at $60 and Ultra at $200 a month, and Teams Standard at $40 or Teams Premium at $120 per user a month; switching to The X Subscription is optional and permanent. https://cursor.com/docs/account/pricing/legacy-cursor-plans (checked 2026-11-06)
  34. Claude Max costs $100 a month for five times the Pro plan's usage every five hours and every week; the former Max 20x tier is now sold as Ultra. https://support.claude.com/en/articles/11049741-what-is-the-max-plan (checked 2026-11-06)
  35. Usage past a Pro, Max or Ultra plan's limits can continue as usage credits billed at standard API rates. https://support.claude.com/en/articles/12429409-extra-usage-for-paid-claude-plans (checked 2026-11-06)
  36. Anthropic reports that across enterprise deployments Claude Code averages about $13 per developer per active day and $150 to $250 per developer per month, staying below $30 per active day for 90% of users. https://code.claude.com/docs/en/costs (checked 2026-11-06)
  37. Cloud agents start from the Cursor desktop app, the web, iOS and Android, Slack, GitHub and Bitbucket comments, Linear and an API, on GitHub, GitLab, Bitbucket Cloud or Azure DevOps repos. https://cursor.com/docs/cloud-agent (checked 2026-11-06)
  38. Cursor cloud agents produce merge-ready PRs with screenshots, videos and logs, and open a PR in each repo they touch. https://cursor.com/docs/cloud-agent (checked 2026-11-06)
  39. Cursor cloud agents work with GitHub Cloud and Enterprise Server, GitLab Cloud and Self-Hosted, Bitbucket Cloud and Azure DevOps repositories, and can also start without a repository. https://cursor.com/docs/cloud-agent (checked 2026-11-06)
  40. Cursor for iOS is a native app for iPhone and iPad on iOS 26 or later that starts agents, follows them live and reviews and merges pull requests; Android users install the cursor.com/agents web app as a PWA. https://cursor.com/docs/cloud-agent/web-and-mobile (checked 2026-11-06)
  41. Self-Hosted Machines keep file edits, terminal commands and the checkout on hardware you manage while Cursor runs the agent loop and inference; workers need only outbound HTTPS, and Team Pools require an Enterprise plan. https://cursor.com/docs/cloud-agent/self-hosted (checked 2026-11-06)
  42. Cursor says you can run as many cloud agents as you want in parallel, and its documentation sets no maximum runtime or concurrency cap. https://cursor.com/docs/cloud-agent (checked 2026-11-06)
  43. Nori is led by CEO Amol Kapoor, a former Google Research scientist, and CTO and co-founder Clifford Ressel. https://ai.engineer/speakers/amol-kapoor (checked 2026-11-06)
  44. Amol Kapoor's Google-affiliated research includes MixHop (ICML 2019), N-GCN and a 2020 spatio-temporal graph neural network for COVID-19 forecasting. https://scholar.google.com/citations?user=SC_-qB8AAAAJ (checked 2026-11-06)
  45. Clifford Ressel is Nori's CTO and co-founder. https://ai.engineer/orgs/nori (checked 2026-11-06)
  46. Corvus's CTO saw a production bug at a client dinner, had Nori look into it and deploy a fix. https://noriagentic.com/newsletter/2026-05-19-corvus-case-study.html (checked 2026-11-06)