Switching guides

Switching from Warp to Jiro (2026): Setup Steps and First-Week Plan

Updated 2026-11-06 ยท Markdown version

How do I switch from Warp to Jiro?

Switching from Warp to Jiro means moving the cloud agent runs and keeping any terminal you like: start the free 30-day trial, connect GitHub and Slack, sign in with claude setup-token (or Codex OAuth or a Cursor key), write a setup script, and send a first small task while Warp keeps running for a week. Jiro is a background coding agent by Nori. It is not Amazon's Kiro or Atlassian's Jira.

What maps to what: Warp concept to Jiro equivalent

Warp conceptJiro equivalentNotes
Warp terminal (blocks, AI input)No equivalent; keep any terminalOpen-source client (AGPL-3.0 + MIT) [1]
Warp Agent CLI on your laptopYour local Claude Code, Codex or Cursor CLIJiro is the cloud side only; Claude Code, Codex, Cursor, OpenCode, pi-acp [2]
Cloud runJiro sessionIsolated cloud environment with your repos and tools [3]; One machine per active session [4]
Cloud environmentOrg setup script plus GitHub App repo scopeWarp: Repos + container image + setup commands + secrets [5]. Jiro: Org setup script prepares each environment [6]
Harness per run (Warp Agent, Claude Code, Codex)Claude Code, Codex, Cursor, OpenCode, pi-acp [2]Cursor Agent needs a Cursor API key
Team-managed inference (Business and Enterprise)Your Claude/ChatGPT login or API key; Cursor key [7]Your keys, zero token markup [8]
Platform usage at $3 per agent hour + inference + computeFree 30-day trial; Developer $99/mo; Team $250/mo [9]Sized by runtimes; they sleep when idle [10]
Local-to-cloud handoff (& or /handoff)No equivalentPush the branch, then start a session from Slack or the terminal
Slack triggerMention in Slack; works in the thread [11]Mention the bot; the thread is the session
SchedulesCron, one-off reminders, webhooks [12]Cron and one-off reminders
Linear and Jira triggersNo trigger equivalentLinear, Jira, Notion, Google, HubSpot and more [13] as tools the agent uses, not as triggers
GitHub Actions (oz-agent-action)No equivalentJiro webhooks take events from other systems; CI is not a documented trigger
Run outputs (branch, PR, report, transcript)PRs, commits, comments for review [14]Review, merge or send back
Self-hosted computeNori cloud, or a dedicated deployment in your AWS account [15]A dedicated deployment, not self-managed workers
Run trackingEvery session and action logged [16]Single-tenant per organization [17]

Checked 2026-11-06. Rows marked "No equivalent" are gaps, not workarounds in disguise.

What moves and what stays when you leave Warp?

Only the cloud runs move. Warp's terminal client is open source, licensed AGPL-3.0 with MIT UI crates [1], and Jiro has no opinion about which emulator you type into, so the window stays if you want it. What changes is who executes the agent work and who pays for the model. Warp meters each cloud run: $3 for every agent hour, then inference, then any compute Warp hosts [18], and a personal BYOK key never leaves your laptop for a cloud run [19]. In Jiro, the same work happens inside its own isolated cloud environment, repositories and tooling already present [3], charged to the Claude or ChatGPT plan you already have, or to an API key or Cursor key [7], and no token markup is added [8]. Plan for about an hour of setup. The seven steps below are in the order that avoids backtracking.

Step 1: Collect what Warp knows about your code

Open a repository and check for AGENTS.md or CLAUDE.md. Those files travel for free: they live in git, and Claude Code and Codex each read their own file when Jiro runs them. Nori writes one skillset and emits the file each agent expects: a CLAUDE.md for Claude Code, a copilot-instructions.md for Copilot, an AGENTS.md for everything else [20], so repo-level instructions need no conversion.

