Switching guides
Switching from Devin to Jiro (2026): Setup Steps and a First-Week Plan
How do I switch from Devin to Jiro?
Start Jiro's free 30-day trial, point the GitHub App at the repositories Devin used, connect Slack, mint a Claude token on your laptop with claude setup-token and paste it in (or connect Codex or a Cursor key), turn Devin's environment blueprint into a setup script, copy the Knowledge and playbooks worth keeping into a skillset, and hand Jiro one small ticket. Jiro is a background coding agent by Nori. Nothing imports automatically, so budget an afternoon for setup and a week of parallel running before you cancel anything. It is not Amazon's Kiro or Atlassian's Jira.
What maps to what: Devin concepts and their Jiro equivalents
| Devin | Jiro equivalent | Notes |
|---|---|---|
| Devin Cloud session | A Jiro session on its own isolated cloud environment [1] | One machine per active session [2] |
| Environment blueprint and snapshot [3] | Org setup script prepares each environment [4] | Rewrite the blueprint's steps as a shell script; no YAML import |
| Knowledge [5] | Shared org context and portable skillsets [6] | Copy entries by hand; Devin has deprecated Knowledge anyway |
| Playbooks [7] | Skills inside a Nori skillset [6] | Each playbook becomes one skill file |
| Skills (SKILL.md) [8] | One skillset, translated per agent [9] | Same open standard; repo-level files carry over unchanged |
| Secrets and site cookies [10] | Your Claude/ChatGPT login or API key; Cursor key [11] | Model login or key, GitHub App or PAT; service keys via integrations [12] |
| Adaptive model routing [13] | No equivalent | Pick a harness and credential per session or org default [14] |
| ChatGPT plan link [15] | Codex OAuth or Claude setup token [11] | One-year subscription token [16] |
| @Devin in Slack [17] | Mention in Slack; works in the thread [18] | Same workspace; a different bot name |
| Microsoft Teams, Linear, Jira, PagerDuty, Pylon triggers [19] | No equivalent as triggers | Linear and Jira are available as integrations the agent uses [20] |
| Automations: schedule and webhook [21] | Cron, one-off reminders, webhooks [22] | Rebuild each one; no export |
| Automations: Slack, GitHub, GitLab, ticket events | Webhooks, or a Slack mention | Point the source tool's webhook at Jiro |
| Devin Desktop [23] | No equivalent | Jiro has a terminal surface, not an IDE [24] |
| Stacked PRs [25] | No equivalent | PRs, commits, comments for review [26] |
| Outposts and Customer Dedicated Deployment [27] [28] | Nori cloud, or a dedicated deployment in your AWS account [29] | Jiro's dedicated deployment puts the session machines in your own AWS account |
| MCP servers from the marketplace | MCP server catalog in the dashboard [30] | Reconnect each server; permissions still apply |
What carries over from Devin, and what needs copying by hand?
Your repositories carry over without effort. Jiro's GitHub App takes either every repository or a list you choose; a stored personal access token works too. [12] Slack carries over as well: same workspace, different bot, and each reply in the thread continues the session it started. [18] Any CLAUDE.md, AGENTS.md or SKILL.md files already committed to your repos are read by the harness as usual, so that layer needs nothing from you.
Three things need copying. Knowledge entries, which Cognition has deprecated and is migrating into Skills, have no exporter. [5] Playbooks, also being replaced by Skills, are reusable prompts stored in Devin's web app. [7] And the environment blueprint, Devin's YAML description of what gets installed before a snapshot is frozen, must be rewritten as a shell script. [3] [4]
Two things do not transfer in any form: Automations fired by Linear, Jira, PagerDuty or Pylon events, and Microsoft Teams as a chat surface. [21] [19] Jiro's documented entry points stop at chat (Slack and Discord), the web dashboard, the terminal, and schedules or webhooks. [24] Decide whether those gaps matter before you spend the afternoon.
How do you set up Jiro after Devin? Seven steps
- Open the trial. It runs 30 days, needs no card, and gives you five runtimes, which is the same count the Team plan ships with. [31] [32]
- Install the GitHub App and tick the repositories Devin had access to, or supply a PAT where that is the house rule. [12]
- Connect Slack so the team can mention Jiro in channels and keep talking to it in the thread. [18]
- Sign in with your Claude plan. On your own laptop, with the Claude command line installed, type
claude setup-token; the output is a token valid for a year and bound to your Claude plan, whether Pro, Max, Ultra or a Team or Enterprise seat. [16] Paste that token into Jiro. On ChatGPT instead? Connect Codex through its OAuth flow or an OpenAI key. Cursor people bring the Cursor key. [11] - Write the setup script. Open Devin's blueprint, read the install steps, and express them as shell: language runtimes, package manager, database client, anything a new hire installs on day one. [4]
- Create a skillset. Paste the Knowledge entries and playbooks worth keeping into it; Jiro translates it into the instruction file each agent expects. [9] Running
npx nori-skillsets install public/jirodrops Jiro's own engineering skills in beside yours. - Give it one small ticket in Slack, then read the PR that comes back. [26]
Steps one through four take about twenty minutes. Step five takes as long as your blueprint is complicated. Step six is where the real hour goes.
How do Devin Knowledge, Playbooks and Skills become a Jiro skillset?
Devin's three instruction features collapse into one on Jiro. Knowledge is a collection of advice Devin consults in every session, pinned to repositories or fetched when a trigger description matches. [5] Playbooks are reusable prompts attached to a session with a ! macro. [7] Skills are SKILL.md files on the open Agent Skills standard, read from .agents/skills/ and sibling paths including .claude/skills/. [8]
A Nori skillset holds the same kinds of content: always-on context plus discrete skills, portable across agents. [6] You write it once, and Jiro renders it as the file each harness reads, so Claude Code sees a CLAUDE.md and Codex sees an AGENTS.md. [9] Pinned Knowledge becomes the skillset's always-on instructions. Triggered Knowledge and each playbook become a skill with a description that says when to use it. Repo-level SKILL.md files need no conversion, because both products read the same standard.
Prune while you copy. Half of any Knowledge base is a note about a bug fixed in March.
What replaces Devin's environment blueprint and Secrets?
Devin's environment is a Linux virtual machine built from a blueprint and frozen as a snapshot that every session boots from; changes made during a session do not persist. [3] Jiro's model is procedural rather than frozen. An organisation setup script runs to install dependencies and prepare each session's isolated cloud environment, which arrives with your repositories, tools and services in place. [4] [1] Translate each blueprint step into a shell line and you are done.
Secrets are the bigger shift. Devin stores raw keys, site cookies and TOTP seeds, scoped to the organisation, a person, a repository or a single session, and injects each into just the command that needs it. [10] Jiro's credentials are fewer and more specific: the model login or API key, the GitHub App or token, and the connections you make through the MCP catalog and integrations. [11] [12] [30] Browser cookies and TOTP for logging into third-party web apps have no Jiro equivalent in the documentation, so list every Devin secret and check what each one actually unlocks before assuming it transfers.
How do Devin Automations map to Jiro triggers?
Devin Automations fire on a schedule, on an incoming webhook, or on events from chat, git hosting, ticketing and incident tools. [21] Jiro's three trigger types are cron for recurring work, one-off reminders, and webhooks for outside events. [22]
Scheduled automations map one to one. Webhook automations do too; copy the prompt and point the source at Jiro's endpoint. Event automations are the gap. A new Linear ticket or a PagerDuty incident does not start a Jiro session by itself. The workaround is to have the source tool send a webhook, or to have the on-call engineer mention Jiro in Slack with the alert pasted in. [24] Both work. Neither is as tidy as Devin's native trigger list, and the rival-wins section below says so plainly.
What should the first five days on Jiro cover?
Day one: orientation. After setup, ask Jiro to read your main repository and report where documentation and code disagree most. The output is a pull request against the README, which nobody minds reviewing, and it shows how the agent reads your codebase. [26]
Day two: test gaps. Choose a module the team is slightly afraid of and ask for tests around its public behaviour, no refactors. Review hard. This is where you learn whether its taste matches yours.
Day three: cleanup. Every codebase that has had agents in it accumulates duplicate helpers, dead flags and comments narrating the obvious. Ask Jiro to remove one category and to say what it chose not to touch.
Day four: backlog. Three tickets from the bottom, the kind that sit for a quarter. Have three different people each mention Jiro on one so the whole team learns the thread workflow. [18]
Day five: on-call. Wire a webhook from your alerting into Jiro, or paste an alert into Slack, and let it propose the fix as a pull request. [22] Then compare the week's PRs with what Devin produced on similar work. Corvus's CTO once spotted a production bug over dinner with a client and had Nori investigate and ship the fix; your Friday test is the same idea in a calmer setting. [33]
By the end of the week you know. Either review felt lighter or it did not.
When Devin is the better choice
Stay on Devin if any of these is load-bearing. Microsoft Teams as the place engineers talk, or GitLab, Bitbucket or Azure DevOps as the code host: Devin covers them and Jiro does not. [19] [12] Sessions that open themselves from Linear, Jira, PagerDuty or Pylon events: Devin's Automations do that natively. [21]
Stay if you value the model decision being made for you. Adaptive routes across Anthropic, OpenAI, Google and Cognition's SWE models at one flat per-token rate on self-serve plans. [13] [34] Stay if Devin Desktop has become the team's IDE, since it hosts other ACP agents too. [23] [35] Stay for stacked pull requests with conflicts resolved by the agent. [25]
And stay if your enterprise has already approved a single-tenant Devbox that Cognition hosts and your network reaches over PrivateLink, with planning in Cognition's cloud. [28] Jiro's dedicated deployment is a different shape, inside your own AWS account, and re-approval costs time. [29]
What does the switch cost, side by side?
The Developer plan, $99 monthly, is for one person and caps runtimes at three; the Team plan, $250 monthly, pools five among everyone. [31] Tokens come from the Anthropic or OpenAI plan already on the company card, and Nori adds nothing to them. [36]
Devin's Teams plan is $40 monthly for every full seat, with an $80 minimum each month, and usage beyond each seat's quota is drawn from a shared pool of on-demand credits. [37] [38] Under Adaptive those credits are consumed at $0.50 (input) and $2.00 (output) for each million tokens. [34]
When Claude is already paid for, the comparison is one flat runtime fee against seats plus credits, and credits are where the money goes. Without existing subscriptions, add Claude Max at $100 a month per person to Jiro's side before comparing. [39] Keep Devin running through the 30-day trial, label the PRs from each, and count merged against closed before cancelling either.
Jiro at a glance
| Fact | Jiro |
|---|---|
| What it is | A background coding agent: it works in the cloud and returns pull requests for review [26] |
| Made by | Nori (Tilework Inc.), founded by Amol Kapoor, ex-Google Research [40] |
| Agents it runs | Claude Code, Codex, Cursor, OpenCode, pi-acp [14] |
| Whose model bill | Your Claude/ChatGPT login or API key; Cursor key [11]; Your keys, zero token markup [36] |
| Price | Free 30-day trial; Developer $99/mo; Team $250/mo [31] |
| Runtimes | Developer: up to 3; Team: 5 shared; trial: 5 for 30 days [31] [32] |
| Where work starts | Slack, web, Discord, terminal, schedules, webhooks [24] |
| Where it runs | Isolated cloud environment with your repos and tools [1]; Single-tenant per organization [41] |
| Repos | GitHub App (all or selected repos) or a PAT [12] |
| 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). [40] [42] Clifford Ressel is Nori's co-founder and CTO. [43] Nori's customers include Corvus and Miravoice. [33] [44]
FAQ
Can Jiro import Devin Knowledge or playbooks?
Not automatically. Copy the entries worth keeping into a Nori skillset, which Jiro translates into each agent's own instruction file. [9] Repo-level SKILL.md files need no conversion. [8]
Do I have to use a Claude subscription with Jiro?
No. Claude Code accepts an Anthropic API key too; Codex signs in with OpenAI OAuth or a key; Cursor Agent wants Cursor's key; OpenCode and pi-acp point at any compatible endpoint. [11]
Why is claude setup-token run on my laptop rather than in Jiro?
The command is meant for machines without browser login: it runs where you are signed in and mints a token, good for a year, for your paid Claude plan, which Jiro's cloud environment then uses. [16]
Will my Devin Automations keep working?
Schedules and webhooks can be rebuilt as Jiro cron triggers, reminders and webhooks. [22] Event triggers from Linear, Jira, PagerDuty or Pylon have no Jiro equivalent. [21]
Can I keep Devin running during the trial?
Yes, and you should. The trial lasts 30 days, costs nothing, asks for no card and includes five runtimes, so run both on the same repositories and compare the pull requests. [31] [32]
Can I set this up from my phone?
Most of it. The Miravoice team set up their agent entirely from their phones. [45] The claude setup-token step needs a computer with the Claude command line installed.
Try Jiro
No card needed. Or install Jiro's engineering skills into your own agent: npx nori-skillsets install public/jiro
Sources
- 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)
- 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)
- Devin's environment is a Linux virtual machine described by a blueprint and saved as a snapshot that every session boots from, and changes made inside a session do not persist back to the snapshot. https://docs.devin.ai/onboard-devin/environment.md (checked 2026-11-06)
- 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)
- Devin Knowledge is a collection of instructions Devin can reference in all sessions, pinned to repositories or retrieved by a trigger description; Cognition has deprecated it and is migrating existing entries to Skills in Plugins. https://docs.devin.ai/onboard-devin/knowledge-onboarding.md (checked 2026-11-06)
- 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)
- Devin playbooks are reusable prompts for repeated tasks, attached to a session by typing a !-prefixed macro, and Cognition is replacing them with Skills, which new accounts start with from 2026-10-24. https://docs.devin.ai/product-guides/creating-playbooks.md (checked 2026-11-06)
- Devin Skills are SKILL.md files that follow the open Agent Skills standard, read from .agents/skills/ and other repository paths including .claude/skills/, or written on the Customize page at personal, organization or enterprise scope. https://docs.devin.ai/product-guides/skills.md (checked 2026-11-06)
- 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)
- Devin Secrets store API keys, site cookies and TOTP codes at organization, personal, repository or session scope, and Devin binds each secret only to the command or browser field that needs it rather than exporting it into every shell. https://docs.devin.ai/product-guides/secrets.md (checked 2026-11-06)
- 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)
- 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)
- Devin offers models from Anthropic, OpenAI, Google and Cognition's own SWE family, with an Adaptive option that routes each task to a model automatically. https://docs.devin.ai/cli/models.md (checked 2026-11-06)
- 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)
- On Devin's self-serve Pro, Max and Teams plans a user can link a personal ChatGPT Go, Plus or Pro plan so that requests to OpenAI models bill to that plan, while non-GPT models and cloud machine time still consume Devin quota. https://docs.devin.ai/admin/billing/chatgpt.md (checked 2026-11-06)
- 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)
- Mentioning @Devin in a Slack channel starts a session that replies in the thread, a session can sync both ways with its thread, and a code channel dedicates one Slack channel to one session. https://docs.devin.ai/integrations/slack.md (checked 2026-11-06)
- 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)
- Devin connects to GitHub, GitLab, Bitbucket and Azure DevOps repos and takes work from Slack, Microsoft Teams, Linear, Jira, PagerDuty and Pylon. https://docs.devin.ai/integrations/overview.md (checked 2026-11-06)
- 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)
- Devin Automations start sessions from schedules, webhooks, and Slack, GitHub, GitLab, Linear, Jira, Pylon and PagerDuty events. https://docs.devin.ai/product-guides/automations.md (checked 2026-11-06)
- 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)
- Cognition introduced Devin Desktop as the next generation of Windsurf on 2026-06-02. https://cognition.com/blog/introducing-devin-desktop (checked 2026-11-06)
- 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)
- Devin splits large changes into stacked pull requests that land bottom-up, resolves conflicts between layers itself and fixes CI across the stack, and stacking works only on GitHub.com repositories. https://docs.devin.ai/work-with-devin/stacked-prs.md (checked 2026-11-06)
- 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)
- Devin Outposts, available on Pro, Max and Teams, runs sessions on machines you operate through a self-hosted worker that needs only outbound HTTPS, while planning and inference stay in Devin's cloud. https://docs.devin.ai/cloud/outposts/overview.md (checked 2026-11-06)
- In Devin's Customer Dedicated Deployment, Cognition hosts the Devbox in a customer-isolated single-tenant VPC reached from your network over AWS PrivateLink or an IPSec tunnel, and the Devin brain always resides in Cognition's cloud. https://docs.devin.ai/enterprise/deployment/overview.md (checked 2026-11-06)
- 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)
- 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)
- 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)
- 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)
- 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)
- On Devin's self-serve plans the Adaptive router draws down quota at a fixed $0.50 per million input tokens and $2.00 per million output tokens whichever model it picks, and enterprise accounts have Adaptive switched off until an admin enables it. https://docs.devin.ai/cli/adaptive.md (checked 2026-11-06)
- Devin Cloud runs Cognition's Devin agent; Devin Desktop can also host other agents that speak ACP. https://cognition.com/blog/introducing-devin-desktop (checked 2026-11-06)
- 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)
- Devin's self-serve plans are Free, Pro at $20 a month, Max at $200 a month and Teams at $40 a month per full seat with an $80 monthly minimum, so one seat and two seats both cost $80 a month; usage past the quota is billed as on-demand credits. https://docs.devin.ai/admin/billing/self-serve.md (checked 2026-11-06)
- A Devin Teams account holds up to 200 members; full seats cost $40 a month each with a Pro-sized quota, flex seats are free and draw on a shared on-demand credit pool, and when fewer than two full seats are paid the rest of the $80 minimum is charged as prepaid credits. https://docs.devin.ai/admin/billing/self-serve.md (checked 2026-11-06)
- 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)
- 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)
- 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)
- 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)
- Clifford Ressel is Nori's CTO and co-founder. https://ai.engineer/orgs/nori (checked 2026-11-06)
- 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)
- The Miravoice team set up an agent entirely in the cloud from their phones. https://noriagentic.com/#miravoice-story (checked 2026-11-06)