Switching guides

Switching from Amp to Jiro (2026): What Maps to What, Setup Steps and Gotchas

Updated 2026-11-06 ยท Markdown version

How do I switch from Amp to Jiro?

Keep your AGENTS.md in the repository, start the free 30-day Jiro trial, install the GitHub App on one or two pilot repos, connect Slack, and link your Claude plan with a token from claude setup-token or your ChatGPT plan through Codex OAuth. Jiro is a background coding agent by Nori. Amp threads become Jiro sessions, orbs become runtimes, and Amp's Ship-to-main default becomes a pull request for review, so turn on branch protection before the first task. It is not Amazon's Kiro or Atlassian's Jira.

What maps to what: Amp concepts and their Jiro equivalents

AmpJiro equivalentNotes
Thread (saved, shareable conversation)Session, usually a Slack thread or web chatMention in Slack; works in the thread [1]
Orb (one remote machine per thread)Runtime: an isolated cloud environment per sessionIsolated cloud environment with your repos and tools [2]; One machine per active session [3]
Orb pause after idleRuntimes sleep when idle, wake on demandSized by runtimes; they sleep when idle [4]
Self-hosted orb providerDedicated deployment in your own AWS accountNori cloud, or a dedicated deployment in your AWS account [5]
Runner (your own laptop as compute)No equivalentJiro runs only in cloud environments
AGENTS.md in the repoSame file, read by the harnessReads AGENTS.md; falls back to CLAUDE.md [6]
Global AGENTS.md set by a workspace adminSkillset, translated per agentOne skillset, translated per agent [7]
Ship (push to base branch after tests)Pull request, commit or comment for reviewPRs, commits, comments for review [8]
Push to BranchDefault behavior; nothing to switch onEnforce with GitHub branch protection
Claude subscription via Agent SDKClaude subscription via claude setup-tokenOne-year subscription token [9]
ChatGPT subscription or API keysCodex OAuth or OpenAI API key; Cursor API key for Cursor AgentYour Claude/ChatGPT login or API key; Cursor key [10]
Agent usage creditsNo equivalent: tokens stay on your own billYour keys, zero token markup [11]
Amp CLIHandroll terminal; also Slack, web, DiscordSlack, web, Discord, terminal, schedules, webhooks [12]
Slack AI agent app (paid Slack plan)Mention the Nori bot in a channelMention in Slack; works in the thread [1]
Assign a Linear issue to AmpNo trigger from Linear; Linear is reachable as an integrationLinear, Jira, Notion, Google, HubSpot and more [13]
GitHub listeners on Amp's PRsNo direct equivalent; webhooks can start a sessionCron, one-off reminders, webhooks [14]
WorkspaceOrganization with its own single-tenant brokerSingle-tenant per organization [15]
Megawatt / GigawattDeveloper / TeamFree 30-day trial; Developer $99/mo; Team $250/mo [16]
macOS, iOS and Android appsNo equivalent; web dashboard and Slack on mobileWeb, macOS/iOS/Android, CLI, GitHub, Slack [17]

Equivalents reflect shipped features on 2026-11-06; 'no equivalent' means Jiro has no sourced counterpart.

What should you check before switching from Amp?

Check the merge path first, because it is the habit that will bite. Amp's default Ship step lands a change on the base branch once tests pass; Push to Branch is the setting that instead pushes a branch and reports the PR URL [18]. Jiro never lands on main for you. Someone has to own review from the first day.

Then the credentials. Amp has let users bring a Claude subscription since 2026-10-10, via Anthropic's Agent SDK [19], but that login is Amp's. Jiro needs its own token, which you generate on your laptop in step 5 below.

Finish or archive running Amp threads before you start. An orb pauses 5 minutes after the agent stops or 20 minutes after your last message, and archiving the thread stops it at once [20]; nothing in a thread migrates. Finally, pick one or two pilot repositories. Not the whole organization.

What carries over from Amp, and what does not?

Your repository guidance comes along untouched. Amp reads AGENTS.md from the working directory and its parents, falling back to AGENT.md or CLAUDE.md where none exists [6]. Jiro's harnesses read those same files on clone: Codex and OpenCode take AGENTS.md as-is, and Claude Code reads CLAUDE.md.

Rules that live outside a repo need a new home. Amp's workspace-level global AGENTS.md becomes a Jiro skillset: write it once and Nori emits a CLAUDE.md when the harness is Claude Code and an AGENTS.md otherwise [7]. Skillsets also carry team policy and integrations across every session [21]. If you want Jiro's own engineering habits in your repos, npx nori-skillsets install public/jiro adds them.