Everything else needs a manual pass. Rules you taught the Warp Agent, saved prompts, the note about not touching the migrations folder: none of it exports. Paste the parts you still believe into one scratch file. That file becomes your org skillset, which Nori holds alongside machines, credentials, integrations and transcripts as part of the runtime around the agent [21]. Expect to delete half of it. Stale rules cost more review time than missing ones.

Step 2: Mint a subscription token by running claude setup-token

Open a terminal and type claude setup-token. Anthropic returns a 12-month token for your Claude plan, whether Pro, Max, Ultra, Team or Enterprise, built for machines with no browser available for sign-in [22], which is exactly what a cloud runtime is. Copy the output and keep it for step 4. Treat it as a password.

This is the step Warp cannot offer: its cloud runs never see a personal key [19], while Jiro's Claude Code harness accepts this setup token, or alternatively an Anthropic API key or Claude OAuth [7]. If your team is on ChatGPT instead, skip the token; you will sign in with Codex OAuth or paste an OpenAI key. For the Cursor harness, create a Cursor API key now. For OpenCode or pi-acp, supply a compatible API endpoint, its key and a model name [7].

Step 3: Start the trial and connect GitHub

Sign up for the trial. It lasts 30 days, costs nothing and needs no card [9]. Then install the GitHub App. Nori offers two credential methods: either a GitHub App, which you can scope to every repository or only chosen ones, or a saved personal access token [23]. Choose selected repositories and tick two or three to begin with. You widen the scope later once the first pull requests have been reviewed. The App route is the one to prefer for a team, because it does not depend on one person's account staying active.

Step 4: Connect Slack and add your credential

Connect your Slack workspace, make a channel such as #jiro, and invite the bot. Mention the bot to open a session; it answers in a thread, and anything posted in that thread continues it [11]. That thread-equals-session rule is the closest Jiro gets to Warp's conversation model, so teach the team early.

Now paste the token from step 2 into the Claude connection, or sign in with Codex OAuth, or add your OpenAI or Cursor key [7]. The credential is scoped to your organization; each hosted organization runs on a broker of its own, single-tenant, at its own subdomain [17]. Verify the connection with a one-line request in Slack before continuing.

Step 5: Rebuild Warp's cloud environment as a setup script

A Warp cloud environment groups repositories, a container image, setup commands, environment variables and secrets injected at runtime [5]. Jiro's counterpart is an org setup script, run before each session, that installs what the code needs [6], on a machine that already has your repository, tools and services available [3]. One claimed machine serves one active session [4].

Translate directly. Setup commands become lines in the script. Image choices become install steps for the language runtimes you need. Secrets become environment variables set in the dashboard. Write it so that your test suite passes from a clean checkout, then run a session that does nothing but execute the tests. If that passes, every later task starts from a working machine. Skipping this step is the most common cause of a disappointing first week.

Step 6: Recreate schedules and connect integrations

Jiro's triggers are cron for work that repeats, one-shot reminders scheduled for a later time, and webhooks for events from other systems [12]. Any Warp schedule maps to a cron trigger with the same prompt. Warp triggers from Linear, Jira, GitHub comments and GitHub Actions [24] have no direct equivalent; the honest substitute is a Slack message or a webhook from the system that notices the event.

Integrations are a different matter. Nori connects to Linear, Jira, Notion, Google Drive, HubSpot, Stripe and more [13], and the dashboard offers an MCP server catalog where each server's own permissions still apply [25]. Connect the ones your Warp runs used so the agent can read tickets and update them, even though a ticket cannot start the run.

Step 7: Send the first task

Ask for something small in #jiro. A good first task has a clear finish line and touches one file: a README command that no longer matches the Makefile, a flaky test with a known cause, a lint rule the repo already violates. The session provisions a machine, runs your setup script, reads the repo and hands back a pull request, a commit or a comment for you to review [14]. Read it the way you would read a colleague's PR. If it questions the premise of the task, that is working as intended. Record how many review rounds it took. You will want that number at the end of the week.

