---
title: "Switching from GitHub Copilot Coding Agent to Jiro (2026): Setup Steps and a First-Week Plan"
canonical: https://jiro.bot/switch/copilot-to-jiro
last_updated: 2026-11-06
---

# Switching from GitHub Copilot Coding Agent to Jiro (2026): Setup Steps and a First-Week Plan

Updated 2026-11-06

> **How do I switch from GitHub Copilot coding agent to Jiro?**
>
> Switching takes one afternoon of admin work: start Jiro's free trial, install its GitHub App on a pilot repository, generate a `claude setup-token` token locally and enter it in Jiro, then move .github/copilot-instructions.md into a skillset and copilot-setup-steps.yml into the org setup script. Jiro is a background coding agent by Nori. Keep Copilot's cloud agent enabled during the pilot, because the same skillset is translated back into copilot-instructions.md, so both agents follow identical rules. It is not Amazon's Kiro or Atlassian's Jira.

## What maps to what: Copilot cloud agent concepts and their Jiro equivalents

| Copilot concept | Jiro equivalent | Notes |
|---|---|---|
| .github/copilot-instructions.md | Skillset: One skillset, translated per agent [1] | Moved by hand; there is no importer |
| .github/instructions/*.instructions.md with applyTo globs | Individual skills inside the skillset | Scope by task rather than by file glob |
| AGENTS.md, CLAUDE.md in the repo | Kept in the repo; skillset output is written beside them | Shared org context and portable skillsets [2] |
| copilot-setup-steps.yml workflow | Org setup script prepares each environment [3] | Rewrite the workflow steps as shell |
| Settings > Copilot > MCP servers JSON | MCP server catalog in the dashboard [4] | Connected once for the organization |
| Assign an issue or PR comment to Copilot | Slack, web, Discord, terminal, schedules, webhooks [5] | No GitHub-issue assignment; mention the bot in Slack instead |
| Automations on a schedule or repository event | Cron, one-off reminders, webhooks [6] | Cron for recurring, reminder for one-off, webhook for events |
| GitHub-supplied models billed in AI Credits | Your Claude/ChatGPT login or API key; Cursor key [7] | Your keys, zero token markup [8] |
| Draft PR on a copilot/ branch | PRs, commits, comments for review [9] | Your branch protection decides what merges |
| Cloud sandbox or Actions runner with a 59-minute cap | Isolated cloud environment with your repos and tools [10] | One machine per active session [11] |
| Organization and enterprise Copilot policies | Single-tenant per organization [12]; Every session and action logged [13] | Scope is the GitHub App's installation list |
| Microsoft Teams, Jira and Azure Boards entry points | No equivalent | Jiro does not start work from these |
| Copilot Business or Enterprise seats | Free 30-day trial; Developer $99/mo; Team $250/mo [14] | Flat fee; model usage stays on your own bill |

Rows marked 'No equivalent' are genuine gaps, not omissions.

## Who is this guide for?

This guide is for the person who owns the GitHub organization settings at a team of somewhere between five and twenty engineers, where Copilot's cloud agent is already switched on and an Anthropic or OpenAI plan is already being paid for. That second condition matters more than the first. Jiro drives Claude Code and Codex with the subscription login or API key your team holds already, and Cursor Agent with a Cursor key [7], with no markup on tokens [8]. Should no one on the team hold a Claude or ChatGPT plan, read the billing section first. Budget one afternoon for setup and one week for the pilot.

## Which product am I actually leaving?

The thing you enabled as the Copilot coding agent is documented today as the Copilot cloud agent, and GitHub now wraps it in an experience called Copilot in the cloud [15]. From 2026-10-28 that experience ships to every paid plan, with a cloud sandbox that can span multiple repositories in an organization alongside the older single-repository Actions environment [16]. The migration below works the same under either name. Where this page says Copilot, it means the cloud agent, not editor completions, which many teams keep.

## What migrates, what gets rebuilt, and what stays?

Three Copilot artifacts carry over, each by a different route. Instructions migrate by hand. Copilot reads `.github/copilot-instructions.md` for the whole repository, `.github/instructions/*.instructions.md` files scoped by `applyTo` globs, AGENTS.md files anywhere in the tree, and a root CLAUDE.md or GEMINI.md [17]. A Nori skillset is a single source that Nori renders into whichever file each agent reads: copilot-instructions.md for Copilot, CLAUDE.md for Claude Code, AGENTS.md for others [1], so the content moves into the skillset and flows back out.

Environment setup is rebuilt. The `copilot-setup-steps.yml` workflow, with its one mandatory job name and 59-minute timeout [18], becomes an organization setup script that prepares every session [3].

MCP configuration is re-entered. Copilot keeps a per-repository JSON block under Settings > Copilot > MCP servers [19], while Jiro offers an MCP catalog in its dashboard, connected once for the organization [4].

Copilot's session history, draft pull requests and issue assignments stay in GitHub. Nothing imports them, and nothing needs to.

## Step 1: start the trial and scope the GitHub App to one repository

Begin the free 30-day trial; no card is requested [14]. During sign-up Jiro asks for repository access. Choose the GitHub App rather than a personal access token, and install it on a selected set containing only the pilot repository instead of all repositories [20]. You will widen that selection later. Pick a repository with a decent test suite and an owner who reviews pull requests within a day, because the pilot's exit test is a merged PR, and a slow reviewer makes a good agent look idle. The trial runs five runtimes for 30 days [21], which is more than one repository needs.

## Step 2: `claude setup-token`, the Claude command-line sign-in

This is the step that makes Jiro run on your existing plan. Open a terminal on your own computer, one that already has Claude Code, and type `claude setup-token`. A browser sign-in follows, and the command then prints a token bound to the Claude plan you signed into, whether Pro, Max, Ultra, Team or Enterprise, good for one year and meant for headless machines with no browser login [22]. Enter it as Jiro's Claude Code credential.

Other accepted credentials: for Claude Code, an Anthropic API key or Claude OAuth; for Codex, an OpenAI API key or Codex OAuth; for Cursor Agent, a Cursor API key [7]. Whichever you choose, Nori charges nothing on top of the tokens [8]. Compare Copilot, where BYOK is documented for the IDEs, CLI, app and SDK and nowhere for the cloud agent [23]. Treat the token like a password. It is bound to the plan of whoever ran the command.

## Step 3: turn copilot-instructions.md into a skillset

Open `.github/copilot-instructions.md` and sort its contents into two piles. Repository-wide conventions, such as language, formatting, commit style and test commands, go into the skillset's top-level instructions. Narrow procedures, say writing a migration or shipping a release, each become a skill of their own. Path-scoped `.instructions.md` files with `applyTo` globs [17] usually map to one skill each, named for the task rather than the glob.

Nori provides the skillset layer along with machines, credentials, integrations and transcripts [2], and translates the result into each agent's native file, copilot-instructions.md included [1]. That translation is why you can leave Copilot running: it keeps reading rules that now live in one place. Install Jiro's own engineering defaults beside yours with `npx nori-skillsets install public/jiro`. Plan an hour for a typical instructions file. Resist rewriting the rules during the move. Change them after the pilot, when you can see what each agent did with them.

## Step 4: rewrite copilot-setup-steps.yml as the org setup script

Copilot preinstalls dependencies through `.github/workflows/copilot-setup-steps.yml`, which must contain a single job named `copilot-setup-steps`, honours only `steps`, `permissions`, `runs-on`, `services`, `snapshot` and `timeout-minutes`, and limits `timeout-minutes` to 59; runners are Ubuntu x64 or Windows only [18]. On the Jiro side the same job belongs to the organization's setup script, which readies each session's environment and installs what it needs [3].

Translate each `run:` step into shell. Drop the checkout step, because the repository is already present in the isolated cloud environment with your tools and services [10], and drop anything that existed only to satisfy the runner. One machine serves one active session [11], so the script runs per session, not per repository. Test it by starting a session and asking Jiro to run your test suite.

## Step 5: connect Slack and the MCP servers your team relies on

Connect Slack and invite the bot to the pilot team's channel. An @-mention opens a session and a thread; replying in that thread keeps talking to the same session [24]. Discord, the web dashboard, the terminal, schedules and webhooks all land on the same fleet [5].

Then re-create MCP access. In Copilot the GitHub and Playwright servers are on by default, and extra servers are JSON entries whose secrets must use `COPILOT_MCP_`-prefixed names [19]. In Jiro, an admin picks servers from the dashboard catalog, and each server's own permissions still apply [4]; Linear, Jira, Notion, Google Drive, Stripe and HubSpot are among the available integrations [25]. Connect only what the pilot needs.

## What should Jiro work on during week one?

Give it the work the team keeps postponing, one kind per day, all from the pilot channel.

- Day 1: reconcile the README and onboarding docs with what the code does now.
- Day 2: find the three least-tested modules and propose tests.
- Day 3: remove one piece of slop, for example a helper copied into four files.
- Day 4: two small backlog tickets, assigned in Slack.
- Day 5: point a webhook from your alerting at Jiro and let it take the next small fix [6].

Each piece of work returns for human review as a PR, commit or comment; merging or sending back is the reviewer's call [9]. Read the transcripts, not only the diffs; they exist because Nori keeps a searchable record of all sessions and their actions [13]. A good pilot shows Jiro questioning a vague ticket before writing code. Exit criteria: five merged PRs and reviewers who want to keep going.

## How does the bill change?

Copilot Business is $19 per user a month and Enterprise $39 [26], with 1,900 and 3,900 AI Credits per user included [27]. Since 2026-06-01 all usage is metered in those credits at $0.01 each [28], the allowance resets on the first of the month without carry-over, and a Business user who runs out has to ask an administrator for budget [29].

Jiro's platform fee is flat instead: Developer $99 monthly, Team $250 monthly with five runtimes shared among several users [14], and runtimes sleep when idle [21]. Model usage goes straight to Anthropic or OpenAI at their rates [8]; Claude Max, as a reference point, is priced at $100 a month with five times the usage of Pro [30]. If those plans already exist, the marginal cost of the move is the Jiro fee. If they do not, add them before comparing.

## Which Copilot controls have a Jiro counterpart?

Copilot's defaults are conservative and worth writing down before you leave: write-access-only triggering, pushes confined to a `copilot/` branch under branch protection, a firewall, CodeQL and secret scanning on generated code, human approval before Actions runs, and signed commits linked to session logs [31], plus organization and enterprise policy switches for MCP, models and features [32].

Jiro's counterparts are structural rather than per-feature. The broker serving your organization is single-tenant and lives on a subdomain reserved for you [12]; sessions and actions are recorded and searchable [13]; repository scope is the GitHub App's installation list [20]; and merges are decided by the branch protection you already enforce, because Jiro returns its work as a pull request for review [9]. Keep the Copilot checks on while both agents run.

## When staying on Copilot's cloud agent is the better choice

Do not move if any of these describe you. Copilot is already approved and paid for across your GitHub organization, with per-user pricing of $19 on Business and $39 on Enterprise [26], and adding a vendor costs more in review time than Jiro saves. Work arrives via Microsoft Teams, Jira or Azure Boards, or scripts call the agent through the REST API or GitHub MCP server [33]; Jiro's only starting points are Slack, Discord, the web dashboard, the terminal, schedules and webhooks. You need enterprise owners to pin MCP, model and feature policies for every organization [32]. You want the agent itself to be swappable within GitHub, which the third-party agents preview provides for Claude and Codex [34]. Or your tasks are short enough that the 59-minute Actions cap [35] has never been hit.

In each of those cases the honest advice is to stay, and to revisit when a constraint actually bites.

## Can Copilot and Jiro overlap during the pilot?

They should. Copilot keeps taking issue assignments and automations in GitHub while Jiro takes Slack requests, and because the skillset is translated back into copilot-instructions.md [1] both read the same rules. Give them the same category of task for two weeks, compare the merged results, then decide which seats to keep. Some teams retire Copilot's agent and keep its completions. For the whole field, see the [Copilot coding agent alternatives](https://jiro.bot/alternatives/copilot-coding-agent) ranking.

## Jiro at a glance

| Fact | Jiro |
|---|---|
| What it is | A background coding agent: it works in the cloud and returns pull requests for review [9] |
| Made by | Nori (Tilework Inc.), founded by Amol Kapoor, ex-Google Research [36] |
| Agents it runs | Claude Code, Codex, Cursor, OpenCode, pi-acp [37] |
| Whose model bill | Your Claude/ChatGPT login or API key; Cursor key [7]; Your keys, zero token markup [8] |
| Price | Free 30-day trial; Developer $99/mo; Team $250/mo [14] |
| Runtimes | Developer: up to 3; Team: 5 shared; trial: 5 for 30 days [14] [21] |
| Where work starts | Slack, web, Discord, terminal, schedules, webhooks [5] |
| Where it runs | Isolated cloud environment with your repos and tools [10]; Single-tenant per organization [12] |
| Repos | GitHub App (all or selected repos) or a PAT [20] |
| 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). [36] [38] Clifford Ressel is Nori's co-founder and CTO. [39] Nori's customers include Corvus and Miravoice. [40] [41]

## FAQ

### Does Jiro import copilot-instructions.md automatically?

No. You move the content into a skillset by hand; Nori then translates that skillset into copilot-instructions.md, CLAUDE.md and AGENTS.md [1].

### Is claude setup-token required for Jiro?

Only when Claude Code should bill to a Claude subscription. `claude setup-token` issues a token good for a year and bound to one of the Pro, Max, Ultra, Team or Enterprise plans [22]; an Anthropic API key, Codex OAuth, an OpenAI key or a Cursor key also work [7].

### Can we limit Jiro to specific repositories?

Yes. Install the GitHub App on just the repositories you choose, or on all of them [20]; begin with the pilot repository alone.

### What happens to copilot-setup-steps.yml?

It is rewritten as the org setup script that prepares every session [3]; the 59-minute workflow timeout and the mandatory job name do not carry over [18].

### Can Jiro take tasks from Jira or Microsoft Teams like Copilot?

No. Work reaches Jiro from Slack or Discord, from its dashboard or a terminal, or on a schedule or webhook [5]; Copilot adds Teams, Jira, Linear and Azure Boards [33].

### Should we cancel Copilot before the pilot ends?

No. Run both for at least two weeks; Copilot's draft PRs and controls keep working in GitHub [42], and many teams keep its editor completions afterwards.

## 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. 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)
2. 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)
3. 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)
4. 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)
5. 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)
6. 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)
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. Source: 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. Source: https://noriagentic.com/#compare (checked 2026-11-06)
9. 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)
10. 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)
11. 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)
12. 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)
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'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)
15. GitHub's Copilot cloud agent, now presented as Copilot in the cloud, researches a repository, plans changes and implements them in a GitHub cloud sandbox, a GitHub Actions environment or a remote environment you connect. Source: https://docs.github.com/en/copilot/concepts/agents/cloud-agent/about-cloud-agent (checked 2026-11-06)
16. Since 2026-10-28 paid Copilot plans get Copilot in the cloud on GitHub.com and GitHub Mobile, where the cloud sandbox can span several repositories in one organization and be resumed across clients, while the Actions-based environment is limited to a single repository and the GitHub website. Source: https://docs.github.com/en/copilot/concepts/agents/cloud-agent/about-cloud-agent (checked 2026-11-06)
17. Copilot reads repository-wide guidance from .github/copilot-instructions.md, path-specific rules from .github/instructions/NAME.instructions.md files with an applyTo glob, any number of AGENTS.md files, and a single root CLAUDE.md or GEMINI.md. Source: https://docs.github.com/en/copilot/how-tos/configure-custom-instructions/add-repository-instructions (checked 2026-11-06)
18. Dependencies for the cloud agent are preinstalled by a .github/workflows/copilot-setup-steps.yml workflow whose single job must be named copilot-setup-steps, with timeout-minutes of at most 59, on Ubuntu x64 or Windows GitHub-hosted, larger or self-hosted runners. Source: https://docs.github.com/en/copilot/how-tos/use-copilot-agents/cloud-agent/customize-the-agent-environment (checked 2026-11-06)
19. MCP servers for the cloud agent are configured as JSON under the repository's Settings > Copilot > MCP servers, with the GitHub and Playwright servers enabled by default, local and remote servers supported, secrets passed only through COPILOT_MCP_-prefixed names, and configured tools usable without approval. Source: https://docs.github.com/en/copilot/how-tos/use-copilot-agents/cloud-agent/extend-cloud-agent-with-mcp (checked 2026-11-06)
20. 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)
21. 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)
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. Source: https://code.claude.com/docs/en/authentication (checked 2026-11-06)
23. The cloud agent offers Auto plus GitHub-provided Claude, Gemini, GPT and MAI models; bring-your-own-key is documented for IDEs, Copilot CLI, the Copilot app and the SDK, not for the cloud agent. Source: https://docs.github.com/en/copilot/reference/ai-models/supported-models (checked 2026-11-06)
24. 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)
25. 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)
26. Copilot Pro is $10, Pro+ $39 and Max $100 a month; Business is $19 and Enterprise $39 a month per user; Copilot Free does not include the cloud agent. Source: https://docs.github.com/en/copilot/get-started/plans (checked 2026-11-06)
27. Copilot Pro includes 1,500 GitHub AI Credits a month, Pro+ 7,000 and Max 20,000; Business includes 1,900 credits per user a month and Enterprise 3,900 per user. Source: https://docs.github.com/en/copilot/get-started/plans (checked 2026-11-06)
28. Since 2026-06-01, all Copilot plans bill in GitHub AI Credits, which meter input, output and cached tokens at per-model rates, with one credit equal to $0.01. Source: https://docs.github.com/en/copilot/concepts/billing-and-usage/individuals/billing (checked 2026-11-06)
29. Included AI Credits reset at 00:00 UTC on the first day of each calendar month and do not carry over; when they run out an individual can upgrade, set a dollar budget for additional usage or wait, while Business and Enterprise users must ask an administrator for more budget. Source: https://docs.github.com/en/copilot/concepts/billing-and-usage/individuals/billing (checked 2026-11-06)
30. 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)
31. Only users with write access can trigger the cloud agent; it pushes only to a copilot/ branch or the PR branch under existing branch protections, works behind a firewall, has its code checked by CodeQL, dependency review and secret scanning, needs a write-access user to approve Actions workflows on its PRs, and signs commits that link to session logs and audit log events. Source: https://docs.github.com/en/copilot/concepts/agents/cloud-agent/risks-and-mitigations (checked 2026-11-06)
32. Organization owners set Copilot policies under Settings > Copilot, including MCP servers in Copilot, which models beyond the basic ones are available, and Copilot in GitHub.com on Business or Enterprise, and an enterprise owner can fix any policy as enabled or disabled everywhere or for selected organizations. Source: https://docs.github.com/en/copilot/how-tos/administer-copilot/manage-for-organization/manage-policies (checked 2026-11-06)
33. Copilot cloud agent sessions start from GitHub.com, GitHub Mobile, VS Code, JetBrains, Visual Studio and Eclipse, the GitHub CLI, REST API and MCP server, Raycast, Slack, Microsoft Teams, Linear, Jira and Azure Boards. Source: https://docs.github.com/en/copilot/how-tos/use-copilot-agents/cloud-agent/create-a-pr (checked 2026-11-06)
34. On Pro, Pro+, Max, Business and Enterprise, Claude and Codex can be assigned GitHub tasks as third-party agents (public preview). Source: https://docs.github.com/en/copilot/concepts/agents/about-third-party-agents (checked 2026-11-06)
35. Copilot cloud agent sessions run in a GitHub cloud sandbox, in a GitHub Actions environment capped at 59 minutes, or in a remote environment you connect. Source: https://docs.github.com/en/copilot/concepts/agents/cloud-agent/about-cloud-agent (checked 2026-11-06)
36. 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)
37. 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)
38. 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)
39. Clifford Ressel is Nori's CTO and co-founder. Source: https://ai.engineer/orgs/nori (checked 2026-11-06)
40. 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)
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. Source: https://noriagentic.com/newsletter/2026-09-18-miravoice-case-study.html (checked 2026-11-06)
42. Copilot cloud agent opens draft pull requests on its own branch and cannot approve or merge them. Source: https://docs.github.com/en/copilot/concepts/agents/cloud-agent/risks-and-mitigations (checked 2026-11-06)

---

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