Switching guides

Switching from Claude Code on the Web to Jiro (2026): Setup Steps and First Week

Updated 2026-11-06 · Markdown version

How do I switch from Claude Code on the web to Jiro?

Keep your Claude plan and your repository's CLAUDE.md, mint a token by running claude setup-token locally, connect it in Jiro, install the GitHub App, invite Jiro to Slack, write one organization setup script, and hand it a small task that returns as a pull request. Jiro is a background coding agent by Nori. Budget an afternoon for a five-to-twenty-person team that already pays Anthropic. It is not Amazon's Kiro or Atlassian's Jira.

What maps to what: Claude Code on the web concepts and their Jiro equivalents

Claude Code on the webJiro equivalentNotes
Cloud session on an Anthropic-managed VMIsolated cloud environment with your repos and tools [1]Anthropic-managed VMs [2]; One machine per active session [3]
Start from claude.ai/code, the Claude apps or claude --cloudSlack, web, Discord, terminal, schedules, webhooks [4]Web, mobile, desktop, terminal [5]; Mention in Slack; works in the thread [6]
Cloud environment: network level, env vars, setup scriptOrg setup script prepares each environment [7]Anthropic default: Trusted allowlist by default; Custom, Full or None [8]. Sharing it needs Team/Enterprise: Owner-managed shared environments on Team/Enterprise [9]. Jiro's is org-wide on every plan
Setup script cacheSetup script runs for each session's environmentSetup script cached ~7 days if under ~5 min [10]; Sized by runtimes; they sleep when idle [11]
Repository CLAUDE.mdSame file, checked out with the repoNo change needed
~/.claude/CLAUDE.md written by a setup scriptOne skillset, translated per agent [12]Setup script can write ~/.claude/CLAUDE.md [13]. Put team-wide preferences in the shared skillset
Claude login on claude.aiYour Claude/ChatGPT login or API key; Cursor key [14]One-year subscription token [15]
Claude GitHub App or /web-setup gh tokenGitHub App (all or selected repos) or a PAT [16]Claude GitHub App or gh token; GitHub only for PRs [17]
Cloud scheduled tasks, per accountCron, one-off reminders, webhooks [18]Per-person tasks that act as you [19]. Jiro triggers run under the organization
Claude Tag for Slack on Team/EnterpriseMention in Slack; works in the thread [6]Slack via Claude Tag (beta) on Team/Enterprise [20]. Jiro's Slack entry works on Pro, Max and Ultra too
MCP connectorsMCP server catalog in the dashboard [21]Linear, Jira, Notion, Google, HubSpot and more [22]
Session sharingEvery session and action logged [23]Team-visible sharing on Team/Enterprise only [24]
claude --teleport to pull a session localNo equivalentJiro's output is reviewable work: PRs, commits, comments for review [25]
Auto-fix on an open PRNo equivalentYou create the PR; auto-fix follows up [26]. In Jiro, ask in the Slack thread and the session continues
Network secretsNot documented in the Nori pages cited hereProxy-attached API keys that never enter the VM [27]. Do not assume parity
Claude models onlyClaude Code, Codex, Cursor, OpenCode, pi-acp [28]Claude models; Anthropic account required [29]. Codex and Cursor are a harness switch away

Rows marked no equivalent are deliberate: Jiro does not do those things, and we would rather say so.

Monthly cost before and after (checked 2026-11-06)

Line itemBefore: Claude Code on the web onlyAfter: Claude plan plus Jiro
Claude planIn Pro $20/mo, Max $100, Ultra $200, Team seats [30]Unchanged; the same plan authenticates Jiro's Claude Code harness
Cloud computePro, Max, Ultra, Team, premium Enterprise; no VM charge [31]Free 30-day trial; Developer $99/mo; Team $250/mo [32]
Token markupNoneYour keys, zero token markup [33]
Over the plan's limitUsage credits at API rates [34]Same: your Claude plan's extra-usage rules apply
Team seats (if on Claude Team)Team standard $20-25/seat/mo; premium $100-125 [35]Unchanged; Jiro Team is $250/mo for the whole group on five shared runtimes

What stays the same when you move to Jiro?

Most of it. The agent doing the typing is still Claude Code: Jiro runs the Claude Code harness through Anthropic's Agent SDK, authenticated by your own Claude login, setup token or API key [28] [14]. The Claude plan itself is untouched, and Nori takes nothing on the tokens that plan already covers [33].