What should the first week with Jiro look like?

Keep Warp running for anything already in flight and route new work to Jiro. A workable split:

Count review rounds per task and compare with the same week of Warp runs. Also compare the bills. Warp's runs tick at $3 an agent hour before inference and compute [18]; Jiro's platform fee is flat, and runtimes sleep when idle [10]. By Friday you will have a number for each, which is a better basis for the decision than any comparison page, including this one.

What do you give up by leaving Warp?

Four things, stated plainly. Warp's local-to-cloud handoff, triggered with & or /handoff, forks a conversation and carries your uncommitted diff into the cloud [26]; Jiro has nothing like it, and you will push a branch and start fresh instead. Warp's oz-agent-action runs agents from pull request events, labels, CI failures and comment mentions inside GitHub Actions [27]; Jiro does not trigger from CI or GitHub comments. Warp starts runs from Linear and Jira [24]; Jiro treats those as integrations rather than triggers [13]. And Warp can execute on your own infrastructure with no compute charge for self-hosted compute [28]; Nori hosts Jiro, and customers who want it in their own AWS account get a dedicated deployment [15]. Also gone: Warp's own agent harness. Jiro offers Claude Code, Codex or Cursor Agent, with OpenCode and pi-acp as further options [2].

How do the bills compare for a five-person team?

Warp's Business tier runs $50 per user monthly and includes $20 of agent usage per seat, up to 25 seats [29] [30]. Beyond the included usage, every run adds $3 per agent hour and its own inference and hosted-compute charges [18]. Jiro Team is $250 a month, flat, for multiple users sharing five runtimes; Developer, at $99 monthly, is for one person with up to three runtimes [9]. Inference stays on the Claude or ChatGPT plans the team already pays for [7].

Do not compute a total from these figures. The variable is agent hours, and only your pilot week can supply it. If a Pro subscriber hits plan limits during the pilot, Claude Max at $100 a month gives five times Pro usage [31], or extra usage can be bought as credits at the standard API rate [32].

When Warp is the better choice

Stay on Warp if the handoff is part of how you work. Forking a live local conversation, uncommitted files and all, into a cloud run [26] is a workflow no tool on jiro.bot matches, and it is why Warp's terminal-plus-agent design earns its place.

Stay if GitHub is where work begins. The oz-agent-action runs from PR events, issue labels, CI failures and @oz-agent mentions using a Warp API key stored as a repository secret [27], and Linear and Jira can start runs too [24]. Jiro cannot do any of that.

Stay if you need compute on your own infrastructure right now [33], or if Business-tier team-managed inference already solves the key problem [19]. And if you are a light user, Build's $20 or Max's $200 of included monthly agent usage may cover everything you do [30], at which point the switch saves nothing. In each of those cases, keep Warp and bookmark this page.

Jiro at a glance

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

FAQ

Do I have to stop using the Warp terminal to use Jiro?

No. Jiro replaces cloud agent runs only. The Warp terminal is open source, licensed AGPL-3.0 with MIT UI crates [1], and works fine beside Jiro.

Why run claude setup-token when switching to Jiro?

The token it produces lasts one year, is tied to the Claude subscription you already pay for, and works on hosts with no browser [22], which lets Jiro's Claude Code harness run on your existing subscription [7].

Will my Warp rules and prompts import into Jiro?

Not automatically. Copy them into your org skillset by hand; Nori translates that skillset into each agent's own instruction file [20]. AGENTS.md and CLAUDE.md in your repos need no copying.

Can Jiro trigger from GitHub Actions or Linear like Warp?

No. Jiro starts from Slack, Discord, its web dashboard, the terminal, schedules and webhooks [35]. Linear and Jira connect as integrations the agent can use [13], not as triggers.

Can I run Warp and Jiro at the same time during a pilot?

Yes, and you should for at least a week. Leave in-flight Warp runs alone, send new work to Jiro, and never hand the same ticket to both so your review-round counts stay comparable.