Threads do not migrate. Nor do orb snapshots, Puck conversations or Amp credits. Export anything you need from thread history by hand and assume the rest is gone.

How do you set up Jiro, step by step?

  1. Start the trial; 30 days, no card required [16].
  2. Add the GitHub App to the pilot repositories only, or store a personal access token [22].
  3. Protect main in each pilot repo: require a pull request and at least one approving review. Do this before step 7.
  4. Connect Slack. An @mention of the bot in a channel opens a session; replies in that thread continue it [1].
  5. Mint a Claude token on your own laptop (claude setup-token; the next section walks through it) and paste it into Jiro. ChatGPT users sign in via Codex OAuth or paste an OpenAI key; Cursor Agent only accepts a Cursor API key [10].
  6. Write the org setup script: dependencies, CLIs and services installed once, so each session's environment starts ready [23].
  7. Hand over a first task in a Slack thread. Keep it small and verifiable.

Steps 2 and 4 take minutes. Step 3 is the one teams skip, and the one that makes the review-first promise real.

How do you connect a Claude subscription using claude setup-token?

Run it locally, not inside Jiro. The command exists for machines that cannot open a browser login, and Jiro's cloud environments are exactly that kind of machine [9].

Open a terminal on a laptop where the Claude command line is installed and signed in, type claude setup-token, and copy what it prints. That token stays valid for a year and follows whichever Claude plan the account carries, from Pro up to Enterprise [9]. In Jiro's credential settings, add it as the Claude Code credential; Nori also takes a Claude OAuth sign-in or an Anthropic API key in place of the token [10].

Nothing is resold. Sessions bill against the subscription you already pay Anthropic for, and Nori adds zero token markup [11]. Set a calendar reminder for eleven months out to rotate the token.

How do Amp threads and orbs map to Jiro sessions and runtimes?

An Amp thread is a saved, shareable conversation that follows you between the web, native apps and CLI [24]. The Jiro counterpart is a session, which most teams run as a Slack thread so everyone can read it; replies in the thread keep the same session alive [1].

An orb is the machine Amp spins up for a thread, on its hosted providers, on infrastructure you supply, or on a runner you own [25]. Jiro's counterpart is a runtime: one claimed machine serves one active session [3], each is an isolated cloud environment holding your repos and tools [2], and a runtime left idle dozes off, waking when the next task lands [4].

The sizing differs. Amp lets each user burst to 20 orbs and then starts one more every five minutes [26]. Jiro's Developer plan gives one user up to 3 persistent runtimes and Team gives 5 shared ones [16], so queue work rather than fanning it out.

How should the first five days on Jiro go?

Monday: ask Jiro to read one pilot repo and propose three changes it would make first. Judge its taste before its speed. Tuesday: a documentation pass on the module nobody wants to explain. Wednesday: fill test gaps around a recently changed file. Thursday: clean up dead flags, duplicated helpers and copy-pasted error handling. Friday: one small backlog ticket, plus a cron schedule or one-off reminder for next week so the agent works while nobody is online [14].

Every result shows up as something to review: a PR, a commit or a comment [8]. Reply to those pull requests the way you would reply to a colleague's. Specific comments get specific fixes. If production breaks that week, try the on-call fix from Slack; Corvus's CTO did that from a client dinner [27].

What does switching from Amp cost?

Amp's tiers: Hobby costs nothing and meters orbs as you go, or uses your own runners; Megawatt costs $20 monthly; inside are $20 of agent usage and, on a1.small, 750 orb hours. Gigawatt costs $200 monthly; inside are $200 of usage and, on a1.xxlarge, 1,000 hours [28]. The smallest orb runs $0.08 for an hour, metered minute by minute [29], and extra credits are charged at API list price with no markup outside Enterprise [30].

Jiro charges $99 monthly for Developer (one engineer, three persistent runtimes) and $250 monthly for Team (five runtimes, shared) [16]. Your Claude or ChatGPT invoice does not change, because Nori takes no cut of tokens [11].

Gotcha: a single developer on Megawatt pays Amp less. The case for Jiro's higher flat fee is shared runtimes, Slack threads the whole team sees and work that returns as a reviewable pull request, not a smaller invoice.

When Amp is the better choice