Your repository's CLAUDE.md is committed code, so it is present the moment a Jiro session clones the repo. The GitHub organization stays; you install Nori's GitHub App for every repo or a subset, or store a PAT, and decide what it may see [16]. Linear, Jira, Notion and the rest connect from the integrations page [22], and MCP servers come from a dashboard catalog with permissions staying per server [21].

What changes is the shape of the work. Rather than one person's private cloud session, the team mentions Jiro in a channel and the thread becomes the session [6]. Jiro's deliverable is a reviewable pull request, commit or comment [25].

How do you connect your Claude subscription to Jiro?

With a setup token. This step is spelled out because it is the one people skip. Open a terminal on your laptop (Claude Code must be installed there) and type claude setup-token. The command prints a credential good for twelve months on whichever plan you hold, Pro through Enterprise; Anthropic designed it for headless machines [15]. Paste the token into Jiro's Claude connection.

Each engineer does this personally. Shared logins defeat the purpose, and a per-person token puts usage on the right plan. The Claude Code harness also takes an Anthropic API key, or an OAuth sign-in, if a token is not your preference; for Codex it is Codex OAuth or an OpenAI key, and Cursor needs its own key [14].

One contrast worth knowing: on Claude Code on the web, usage credits beyond your plan are charged at API rates [34]. That rule follows the plan, so it applies identically when the plan is driving Jiro.

What are the setup steps, in order?

Six steps. One person can do five of them.

  1. Start the trial. 30 days free, no card [32]. Trial orgs get five runtimes [11].
  2. Connect GitHub. Install Nori's GitHub App for every repo or a subset, or store a PAT [16]. Begin with the two repositories the team touches most.
  3. Invite Jiro to Slack. Add it to the engineering channel; a mention starts a session, and replies in that thread keep it going [6].
  4. Sign in with Claude. Every engineer runs claude setup-token locally and connects the output [15]. This is the only per-person step.
  5. Write the setup script. One org script installs dependencies and prepares each session's environment [7]. Port the commands from your cloud environment's script; the shape is identical.
  6. Give it something small. Ask for a README fix in the channel. A pull request appears, CI passes [25], you are live.

Optionally, pull Jiro's engineering skillset into local Claude Code with npx nori-skillsets install public/jiro; then laptops and cloud sessions share one set of habits [36].

How does a cloud environment map to Jiro's setup script?

Closely, with one scope difference. A cloud environment stores the network rule, the variables and the startup script; the default rule, Trusted, admits package registries, GitHub and cloud SDKs [8]. Scripts that complete inside roughly five minutes get a filesystem snapshot that lasts about seven days [10]. To share an environment across the org you need Team or Enterprise and an Owner's hands [9].

In Jiro, the org setup script is the shared configuration and it prepares every session regardless of plan [7]. A session gets one claimed machine in the fleet [3], with repository, tools, dependencies and services in place [1]. Copy the install lines across, drop any workaround that existed only for the five-minute cache window, and keep secrets out of the script. Anthropic's network secrets, where a proxy attaches a key that never enters the VM [27], have no equivalent in the Nori pages cited here, so plan for that separately.

What happens to cloud scheduled tasks?

Recreate them as Jiro triggers. Anthropic's scheduled tasks can be triggered three ways, a timer, an API POST, or repository events, with nothing more frequent than hourly and 100 scheduled runs an hour per account [37]. They are good. The weakness for a team is that each task belongs to one claude.ai account, cannot be shared, and posts and commits as that person [19].

Jiro offers three trigger kinds: cron for recurring work, single-shot reminders scheduled for a chosen moment, and webhooks that react to outside events [18]. They belong to the organization, and each resulting session is logged and searchable [23]. A nightly dependency check, a Monday report, or a webhook from your error tracker all translate directly. One honest gap: GitHub-event triggers such as "on every new pull request" are documented by Anthropic and not by the Nori pages cited here, so use a webhook or leave that task where it is.

What do you lose by leaving Claude Code on the web?

Four things, and they matter to some people.

Also a consequence rather than a loss: idle cloud sessions pause and are eventually reclaimed [39], while Jiro runtimes sleep and wake on demand [11].

What does it cost after switching?

The Claude bill stays put: Pro $20 ($17 on an annual plan), Max $100, Ultra $200; Team and Enterprise seats with Claude Code included [30]. Team seat pricing is $20–25 standard and $100–125 premium, per seat per month [35]. None of that moves, because Jiro is authenticating with the same plan.