What if nobody on the team has a Claude subscription?

Use Codex with ChatGPT sign-in or an OpenAI key, an Anthropic API key, a Cursor API key for the Cursor harness, or a compatible API key for OpenCode or pi-acp [7].

Does Jiro mark up tokens the way Warp bills inference?

No. Jiro runs on your own keys or login with zero token markup [8]; Warp's cloud runs carry a $3 agent-hour meter, with inference and compute billed separately [18].

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. Warp's terminal client is open source on GitHub under AGPL-3.0, with its UI framework crates under MIT. https://github.com/warpdotdev/warp (checked 2026-11-06)
  2. 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)
  3. 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)
  4. 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)
  5. A Warp cloud environment groups one or more repositories, a container image, setup commands, environment variables and secrets that Warp injects at runtime. https://docs.warp.dev/agent-platform/cloud-agents/environments (checked 2026-11-06)
  6. 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)
  7. 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)
  8. 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)
  9. 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)
  10. 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)
  11. 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)
  12. 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)
  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 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)
  15. 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)
  16. Nori logs every session and every action, and makes them searchable. https://noriagentic.com/for-security-leaders.html (checked 2026-11-06)
  17. 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)
  18. Warp bills a cloud run for agent time at $3 per agent hour, plus inference and Warp-hosted compute. https://docs.warp.dev/support-and-community/plans-and-billing/platform-credits/ (checked 2026-11-06)
  19. Each Warp cloud run can use Warp Agent, Claude Code or Codex; personal BYOK keys are not copied to cloud runs, but Business and Enterprise can configure team-managed inference. https://docs.warp.dev/platform/handoff/local-to-cloud/ (checked 2026-11-06)
  20. 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)
  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. 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)
  23. 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)
  24. Warp cloud runs start from Slack, Linear, Jira, GitHub, GitHub Actions, schedules, the Oz CLI, the API or the web app. https://docs.warp.dev/platform/integrations/ (checked 2026-11-06)
  25. Nori's dashboard exposes a catalog of MCP servers for project management, observability, analytics and other tools, and each server's own permissions still apply. https://docs.noriagentic.com/sessions/guides/integrations#managed-mcp-servers (checked 2026-11-06)
  26. Pressing & or running /handoff in a local Warp Agent conversation forks the transcript and snapshots uncommitted changes, including untracked files, into a cloud run. https://docs.warp.dev/platform/handoff/local-to-cloud/ (checked 2026-11-06)
  27. Warp's oz-agent-action GitHub Action runs agents from workflow triggers such as @oz-agent comments, pull request events, issue labels, daily schedules or CI failures, using a Warp API key stored as a repository secret. https://docs.warp.dev/platform/integrations/github-actions (checked 2026-11-06)
  28. Warp charges compute only for sandboxes on Warp-hosted compute, so local or self-hosted compute incurs no compute charge, and customer-supplied inference is billed by your own provider. https://docs.warp.dev/support-and-community/plans-and-billing/platform-credits/ (checked 2026-11-06)
  29. Warp's Terminal and Agents plans are Free, Build at $20 a month, Max at $200 a month and Business at $50 per user a month; Warp Factories also offers pay-as-you-go usage at 20% above API rates. https://www.warp.dev/pricing (checked 2026-11-06)
  30. Warp's Build plan includes $20 of agent usage each month at API rates, Max includes $200 a month, and Business includes $20 per seat a month for up to 25 seats. https://www.warp.dev/pricing (checked 2026-11-06)
  31. 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)
  32. 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)
  33. Warp cloud agents run on Warp-hosted compute or on your own infrastructure. https://docs.warp.dev/agent-platform/cloud-agents/overview (checked 2026-11-06)
  34. 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)
  35. 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)
  36. 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)
  37. Clifford Ressel is Nori's CTO and co-founder. https://ai.engineer/orgs/nori (checked 2026-11-06)
  38. 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)
  39. 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)