Stay on Amp if per-minute compute matters more than a flat bill. Orbs run from $0.08 an hour for a1.tiny to $1.32 an hour for a1.xxlarge [31], billed by the minute [29], and paused orbs are free [20]. Self-hosted orbs on your own Kubernetes, Docker, E2B or Modal compute [32] cost nothing except on Enterprise [33], and personal providers, needing no workspace, arrived on 2026-10-28 [34].

Stay if you work from the terminal. The Amp CLI covers macOS, Linux and WSL, and the agent it drives may sit on your laptop, inside an orb or on a runner [35], with native macOS, iOS and Android apps alongside [17]. Jiro has no local runner and no native apps.

Stay if Linear is your queue: assign an issue to Amp and an orb spins up [36]. Stay if you want the agent to watch the review comments and CI runs on PRs of its own making [37]. And stay if you are one person on a Claude subscription who is happy with Amp's support for it since 2026-10-10 [19] and wants trunk-based shipping.

Can Amp and Jiro overlap for a few weeks?

Yes. Split work by repository, never by task, so two agents never touch the same branch. Switch Amp to Push to Branch for the overlap so both tools sit behind the same review gate [18]; otherwise you will compare a tool that merges itself against one that waits for review, and the numbers will mislead you.

Count merged pull requests, review rounds per change and how often a reviewer rewrote something. Ignore raw volume. Still weighing options? The Amp alternatives comparison covers seven others.

Jiro at a glance

FactJiro
What it isA background coding agent: it works in the cloud and returns pull requests for review [8]
Made byNori (Tilework Inc.), founded by Amol Kapoor, ex-Google Research [38]
Agents it runsClaude Code, Codex, Cursor, OpenCode, pi-acp [39]
Whose model billYour Claude/ChatGPT login or API key; Cursor key [10]; Your keys, zero token markup [11]
PriceFree 30-day trial; Developer $99/mo; Team $250/mo [16]
RuntimesDeveloper: up to 3; Team: 5 shared; trial: 5 for 30 days [16] [4]
Where work startsSlack, web, Discord, terminal, schedules, webhooks [12]
Where it runsIsolated cloud environment with your repos and tools [2]; Single-tenant per organization [15]
ReposGitHub App (all or selected repos) or a PAT [22]
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). [38] [40] Clifford Ressel is Nori's co-founder and CTO. [41] Nori's customers include Corvus and Miravoice. [27] [42]

FAQ

Will my AGENTS.md work in Jiro?

Yes. The file lives in your repo, and Jiro's harnesses read it at clone time, much as Amp reads AGENTS.md and falls back to CLAUDE.md [6]. Cross-repo rules go into a skillset that gets translated into each harness's own file [7].

Can I use the same Claude subscription I used with Amp?

Yes, with a new token. Generate one locally with claude setup-token; it prints a token that lasts a year and follows your Claude plan [9]. Add it to Jiro as the Claude Code credential [10].

What replaces Amp's Ship-to-main in Jiro?

A PR, or occasionally a commit or comment, which your team reviews, merges or rejects [8]. Turn on branch protection so that is the only way changes reach main.

What is the Jiro equivalent of an orb?

A runtime: an isolated cloud environment per session that sleeps when idle [2] [4]. Developer includes up to 3, Team 5 shared, and the trial 5 for 30 days [16].

Can Jiro use my self-hosted orb provider?

No. The closest equivalent is a dedicated deployment: Nori runs private EC2 session machines inside your company's AWS account [5]; Amp's Docker or Kubernetes providers do not plug in.

Is our code isolated from other Jiro customers?