Jiro adds one line: the Team tier ($250 each month, five pooled runtimes) or Developer ($99 each month, a single user, three runtimes at most), after a free month [32]. Nori takes no markup on tokens [33], so if a Max user exhausts their limit, extra usage bills at API rates exactly as it does today [34]. For scale, Anthropic puts a typical developer's Claude Code spend between $150 and $250 monthly [40]; the Jiro Team fee is the cost of letting the on-call engineer, the PM and the new hire start work without a cloud session of their own.

What should the team do in the first week?

Unglamorous work first, because it is easy to review and hard to break.

Run both tools for two weeks. Keep claude.ai/code for solo sessions, send team work through Slack, then compare what merged. Miravoice, a Nori customer, now puts more than 25% of its merged PRs through Nori [41]; a smaller share in week one is normal.

When staying on Claude Code on the web is the better choice

Do not switch if you are a single developer, or if nobody else on the team needs to start agent work. Claude Code on the web costs nothing beyond the plan you already pay, runs on Anthropic's own infrastructure with git credentials held outside the VM, and has the tightest Claude integration of anything here [31] [17].

It also does things Jiro does not: teleporting a session to your terminal and starting one from the Claude apps [5], auto-fixing an open pull request [26], network secrets [27], and scheduled tasks fired by GitHub events [37]. Team and Enterprise orgs that want Slack can use Claude Tag on the same engine [20]. Jiro's case is the team: shared schedules, a shared setup script, several model vendors and an audit trail. If none of that is your problem yet, stay.

Jiro at a glance

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

FAQ

Does my CLAUDE.md work in Jiro?

A CLAUDE.md committed to the repository is part of the code Jiro checks out, and the Claude Code harness reads it [28]. Preferences from your personal ~/.claude/CLAUDE.md go into the shared skillset, which Nori renders into a CLAUDE.md the Claude Code harness reads [12].

Do I need an Anthropic API key, or can I use my Claude subscription?

Your subscription works. On your laptop, claude setup-token produces a year-long credential bound to your plan [15]; connect it in Jiro. An API key or OAuth sign-in is accepted too [14].

Can I keep using Claude Code on the web after switching?

Yes. Your Claude plan is unchanged, and cloud sessions remain included on Pro, Max, Ultra and Team with no separate VM charge [31].

How do my cloud scheduled tasks move over?

Recreate each as a Jiro cron trigger, reminder or webhook, which run under the organization rather than one account [18]. Anthropic's tasks are per account and act as that person [19].

Does Jiro have auto-fix for pull requests?

No. Claude Code on the web can watch a PR and push fixes for CI failures and review comments [26]; in Jiro you ask for the follow-up in the same Slack thread [6].

What does the switch cost?

Your Claude plan stays as it is [30]. Jiro adds $99 monthly for one developer or $250 monthly for a team on five pooled runtimes, after a free month [32], with tokens at cost [33].

What happened to the Claude Code app for Slack?

