---
title: "Switching from Claude Tag to Jiro (2026): Setup Steps and a Two-Week Pilot"
canonical: https://jiro.bot/switch/claude-tag-to-jiro
last_updated: 2026-11-06
---

# Switching from Claude Tag to Jiro (2026): Setup Steps and a Two-Week Pilot

Updated 2026-11-06

> **How do I switch from Claude Tag to Jiro?**
>
> Run both for two weeks instead of cutting over: leave Claude Tag in its channel, connect Jiro to a neighbouring one using a `claude setup-token` login from the Claude plan you already pay for, recreate routines as schedules, and alternate tickets between the two. Jiro is a background coding agent by Nori. Teams of 5 to 20 engineers on Claude or ChatGPT are the fit; a Claude Enterprise shop that wants a single vendor should stay on Tag. It is not Amazon's Kiro or Atlassian's Jira.

## What maps to what

| Claude Tag | Jiro equivalent | Notes |
|---|---|---|
| @Claude mention in a channel | Mention in Slack; works in the thread [1] | Same habit; only the bot name changes |
| Ephemeral sandbox per thread | Isolated cloud environment with your repos and tools [2] | One machine per active session [3] |
| Admin environment setup script | Org setup script prepares each environment [4] | Copy the install commands across |
| Claude GitHub App grants per channel | GitHub App (all or selected repos) or a PAT [5] | Select only pilot repositories at first |
| Connectors and remote MCP servers | MCP server catalog in the dashboard [6] | Linear, Jira, Notion, Google, HubSpot and more [7] |
| Scheduled routines | Cron, one-off reminders, webhooks [8] | Recreate each as a cron schedule |
| Single-PR subscription | Webhook trigger | Partial: fires on events your tooling sends |
| Channel watch | No equivalent | Record the gap before deciding |
| Channel memory and workspace notes | Shared org context and portable skillsets [9] | Rewrite as skillset text; nothing migrates automatically |
| Model switch per thread | Claude Code, Codex, Cursor, OpenCode, pi-acp [10] | Pick the harness; models follow your plan |
| Organization usage balance and spend limit | Free 30-day trial; Developer $99/mo; Team $250/mo [11] | Your subscription's own limits still apply |
| Self-hosted runners | Nori cloud, or a dedicated deployment in your AWS account [12] | Dedicated deployment in your own AWS account |
| Session transcripts kept by Anthropic | Every session and action logged [13] | Logged on your single-tenant broker |
| One-to-one DMs on your own seat | Slack, web, Discord, terminal, schedules, webhooks [14] | Web dashboard, terminal or Discord for solo work |

Rows marked partial or no equivalent are the honest gaps; the pilot measures whether they matter to your team.

## Who should switch from Claude Tag, and who should stay?

Switch if any of three things is true. Your engineers hold Pro, Max or Ultra plans, which Tag does not accept [15]. Finance wants a flat monthly figure rather than a usage balance an Owner must fund and cap [16] [11]. Or part of the team wants Codex or Cursor Agent alongside Claude Code [10]. Stay if your organization is on Claude Enterprise, everyone is content with Opus and Sonnet, and the people asking for work are mostly outside engineering, since channel use needs no seat each [17]. The guide below assumes the first group. It is written for a pilot lead with admin rights in Slack, GitHub and the Claude organization, and it takes one sitting to set up.

## What carries over from Claude Tag, and what has to be rebuilt?

Committed repository files travel for free. Once Tag clones a granted repository it picks up `CLAUDE.md`, the rules directory and committed skills [18], and Jiro's Claude Code harness reads those same files from its own clone [10]. Hooks and `.mcp.json` never ran in Tag [19], so any workaround your team built can be retired once Jiro's setup script takes over [4].