Each organization gets its own single-tenant broker [15], one machine serves one active session [3], and every session and action is logged [43].

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. 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)
  2. 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)
  3. 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)
  4. 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)
  5. 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)
  6. Amp reads AGENTS.md from the working directory and its parent directories, falls back to AGENT.md or CLAUDE.md where none exists, loads subtree files on demand, and lets workspace admins set a global AGENTS.md. https://ampcode.com/docs/customize/agents-md (checked 2026-11-06)
  7. 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)
  8. 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)
  9. 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)
  10. 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)
  11. 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)
  12. 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)
  13. 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)
  14. 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)
  15. 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)
  16. 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)
  17. Amp runs from the web app at ampcode.com, macOS, iOS and Android apps, the CLI, SDKs, and GitHub and Slack integrations. https://ampcode.com/manual (checked 2026-11-06)
  18. Amp's default Ship rebases, runs tests and pushes straight to the base branch; the Push to Branch setting pushes a feature branch and reports a pull request URL instead. https://ampcode.com/docs/markdown/orbs/shipping (checked 2026-11-06)
  19. Amp added support for running on a Claude subscription through the Claude Agent SDK on 2026-10-10. https://ampcode.com/news/use-your-claude-plan (checked 2026-11-06)
  20. An Amp orb pauses 5 minutes after the agent stops working or 20 minutes after your last interaction, whichever is later, archiving the thread stops it at once, and a paused orb costs nothing. https://ampcode.com/docs/markdown/orbs/sizes-and-costs (checked 2026-11-06)
  21. Nori provides the runtime around coding agents: machines, lifecycle, credentials, integrations, transcripts, checkpoints, team policy and portable skillsets. https://docs.noriagentic.com/start/what-is-nori (checked 2026-11-06)
  22. 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)
  23. 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)
  24. Amp threads are saved conversations you can share, and the same threads are available in the web app, the native apps and the CLI. https://ampcode.com/manual (checked 2026-11-06)
  25. Amp runs cloud work in orbs, one remote machine per thread on Amp-hosted or self-hosted providers that keeps working while your laptop is closed, or on your own machines as runners. https://ampcode.com/manual/orbs (checked 2026-11-06)
  26. Each Amp user can start a burst of 20 metered orbs, after which Amp starts one new orb every five minutes unless support raises the limit. https://ampcode.com/manual/orbs (checked 2026-11-06)
  27. 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)
  28. Amp's Hobby tier is free with pay-as-you-go orbs or your own runners; Megawatt is $20 a month with $20 of agent usage and 750 hours of a1.small orbs, and Gigawatt is $200 a month with $200 of agent usage and 1,000 hours of a1.xxlarge orbs. https://ampcode.com/docs/markdown/pricing (checked 2026-11-06)
  29. Orbs are billed per minute, from $0.08 an hour for the smallest size. https://ampcode.com/docs/markdown/orbs/sizes-and-costs (checked 2026-11-06)
  30. Past a tier's included usage, Amp credits are charged at provider API list prices with no markup for individuals and non-enterprise workspaces, and expire 12 months after purchase. https://ampcode.com/docs/markdown/pricing (checked 2026-11-06)
  31. Amp orb sizes run from a1.tiny with 1 vCPU and 2 GB of RAM at $0.08 an hour to a1.xxlarge with 16 vCPUs and 32 GB at $1.32 an hour, each with 60 GB of disk. https://ampcode.com/docs/markdown/orbs/sizes-and-costs (checked 2026-11-06)
  32. Amp's self-hosted orbs, announced 2026-10-22, turn compute you provide, such as Docker, Kubernetes, Modal, E2B or Daytona, into orbs, with a Helm chart for GKE, EKS and AKS. https://ampcode.com/news/self-hosted-orbs (checked 2026-11-06)
  33. Self-hosted orbs are free on every Amp plan except Enterprise, where they are billed at $0.0504 per CPU-hour plus $0.0162 per GB-hour of memory while connected to a thread. https://ampcode.com/docs/markdown/orbs/sizes-and-costs (checked 2026-11-06)
  34. Since 2026-10-28 any Amp user can add a personal self-hosted orb provider from their own settings, without belonging to a workspace. https://ampcode.com/news/personal-self-hosted-orbs (checked 2026-11-06)
  35. The Amp CLI installs with a one-line curl script on macOS, Linux and Windows through WSL, signs in with amp login, and runs the agent locally, in an orb or on a connected runner. https://ampcode.com/docs/cli (checked 2026-11-06)
  36. Since 2026-10-19, assigning a Linear issue to Amp or mentioning @Amp starts an agent session in Linear and spawns a new orb. https://ampcode.com/news/assign-it-to-amp (checked 2026-11-06)
  37. Since 2026-10-12 Amp can subscribe to the comments, reviews and CI results of a pull request it opened and handle them in the same thread, through the Amp GitHub App. https://ampcode.com/news/github-listeners (checked 2026-11-06)
  38. 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)
  39. 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)
  40. 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)
  41. Clifford Ressel is Nori's CTO and co-founder. https://ai.engineer/orgs/nori (checked 2026-11-06)
  42. 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)
  43. Nori logs every session and every action, and makes them searchable. https://noriagentic.com/for-security-leaders.html (checked 2026-11-06)