Switching guides
Switching from Factory to Jiro (2026): Mapping Droids, AGENTS.md and Automations
How do I switch from Factory to Jiro?
Switching from Factory to Jiro takes one afternoon of setup and a two-week parallel run: start the free trial, install the GitHub App on pilot repos, connect Slack, sign in to Claude with claude setup-token or link ChatGPT, write the setup script, then rebuild each Factory automation as a cron or webhook trigger. Jiro is a background coding agent by Nori. Committed AGENTS.md and CLAUDE.md files carry over unchanged, while Droid Computers, Teams delegation and Factory Private have no direct equivalent. It is not Amazon's Kiro or Atlassian's Jira.
What maps to what: Factory concepts and their Jiro equivalents
| Factory | Jiro equivalent | Detail |
|---|---|---|
| Droid CLI and Factory App on your laptop | No equivalent; every session is cloud-side | Isolated cloud environment with your repos and tools [1] |
| Droid Computers (persistent, Factory-hosted) | Runtimes | Sized by runtimes; they sleep when idle [2] |
| Remote Control and OpenCompute (your hardware or cloud) | No equivalent; nearest is a dedicated deployment | Nori cloud, or a dedicated deployment in your AWS account [3] |
| Environments (dependency setup) | Org setup script | Org setup script prepares each environment [4] |
| AGENTS.md and CLAUDE.md in the repo | Read natively by the harness; org rules via skillset | One skillset, translated per agent [5] |
| Skills (SKILL.md under .factory/skills/) | Skillsets | Shared org context and portable skillsets [6] |
| Custom droids (.factory/droids/) | No equivalent | Fold the prompt into a skill |
| @Factory in Slack | Mention Jiro's bot; the thread is the session | Mention in Slack; works in the thread [7] |
| Assigning a Linear or Jira issue to the Agent | Integration, not a trigger | Linear, Jira, Notion, Google, HubSpot and more [8] |
| @Factory in Microsoft Teams | No equivalent | Slack, web, Discord, terminal, schedules, webhooks [9] |
| Scheduled starters (Ticket to PR, Code Health) | Cron triggers | Cron, one-off reminders, webhooks [10] |
| Webhook starters (Alert Responder) | Webhook triggers | Cron, one-off reminders, webhooks [10] |
| GitHub Actions starters and Droid Exec in CI | No equivalent | Keep them on Factory or drop them |
| Custom models (BYOK) in CLI and desktop | Your own credentials for every session | Your Claude/ChatGPT login or API key; Cursor key [11] |
| Model routing across vendors | Pick the harness | Claude Code, Codex, Cursor, OpenCode, pi-acp [12] |
| Service account Git credentials | GitHub App or PAT | GitHub App (all or selected repos) or a PAT [13] |
| MCP servers | MCP catalog | MCP server catalog in the dashboard [14] |
| Factory Private (customer VPC, preview) | Dedicated deployment in your own AWS account | Nori cloud, or a dedicated deployment in your AWS account [3] |
| Audit logs (Business and Enterprise) | Session and action logging | Every session and action logged [15] |
| Pull request from a delegation | PR, commit or comment | PRs, commits, comments for review [16] |
List prices on each side (checked 2026-11-06)
| Plan | Price | What it covers | |
|---|---|---|---|
| Factory | Pro | $20 a month [17] | Desktop, CLI, SDK, background agents; model usage included under rate limits |
| Factory | Plus / Max | $100 / $200 a month [17] | About 5x and 10x Pro's limits; Droid Computers [18] |
| Factory | Teams | $60 a month plus $40 per seat [17] | Up to 10 seats at Pro limits; no SSO, ZDR or audit logs [19] |
| Jiro | Trial | Free, 30 days, no card [20] | 5 runtimes [2] |
| Jiro | Developer | $99 a month [20] | 1 user, up to 3 runtimes; model usage on your plan or key, no markup [21] |
| Jiro | Team | $250 a month [20] | 5 shared runtimes; model usage on your plan or key |
| Your provider | Claude Pro / Max | $20 / $100 a month [22] [23] | The plan Jiro's Claude Code harness runs on |
Who should use this guide?
This guide is for teams of 5 to 20 engineers moving delegated coding work from Factory's Droids to Jiro, on GitHub, with Slack, and with a Claude or ChatGPT subscription already paid for. It assumes a self-serve Factory plan, Pro through Teams, rather than a Business or Enterprise contract. [17]
It is not for Factory Private customers. If your Droid sandboxes are provisioned inside the customer's VPC through OpenCompute, the nearest Jiro option is Nori's dedicated BYOC deployment, which runs inside an AWS account you own, and that is a procurement conversation rather than an afternoon's work. [24] [3] Budget one afternoon for setup and two weeks of running both tools. Keep Factory switched on the whole time.
What carries over from Factory without changes?
Your repository instruction files. Droid reads a root AGENTS.md and treats CLAUDE.md as a compatible filename, so most Factory users already have one or both committed. [25] Jiro's harnesses read them too: Claude Code picks up CLAUDE.md and the others pick up AGENTS.md, the same per-agent split Nori applies when it translates a skillset. [5] Leave those files where they are.
Skills need a copy. Factory stores them as SKILL.md directories under .factory/skills/ in the repo or ~/.factory/skills/ for one person. [26] The team-shared ones belong in your Jiro org skillset, which Nori treats as portable context across harnesses. [6] Personal ones stay personal.
Custom droids do not carry over. They are Markdown subagents with their own prompt, model and tool policy in .factory/droids/, and Jiro has no matching object. [27] Fold the useful prompts into a skill instead.
How do Factory automations map to Jiro triggers?
One to one on the trigger, not on the template. Factory's starters are pre-written: Ticket to PR polls Linear or Jira every 15 minutes, Error Triage runs hourly, Code Health runs weekday mornings, Slack Bug Fixer fires on a Slack message, and Alert Responder listens to Sentry, Datadog or PagerDuty webhooks. [28] Jiro gives you three primitives: cron triggers for recurring jobs, reminders that run once at a set time, and webhooks for when an outside system should kick things off. [10] You write the prompt.
Translate each starter. Ticket to PR becomes a cron trigger whose prompt reads the tracker through the Linear or Jira integration and opens a pull request for the top ready item. [8] Alert Responder becomes a webhook trigger pointed at your alerting tool. Slack Bug Fixer needs no automation at all, because mentioning Jiro's bot in a channel starts a session that continues in the thread. [7] Factory's GitHub Actions starters, such as Review Comment Fixer, have no Jiro counterpart; keep them running or retire them. [29]
What has no Jiro equivalent?
Four things, and you should know them before the pilot. Local execution: Droids run in the CLI and Factory App on your laptop, and via Remote Control on machines you own; Jiro sessions run only in Nori's isolated cloud environment. [30] [1] Microsoft Teams: @Factory in a Teams channel starts a delegation on a remote computer; Jiro has no Teams surface. [31] [9] Droid Exec: the headless droid exec command slots into CI pipelines, read-only unless given an --auto level, and Jiro has no CI step. [32] Ticket assignment: handing a Linear issue to the Agent assignee is a trigger in Factory and only an integration in Jiro. [33]
Droid Computers are a partial match. Factory hosts them, they keep packages and services between sessions and pause when idle. [34] Jiro runtimes also sleep when idle, and each session's environment is prepared by the setup script rather than by state left over from last time. [2] [4]
What should be ready before cutover?
- A written list of every Factory automation in use, its trigger and where its output lands. [28]
- A list of where delegations start today: Slack, Linear, Jira or Teams. [35] Each Teams or ticket-assignment path needs a new Slack habit.
- The location of every AGENTS.md, CLAUDE.md and .factory/skills directory across the pilot repos. [25]
- Two or three pilot repositories, one of them dull.
- Confirmation that each pilot user holds a Claude plan, a ChatGPT plan, an Anthropic or OpenAI key, or a Cursor key for the Cursor harness. [11]
- One named owner who writes the setup script and reviews every pilot pull request.
- Agreed pass criteria for the pilot, written down before day one. Time to first PR and review rounds are the usual pair.
Cutover: eight steps in order
- Start the trial at the signup link. No card, 30 days, five runtimes. [20] [2] Check that the web dashboard opens.
- Add the GitHub App and restrict it to pilot repositories only; a saved personal access token works where apps are not allowed. [13] Check by asking Jiro, in the web chat, to summarise one repo's README.
- Add the Slack app, create a pilot channel and invite the bot. [7] Check that a greeting gets a threaded reply.
- Connect model credentials. For Claude Code, run
claude setup-tokenon your own laptop and paste the resulting token; for Codex, use Codex OAuth or an OpenAI key; for Cursor Agent, a Cursor key. [36] [11] Check with a one-line coding question in the pilot channel. - Write the org setup script: language runtimes, package install, anything the test suite needs. [4] Check by asking Jiro to run the tests in a pilot repo and report the result.
- Create the org skillset from the shared skills and conventions you collected. [6]
- Connect Linear or Jira and any MCP servers from the catalog. [8] [14] Check that Jiro can read a ticket you link.
- Send one small task with an obvious right answer and wait for the pull request. [16]
Leave every Factory automation switched on.
How do you sign in with a Claude or ChatGPT plan rather than an API key?
Claude first. The claude setup-token command, run in Claude Code on a laptop with a browser, mints a 12-month token bound to whichever paid plan you hold (Pro, Max, Ultra, Team, Enterprise); Anthropic built it for machines with no browser. [36] Copy it into the Claude credential field in Jiro. Jiro's Claude Code harness accepts the setup token, a Claude OAuth login or an Anthropic API key, so either route works. [11]
ChatGPT next. Jiro's Codex harness takes Codex OAuth or an OpenAI API key. [11] Whichever you choose, Nori adds no markup to what your provider charges. [21] This is the step Factory cannot match for hosted work, since its own-key settings are read only by the CLI and desktop app. [37]
Which tasks belong in the first week?
Escalate risk by the day.
- Day 1: documentation. Ask for a diff between the README and the code as it stands.
- Day 2: tests. Point it at the module with the thinnest coverage and request missing cases only.
- Day 3: a small bug from the backlog, posted in the pilot channel with the ticket link.
- Day 4: two more tickets, in parallel, to see how the shared runtimes behave. [2]
- Day 5: the first automation. Recreate one Factory scheduled starter as a cron trigger, for example a morning check of a flaky test area. [10]
Record, per task: minutes to the first pull request, review rounds, and whether a reviewer rewrote anything. Run the same measurements on Factory for comparable tickets during the same week. Jiro will sometimes push back on a ticket it thinks is wrong; log those too, since a refusal that prevents a bad merge is a result. Every session is logged, so the transcript is there if you need it. [15]
How does the bill change?
Factory bundles model usage; Jiro does not. Factory's self-serve ladder is Pro at $20, Plus at $100 and Max at $200 a month, then Teams at $60 monthly for the org and $40 for each of up to 10 seats, every seat carrying Pro's rate limits. [17] [18] Jiro bills $99 a month on Developer (one user, up to three runtimes) and $250 a month on Team (five runtimes pooled), after a 30-day free trial. [20]
On top of Jiro you keep paying your provider directly. A Claude Pro seat is $20 a month and Max is $100 for five times Pro's usage. [22] [23] Anthropic's own figure for Claude Code in enterprises is about $13 per developer per active day. [38] Do the sum for your headcount and usage rather than trusting a vendor's example; the inputs above are the published ones.
When staying on Factory is the better choice
Stay if Droids must run on hardware you control. Factory runs them on your laptop, on registered machines through Remote Control and in your own cloud or data centre through OpenCompute, and Jiro offers none of those. [30] [39] Stay if Microsoft Teams is where your team talks, because @Factory delegation there has no Jiro counterpart. [31] Stay if your process is tracker-first and engineers assign issues to the Agent in Linear rather than posting in chat. [33]
Stay for the model layer if you want one tool to route Anthropic, OpenAI and other models and still accept your own keys or a local model in the CLI. [37] Stay if the automation starters already cover your maintenance rota and nobody wants to write prompts. [28] And stay if a Factory Private or Enterprise conversation is already underway, since dedicated compute, SSO, zero data retention and audit logs sit in those tiers. [24] [19]
How do you roll back?
Nothing on the Factory side changed, so rollback is subtraction. Merge or close any open Jiro pull requests. Remove the Slack app from the pilot channel. Uninstall the GitHub App or deselect the pilot repositories. [13] Delete the Claude, OpenAI or Cursor credential from Jiro, and revoke the setup token on the Anthropic side if you prefer. Let the trial expire; no card was taken. [20] Keep the pilot log and transcripts for the write-up. [15] If you are still weighing options, the Factory alternatives page compares eight products with prices.
Jiro at a glance
| Fact | Jiro |
|---|---|
| What it is | A background coding agent: it works in the cloud and returns pull requests for review [16] |
| Made by | Nori (Tilework Inc.), founded by Amol Kapoor, ex-Google Research [40] |
| Agents it runs | Claude Code, Codex, Cursor, OpenCode, pi-acp [12] |
| Whose model bill | Your Claude/ChatGPT login or API key; Cursor key [11]; Your keys, zero token markup [21] |
| Price | Free 30-day trial; Developer $99/mo; Team $250/mo [20] |
| Runtimes | Developer: up to 3; Team: 5 shared; trial: 5 for 30 days [20] [2] |
| Where work starts | Slack, web, Discord, terminal, schedules, webhooks [9] |
| 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 [13] |
| 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. [44] [45]
FAQ
How long does moving from Factory to Jiro take?
One afternoon to set up, then two weeks running both tools before you retire any Factory automation. The trial covers 30 days with no card. [20]
Do Factory automations import into Jiro?
No. Rebuild each scheduled starter as a cron trigger and each webhook starter as a webhook trigger. [10] Factory's GitHub Actions starters have no Jiro counterpart. [29]
Will Jiro read my AGENTS.md and CLAUDE.md?
Yes. Claude Code reads CLAUDE.md and the other harnesses read AGENTS.md, the same files Droid already loads. [5] [25]
Can I keep using my Claude subscription instead of an API key?
Yes. claude setup-token issues a 12-month token bound to your subscription; paste it into Jiro, whose Claude Code harness also takes a Claude OAuth login or an Anthropic key. [36] [11]
Does Jiro have a Factory Private equivalent?
Partly. Nori hosts Jiro with a single-tenant broker per organisation, and its BYOC option places the session machines in an AWS account the customer controls. [41] [3] Factory Private, in private preview, places some or all of Factory's infrastructure in the customer's VPC. [24]
Can Jiro run on my own machine like the Droid CLI?
No. Every Jiro session runs in an isolated cloud environment, whereas a Droid can also run on your laptop through the CLI or Factory App. [1] [30]
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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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'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)
- 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)
- 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 logs every session and every action, and makes them searchable. https://noriagentic.com/for-security-leaders.html (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)
- Factory's plans are Pro at $20 a month, Plus at $100, Max at $200, and Teams at $60 a month plus $40 per seat for up to 10 seats; Business and Enterprise are custom. https://factory.com/pricing (checked 2026-11-06)
- Factory's Plus plan carries about 5 times Pro's rolling rate limits and Max about 10 times, Plus and Max include Droid Computers, and Teams gives each seat Pro's limits for up to 10 seats. https://factory.com/pricing (checked 2026-11-06)
- Factory's self-serve Teams plan bills month to month for up to 10 seats and leaves SSO, SAML/SCIM provisioning, admin controls, zero data retention and audit logs to the custom-priced Business and Enterprise plans. https://docs.factory.com/pricing/organizations.md (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'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)
- 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)
- 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)
- Factory Private, announced 2026-09-18 and still in private preview, places some or all of Factory's infrastructure in the customer's VPC. https://factory.com/news/factory-private (checked 2026-11-06)
- Droid loads a root-level AGENTS.md before writing code, searching the repository up to its git root plus .factory/, .agents/, .agent/ and ~/.factory/, and reads CLAUDE.md as a compatible filename. https://docs.factory.com/harness/agents-md.md (checked 2026-11-06)
- Factory skills are directories with a SKILL.md entry point, stored in <repo>/.factory/skills/ for the team or ~/.factory/skills/ for one person, and the /skills manager has an Import from Claude tab. https://docs.factory.com/harness/skills.md (checked 2026-11-06)
- A custom droid is a reusable subagent defined in a Markdown file with its own system prompt, model and tool policy, stored in <repo>/.factory/droids/ or ~/.factory/droids/. https://docs.factory.com/harness/subagents.md (checked 2026-11-06)
- Factory's automation starters include Ticket to PR every 15 minutes, Error Triage hourly, Code Health on weekday mornings, Slack Bug Fixer on Slack messages and Alert Responder on Sentry, Datadog or PagerDuty webhooks. https://docs.factory.com/software-factory/automations.md (checked 2026-11-06)
- Factory's scheduled and Slack automations can run on your own machine through the desktop app or on a Droid Computer, webhook automations cannot run on your own machine, and custom GitHub automations run in GitHub Actions. https://docs.factory.com/software-factory/automations.md (checked 2026-11-06)
- Droids run locally in the Droid CLI and Factory App, on Factory-hosted Droid Computers, on your own computer via Remote Control, or in your own cloud via OpenCompute. https://docs.factory.com/llms.txt (checked 2026-11-06)
- A delegation mentioned to @Factory in Microsoft Teams runs on a remote computer under a shared service account's identity, Git credentials and connectors, needs a paid Factory organization, and only the person who started it can send follow-ups or stop it. https://docs.factory.com/delegations/microsoft-teams.md (checked 2026-11-06)
- Droid Exec is Factory's headless mode for CI/CD pipelines and scripts; a run is read-only unless started with --auto low, medium or high. https://docs.factory.com/droid-exec/overview.md (checked 2026-11-06)
- In Linear you delegate by choosing the Agent entry in the assignee picker or mentioning @Factory in a comment; Droid runs on a remote computer with a service account's Git credentials and posts progress in the issue. https://docs.factory.com/delegations/linear.md (checked 2026-11-06)
- Droid Computers are persistent cloud environments that Factory provisions and maintains; they keep installed packages, files and running services between sessions and auto-pause when idle. https://docs.factory.com/droid-computers/overview.md (checked 2026-11-06)
- Droids work in the Factory App, Droid CLI, headless Droid Exec and IDEs, and take delegations from Slack, Linear, Jira and Microsoft Teams. https://docs.factory.com/llms.txt (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)
- Factory routes across Anthropic, OpenAI and other models and accepts your own keys or local models in the CLI and desktop app, but not in the hosted web or mobile apps. https://docs.factory.com/model-independence/byok.md (checked 2026-11-06)
- 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)
- OpenCompute, in private preview, is a self-hosted orchestrator that provisions Droid sandboxes in your own cloud accounts, data centers or Kubernetes clusters, and your team deploys, operates and maintains it. https://docs.factory.com/opencompute/overview.md (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)
- 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)
- 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)