Admin-side configuration does not travel. Connectors reconnect through Jiro's integrations and MCP catalog [6] [7]. Scheduled routines are recreated as cron triggers [8]. Channel memory and workspace notes have to be read out of Tag by asking it what it remembers, then rewritten into a skillset that Nori translates into each agent's instruction file [20]. Channel watches have no counterpart. This mirrors what happened when Tag replaced the earlier Slack bot: the handle stayed, no data migrated, and connections were rebuilt [21]. Old Tag threads remain readable in Slack throughout.

## Step 1: open the trial and connect GitHub

Start the free trial; it is 30 days long, card-free, and comes with five runtimes [11] [22]. Then connect GitHub. Jiro offers two routes: install its GitHub App and choose every repository or a handful, or store a personal access token [5]. For the pilot, grant only the repositories in scope, which is the same discipline Tag admins use when granting repositories per channel. Leave the Claude GitHub App installed; Tag keeps using it in its own channel for the two weeks. Nothing about this step touches your Anthropic account yet.

## Step 2: mint a token with `claude setup-token`

This is the step people skip and then wonder why nothing runs. Open a terminal on a laptop where Claude is already signed in and run `claude setup-token`. Anthropic built the command for machines without a browser; the token it prints lasts twelve months and inherits the plan behind the login, whether Pro, Max, Ultra, Team or Enterprise [23]. Copy it into Jiro's Claude connection. Jiro's Claude Code harness takes three credential forms, an Anthropic key, a Claude OAuth session, or this token [24].

Two notes. The token carries your plan's limits with it, so a Max login still resets every five hours with a weekly cap, and overflow continues as credits at API rates [25] [26]. Teams that also want Codex add a ChatGPT OAuth login or OpenAI key separately, and Cursor Agent is unlocked only by a Cursor API key [24]. None of these tokens is marked up by Nori [27].

## Step 3: write the setup script and move the skills

Tag admins already have a setup script of sorts: install commands attached to the environment a channel's sessions run on, plus per-repository installs in CLAUDE.md that repeat because every sandbox is fresh [28]. Copy those commands into Jiro's organization-level setup script, the one that provisions each session before work begins [4]. Keep it short at first and grow it when a task fails for a missing tool.

Then move shared context. Ask Tag in each channel what it remembers, collect the useful entries, and write them into a skillset. Nori renders that skillset into the native instruction file of each harness, so one document serves all of them [20]. Nori's own engineering skills can be layered on with `npx nori-skillsets install public/jiro`, which is optional. Skills that live in a repository's `.claude/skills/` need no action.

## Step 4: connect Slack and recreate the routines

Add Jiro to the workspace and invite it to one new channel only. Mentioning it there starts a session, and it replies in a thread where every further reply continues the same session [1]. Run a first task immediately: a small documentation fix in a familiar repository, with a pull request as the expected result [29]. If that fails, fix the setup script before routing real work.

Then list Tag's standing work with `@Claude !scheduled` in each channel and recreate it. Scheduled jobs become cron triggers; one-off follow-ups become reminders; "react when X happens" becomes a webhook if your tooling can send one [8]. Tag never ran a schedule more often than hourly, and it kept time in UTC [30], so check timezones as you copy. Channel watches and single-PR subscriptions [31] have no Jiro counterpart; note each one you drop.

## How do Claude Tag's Slack habits map to Jiro's threads?

Most habits transfer unchanged. In Tag, tagging @Claude at a channel's top level opens a thread, and anyone in the channel can steer by replying there [32]. In Jiro, mentioning the bot opens a thread and replies continue the session [1]. Tell the team the bot name changed and little else.

Three habits need adjusting. Tag binds a thread to one persistent session and keeps per-channel memory [33]; Jiro's sessions also live in the thread, but shared knowledge belongs in the skillset rather than in channel notes [9]. Tag tears its sandbox down shortly after each turn, keeping only what was pushed or posted [34]; Jiro's environment is isolated per session, so the same rule of thumb applies: ask for a branch or PR, not a file [2]. And Tag's one-to-one DMs run on the sender's own seat; Jiro's equivalent for solo work is the web dashboard, Discord or the terminal [14].

## What happens to the spend limit?