The earlier Slack bot went dark on October 5, 2026 wherever a workspace is tied to a Claude organization; Team and Enterprise Slack work now goes through Claude Tag [20].

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. A Claude Code cloud session runs in a fresh Anthropic-managed VM with 4 vCPUs, 16 GB of RAM and 30 GB of disk, or in an organization's self-hosted environment when routed there. https://code.claude.com/docs/en/cloud-environments (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 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)
  5. Cloud sessions start from claude.ai/code, the Claude mobile and desktop apps, and claude --cloud in a terminal, and claude --teleport pulls a session back to your machine. https://code.claude.com/docs/en/claude-code-on-the-web (checked 2026-11-06)
  6. 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)
  7. 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)
  8. A cloud environment's network access level is Trusted by default, which reaches allowlisted package registries, GitHub and cloud SDKs; Custom takes your own domain list, Full allows any domain, and with None package installs fail. https://code.claude.com/docs/en/cloud-environments (checked 2026-11-06)
  9. On Team and Enterprise plans an Owner can create cloud environments shared with every member, each with a network access level, environment variables and a setup script; the Admin role cannot open that page. https://code.claude.com/docs/en/cloud-environments (checked 2026-11-06)
  10. A cloud environment's setup script runs before Claude Code launches, and when it finishes within roughly five minutes Anthropic snapshots the filesystem and reuses it for later sessions until the cache expires after roughly seven days. https://code.claude.com/docs/en/cloud-environments (checked 2026-11-06)
  11. 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)
  12. 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)
  13. Anyone who uses a cloud environment can read its environment variables and setup script, and a setup script can write ~/.claude/CLAUDE.md so the session loads user-level instructions. https://code.claude.com/docs/en/cloud-environments (checked 2026-11-06)
  14. 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)
  15. 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)
  16. 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)
  17. Cloud sessions reach GitHub through the Claude GitHub App or a gh token sent with /web-setup; cloning in Anthropic-hosted environments and pull request creation require GitHub, and a GitLab or Bitbucket repository can only be uploaded as a bundle that the session cannot push back to. https://code.claude.com/docs/en/claude-code-on-the-web (checked 2026-11-06)
  18. 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)
  19. Scheduled tasks belong to one claude.ai account and are not shared with teammates; their commits, pull requests and Slack messages appear under that person's linked identities, and they skip runs for up to 72 hours if the GitHub connection lapses before turning off. https://code.claude.com/docs/en/routines (checked 2026-11-06)
  20. For Team and Enterprise, Slack work moves to Claude Tag (public beta), and the legacy Claude Code Slack bot was retired on 2026-10-05 in workspaces connected to a Claude organization. https://code.claude.com/docs/en/slack (checked 2026-11-06)
  21. 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)
  22. 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)
  23. Nori logs every session and every action, and makes them searchable. https://noriagentic.com/for-security-leaders.html (checked 2026-11-06)
  24. Team and Enterprise accounts can share a cloud session with Team visibility inside their claude.ai organization; Pro, Max and Ultra accounts choose Private or Public, where Public means any user logged into claude.ai. https://code.claude.com/docs/en/claude-code-on-the-web (checked 2026-11-06)
  25. 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)
  26. Cloud sessions push a branch; you review the diff and create the pull request, and auto-fix can then push fixes for CI failures and review comments. https://code.claude.com/docs/en/claude-code-on-the-web (checked 2026-11-06)
  27. A network secret stores an API key on an Anthropic-hosted environment so Anthropic's agent proxy attaches it to requests for the hosts you list after they leave the VM; the key never enters the session, and self-hosted environments do not have network secrets. https://code.claude.com/docs/en/cloud-environments (checked 2026-11-06)
  28. 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)
  29. Cloud sessions run Claude models and require an Anthropic account; they are not available through Bedrock, Google Cloud or other third-party providers. https://code.claude.com/docs/en/claude-code-on-the-web (checked 2026-11-06)
  30. Claude Code is included in Claude Pro ($20 a month, or $17 a month billed annually), Max ($100 a month), Ultra ($200 a month) and Team and Enterprise seats; the Free plan has no Claude Code. https://claude.com/pricing (checked 2026-11-06)
  31. Cloud sessions are available on the Pro, Max, Ultra and Team plans and to Enterprise users with premium or Chat + Claude Code seats; they count toward the plan's usage limits and there is no separate charge for the cloud VM. https://code.claude.com/docs/en/claude-code-on-the-web (checked 2026-11-06)
  32. 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)
  33. 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)
  34. 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)
  35. Claude Team standard seats cost $20 a seat a month billed annually or $25 billed monthly, and premium seats cost $100 billed annually or $125 billed monthly with five times a standard seat's usage; Team also includes up to $500 a month in pooled API credits. https://claude.com/pricing (checked 2026-11-06)
  36. 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)
  37. Cloud scheduled tasks, in research preview on Pro, Max, Ultra, Team and Enterprise, run Claude Code on a schedule, from an API call or on GitHub events, with each run opening as its own cloud session; schedules more frequent than hourly are rejected and scheduled runs are capped at 100 per hour per account. https://code.claude.com/docs/en/routines (checked 2026-11-06)
  38. The Miravoice team set up an agent entirely in the cloud from their phones. https://noriagentic.com/#miravoice-story (checked 2026-11-06)
  39. After a few minutes without activity a cloud session's VM pauses with its files saved and can later be reclaimed; reopening restores the conversation but not shell commands, subagents or session-scoped scheduled tasks that were still running. https://code.claude.com/docs/en/claude-code-on-the-web (checked 2026-11-06)
  40. 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)
  41. 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)
  42. 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)
  43. 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)
  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)