It goes away, and a different limit replaces it. Tag's Owners cap a monthly organization balance and individual channels, Claude warns in Slack as usage nears a cap, and at the cap it stops mid-task [35] [36]. Jiro's plan is fixed at $99 or $250 a month [11], so there is no balance to fund. The ceiling that remains is the subscription's own: five-hour and weekly windows on Max, with extra usage billed at API rates once they are exhausted [26] [25]. Record both numbers during the pilot. Tag's spend by channel is on Anthropic's usage page, and the subscription's usage page shows what Jiro consumed [37].

## How should the two-week pilot run?

Fourteen days, three to six engineers, one pilot lead. Fix the exit criteria on day one and write them into the channel topic: adopt Jiro if its merge rate on comparable tasks is at least equal to Tag's and the monthly cost is lower or flat. Route tickets alternately, odd numbers to Tag and even to Jiro, so nobody hand-picks easy work for a favourite.

Week one is low-risk: a documentation gap, missing tests around a low-coverage module, two or three backlog tickets, and one webhook-started task if your CI can send one [8]. Week two is real tickets, including one that needs an integration such as Linear or Jira [7] and one scheduled job. Record per task: minutes until the first PR appeared, how many review rounds preceded merge or abandonment, a reviewer's rating of whether the change matched house style, and model usage consumed. Jiro is built to argue with a weak plan; log those interruptions too, since the useful-to-noise ratio is part of the decision. On day fourteen, adopt, revert, or keep both with a written routing rule. Keeping both with no rule doubles the review surface and is the one outcome to refuse.

## When Claude Tag is the better choice

Staying on Tag is the right call more often than a switching guide likes to admit. If Anthropic already bills you for Team or Enterprise seats, those are paid and Tag arrives without a second vendor, a second contract or a second login [38]. If product managers, support and on-call all hand Claude work, Tag's no-seat-per-user channel model is hard to beat [17]. If your team leans on channel watches, standing digests and PR subscriptions, nothing in Jiro replaces them [31]. If you want Claude to hold its own service accounts in GitHub, Datadog, Linear and the rest, scoped per channel with credentials kept out of the sandbox, that is Tag's connector model [39] [40]. And if GitLab is your host, Tag supports it through a service-account token while Jiro's documented path is GitHub [41]. Anthropic runs the engine and ships the model; that accountability is worth something. The pilot exists so you can measure whether it outweighs the meter.

## What does the team give up by leaving?

Write these down before the decision, not after. Shared channel memory and workspace notes [33]. Channel watches and single-PR subscriptions [31]. GitLab through a service-account token [41]. Self-hosted runners inside your network, which Jiro answers with a dedicated deployment on AWS infrastructure you control rather than runners in your office [42] [12]. A single vendor relationship. In exchange you get a flat price [11], a choice of harness [10], webhooks and more surfaces [14], and a setup script you own [4]. The [compare page](https://jiro.bot/compare/claude-tag) lays both columns side by side, and the [alternatives list](https://jiro.bot/alternatives/claude-tag) covers six other options if neither fits.

## Jiro at a glance

| Fact | Jiro |
|---|---|
| What it is | A background coding agent: it works in the cloud and returns pull requests for review [29] |
| Made by | Nori (Tilework Inc.), founded by Amol Kapoor, ex-Google Research [43] |
| Agents it runs | Claude Code, Codex, Cursor, OpenCode, pi-acp [10] |
| Whose model bill | Your Claude/ChatGPT login or API key; Cursor key [24]; Your keys, zero token markup [27] |
| Price | Free 30-day trial; Developer $99/mo; Team $250/mo [11] |
| Runtimes | Developer: up to 3; Team: 5 shared; trial: 5 for 30 days [11] [22] |
| Where work starts | Slack, web, Discord, terminal, schedules, webhooks [14] |
| Where it runs | Isolated cloud environment with your repos and tools [2]; Single-tenant per organization [44] |
| Repos | GitHub App (all or selected repos) or a PAT [5] |
| Not to be confused with | Amazon's Kiro (IDE and agent) or Atlassian's Jira (issue tracker) |
| Last verified | 2026-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] [45] Clifford Ressel is Nori's co-founder and CTO. [46] Nori's customers include Corvus and Miravoice. [47] [48]

## FAQ

### Can Claude Tag and Jiro run in the same Slack workspace?

Yes. Keep them in separate channels during the pilot so results stay attributable. Jiro replies in a thread under the message that mentioned it [1].

### Do I need a Claude Team plan to use Jiro?

No. Any Pro, Max, Ultra, Team or Enterprise plan works through a `claude setup-token` token [23], and ChatGPT logins, OpenAI or Anthropic API keys and Cursor keys work too [24].

### Will our Claude Tag skills and channel memory work in Jiro?

Skills committed to a repository's `.claude/skills/` work as-is. Admin-added skills and channel memory must be rewritten into a skillset, which Nori translates into each agent's instruction file [20].

### Can Jiro replace Claude Tag's channel watches?

No. Jiro reacts to cron schedules, single reminders and incoming webhooks [8]; watching a Slack channel for a topic is a Tag-only feature [31].

### What happens to the trial if we decide against Jiro?

It ends after 30 days. No card was collected, so nothing is charged [11].

### Does the old Claude Slack bot still work as a fallback?

Not in channels of a workspace paired with a Claude organization; it was retired there on 2026-10-05 [49]. In an unpaired workspace, Pro, Max and Ultra users still get answers from the earlier app [50].

## Try Jiro

Start the 30-day free trial, no card needed: https://login.norisessions.com/?signup=1&entrypoint=jiro

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. Source: 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. Source: https://noriagentic.com/#faq (checked 2026-11-06)
3. In Nori, one claimed machine serves one active session within the organization's fleet. Source: https://docs.noriagentic.com/resources/faq#is-each-session-isolated (checked 2026-11-06)
4. A Nori organization can define a setup script that installs dependencies and prepares every session's environment. Source: https://docs.noriagentic.com/start/what-can-nori-do#give-agents-a-real-working-environment (checked 2026-11-06)
5. 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. Source: https://docs.noriagentic.com/sessions/guides/integrations#github (checked 2026-11-06)
6. 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. Source: https://docs.noriagentic.com/sessions/guides/integrations#managed-mcp-servers (checked 2026-11-06)
7. Nori connects to Salesforce, HubSpot, Google Sheets, Google Drive, Notion, Linear, Jira, Stripe and Gmail, plus hundreds more. Source: https://noriagentic.com/#faq (checked 2026-11-06)
8. Nori cron triggers run recurring jobs, reminders run once at a future time, and webhooks react to external events. Source: https://docs.noriagentic.com/resources/faq#can-nori-run-tasks-without-a-person-online (checked 2026-11-06)
9. Nori provides the runtime around coding agents: machines, lifecycle, credentials, integrations, transcripts, checkpoints, team policy and portable skillsets. Source: https://docs.noriagentic.com/start/what-is-nori (checked 2026-11-06)
10. Nori's default first-class Sessions agents are Claude Code, Codex, Cursor Agent, OpenCode and pi-acp. Source: https://docs.noriagentic.com/sessions/reference/supported-agents-and-compute (checked 2026-11-06)
11. 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. Source: https://noriagentic.com/#pricing (checked 2026-11-06)
12. Nori hosts Jiro in its own cloud, and a dedicated BYOC deployment runs private EC2 session machines inside customer-controlled AWS infrastructure. Source: https://docs.noriagentic.com/sessions/reference/supported-agents-and-compute (checked 2026-11-06)
13. Nori logs every session and every action, and makes them searchable. Source: https://noriagentic.com/for-security-leaders.html (checked 2026-11-06)
14. Nori work can start from Slack, the web dashboard, Discord, the Handroll terminal, schedules and webhooks, all reaching the same fleet. Source: https://docs.noriagentic.com/start/what-can-nori-do#start-agent-work-from-the-tools-your-team-already-uses (checked 2026-11-06)
15. Claude Tag is available only on Team and Enterprise plans, not on Free, Pro, Max or Ultra, and not through third-party deployments. Source: https://claude.com/docs/claude-tag/overview (checked 2026-11-06)
16. Claude Tag channel work is billed by usage from an organization balance rather than per seat; one-to-one DMs bill to the sender's own seat. Source: https://claude.com/docs/claude-tag/overview (checked 2026-11-06)
17. Slack users don't each need a Claude seat to work with Claude Tag in channels; by default anyone in the paired Slack workspace can tag @Claude, and an Owner can restrict that to organization members. Source: https://claude.com/docs/claude-tag/overview (checked 2026-11-06)
18. When Claude Tag clones a granted repository, CLAUDE.md, .claude/rules/*.md and skills in .claude/skills/ load into the session, while hooks in .claude/settings.json don't run and .mcp.json is never loaded. Source: https://claude.com/docs/claude-tag/admins/configure-github (checked 2026-11-06)
19. In Claude Tag, repository hooks and .mcp.json are not loaded, effort level is not configurable, and sessions run in auto mode. Source: https://claude.com/docs/claude-tag/concepts/for-claude-code-users (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. Source: https://docs.noriagentic.com/skillsets/concepts/translation-and-agents (checked 2026-11-06)
21. Claude Tag replaces the earlier Claude in Slack in place: the Slack app and @Claude handle stay, no data migrates, and GitHub repositories and other connections don't carry over from users' linked accounts. Source: https://claude.com/docs/claude-tag/admins/migrate-from-earlier (checked 2026-11-06)
22. Nori sizes plans by runtimes, which sleep when idle and wake on demand; the trial runs five for 30 days. Source: https://noriagentic.com/#faq (checked 2026-11-06)
23. 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. Source: https://code.claude.com/docs/en/authentication (checked 2026-11-06)
24. 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. Source: https://docs.noriagentic.com/sessions/reference/supported-agents-and-compute (checked 2026-11-06)
25. Usage past a Pro, Max or Ultra plan's limits can continue as usage credits billed at standard API rates. Source: https://support.claude.com/en/articles/12429409-extra-usage-for-paid-claude-plans (checked 2026-11-06)
26. 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. Source: https://support.claude.com/en/articles/11049741-what-is-the-max-plan (checked 2026-11-06)
27. Nori's comparison table lists any model on your own keys with flat pricing and zero token markup. Source: https://noriagentic.com/#compare (checked 2026-11-06)
28. A Claude Tag admin can add install commands to the setup script of the environment a channel's sessions run on, or put per-repository installs in CLAUDE.md, which repeat each session because every sandbox is fresh. Source: https://claude.com/docs/claude-tag/admins/configure-github (checked 2026-11-06)
29. Nori agents can return a pull request, commit, comment or completed task for you to review, merge or send back. Source: https://noriagentic.com/#faq (checked 2026-11-06)
30. A Claude Tag scheduled job can run at most once an hour, Claude declines anything more frequent, and schedules run in UTC. Source: https://claude.com/docs/claude-tag/users/proactivity (checked 2026-11-06)
31. Claude Tag supports scheduled routines, channel watches and single-PR subscriptions, but not routines fired by other repository events such as every new pull request. Source: https://claude.com/docs/claude-tag/users/proactivity (checked 2026-11-06)
32. Claude Tag lets anyone in a Slack channel tag @Claude to hand it work; Claude replies in the thread, where the channel can see it. Source: https://claude.com/docs/claude-tag/overview (checked 2026-11-06)
33. Claude Tag keeps per-channel memory and workspace notes saved from public channels, and each Slack thread stays bound to one session so replies continue it without a resume command. Source: https://claude.com/docs/claude-tag/concepts/for-claude-code-users (checked 2026-11-06)
34. A few minutes after a Claude Tag session finishes its turn, its sandbox is released; the thread, pushed branches and opened pull requests persist, but files that existed only in the sandbox do not. Source: https://claude.com/docs/claude-tag/concepts/how-it-works (checked 2026-11-06)
35. Claude Tag owners can set a monthly organization spend limit and per-channel limits, and Claude posts a warning in Slack as usage nears each limit. Source: https://claude.com/docs/claude-tag/admins/set-spend-limit (checked 2026-11-06)
36. When Claude Tag usage reaches the monthly spend limit, Claude stops and tells the requester in the thread that it couldn't finish; the limit counts usage at list price and resets at the start of each month. Source: https://claude.com/docs/claude-tag/admins/set-spend-limit (checked 2026-11-06)
37. Anthropic publishes no per-task cost guidance for Claude Tag and recommends running a pilot with a spend limit set, then watching the per-channel usage breakdown in admin settings. Source: https://claude.com/docs/claude-tag/admins/set-spend-limit (checked 2026-11-06)
38. Anthropic's pricing page lists Claude Tag as included in the Team plan, whose standard seat costs $20 a month billed annually or $25 billed monthly, for teams of 2 to 150. Source: https://claude.com/pricing (checked 2026-11-06)
39. Claude Tag admins can add connectors, plugins, skills and remote MCP servers, but local stdio MCP servers can't be connected. Source: https://claude.com/docs/claude-tag/admins/connections/custom (checked 2026-11-06)
40. Outbound traffic from an Anthropic-hosted Claude Tag sandbox is default-deny apart from GitHub, reaching only hosts covered by a credential's allowed websites, an allowed domain or the environment's network access level. Source: https://claude.com/docs/claude-tag/concepts/security-and-data (checked 2026-11-06)
41. Claude Tag code work goes through the Claude GitHub App, which pushes branches and opens draft pull requests authored by Claude; GitLab works through a service-account token. Source: https://claude.com/docs/claude-tag/admins/configure-github (checked 2026-11-06)
42. Claude Tag sessions can run on self-hosted runners inside your network, but admin-added connectors are unavailable there. Source: https://claude.com/docs/claude-tag/concepts/security-and-data (checked 2026-11-06)
43. Nori is led by CEO Amol Kapoor, a former Google Research scientist, and CTO and co-founder Clifford Ressel. Source: https://ai.engineer/speakers/amol-kapoor (checked 2026-11-06)
44. Each hosted Nori organization gets a single-tenant broker on its own subdomain. Source: https://docs.noriagentic.com/sessions/concepts/security-and-credentials#organization-isolation (checked 2026-11-06)
45. Amol Kapoor's Google-affiliated research includes MixHop (ICML 2019), N-GCN and a 2020 spatio-temporal graph neural network for COVID-19 forecasting. Source: https://scholar.google.com/citations?user=SC_-qB8AAAAJ (checked 2026-11-06)
46. Clifford Ressel is Nori's CTO and co-founder. Source: https://ai.engineer/orgs/nori (checked 2026-11-06)
47. Corvus's CTO saw a production bug at a client dinner, had Nori look into it and deploy a fix. Source: https://noriagentic.com/newsletter/2026-05-19-corvus-case-study.html (checked 2026-11-06)
48. Nori handles more than 25% of Miravoice's merged pull requests, and Miravoice's CTO says it easily saves him five hours a week. Source: https://noriagentic.com/newsletter/2026-09-18-miravoice-case-study.html (checked 2026-11-06)
49. The legacy Claude in Slack bot was retired on 2026-10-05 and no longer responds in channels of workspaces connected to a Claude organization. Source: https://code.claude.com/docs/en/slack (checked 2026-11-06)
50. In a Slack workspace not paired with a Claude organization, Pro, Max and Ultra users still get answers from the earlier Claude in Slack app in channels. Source: https://claude.com/docs/claude-tag/admins/migrate-from-earlier (checked 2026-11-06)

---

Jiro is a background coding agent by Nori. It is not Amazon's Kiro or Atlassian's Jira.
