---
title: "Switching from Kiro to Jiro (2026): Map Specs, Steering and Hooks"
canonical: https://jiro.bot/switch/kiro-to-jiro
last_updated: 2026-11-06
---

# Switching from Kiro to Jiro (2026): Map Specs, Steering and Hooks

Updated 2026-11-06

> **How do I switch from Kiro to Jiro?**
>
> Switching from Kiro to Jiro takes an afternoon: start a Nori trial, give its GitHub App the repositories you want covered, connect Slack, generate a Claude token locally with `claude setup-token` and hand it to Nori (or use a ChatGPT or Cursor credential), write a setup script, then carry your .kiro/steering rules into a skillset and rebuild scheduled hooks as cron or webhook triggers. Jiro is a background coding agent by Nori. Kiro's spec editor has no Jiro equivalent, so committed specs stay in the repository as plain files that Jiro reads when a request points at them. It is not Amazon's Kiro or Atlassian's Jira.

## What maps to what

| Kiro | Jiro equivalent | How it moves |
|---|---|---|
| .kiro/steering/ (product.md, tech.md, structure.md) | One skillset, translated per agent [1] | Copy the rules you still want into one skillset; prune stale advice |
| .kiro/specs/<name>/ (requirements, design, tasks) | No equivalent workflow; the files stay in the repo | Name the spec file in the request and Jiro reads it |
| .kiro/hooks/ on file save, tool use, agent stop | Cron, one-off reminders, webhooks [2] | Scheduled and event hooks become cron or webhook triggers; per-edit hooks have no equivalent |
| Kiro Web Cloud Configuration | Org setup script prepares each environment [3] | Toolchain and dependency installs move into the setup script |
| Kiro credits | Your Claude/ChatGPT login or API key; Cursor key [4] | `claude setup-token`, Codex sign-in or an API key |
| kiro label or /kiro comment on an issue | Mention in Slack; works in the thread [5] | Mention the bot in Slack; use a webhook for machine events |
| Cloud sessions, 10 at a time | Sized by runtimes; they sleep when idle [6] | Developer: up to 3 runtimes; Team: 5 shared |
| Kiro IDE, JetBrains, Zed | No equivalent | Keep whatever editor you like; Jiro has none |
| Kiro for iOS (early access) | Set up from a phone [7] | Slack and the web dashboard work from a phone |
| MCP servers in .kiro settings | MCP server catalog in the dashboard [8] | Re-add the servers you use from the dashboard catalog |
| GitLab repositories | GitHub App (all or selected repos) or a PAT [9] | No path; Jiro connects to GitHub |

Verified against kiro.dev and docs.noriagentic.com on 2026-11-06.

## Should we switch from Kiro at all?

Switch only if your team already pays Anthropic or OpenAI and wants work done while nobody is at a keyboard. That is the case Jiro is built for, and it is narrower than Kiro's.

Kiro is a complete agentic environment whose core is the spec: requirements, design and tasks files that the agent executes in waves. [10] If that discipline is why you bought it, moving to Jiro means losing it. Nothing on this page pretends otherwise.

The arithmetic favours switching when a group of five to twenty engineers holds Claude or ChatGPT seats with headroom to spare and is paying $20 to $200 a month per head for Kiro credits on top. [11] Jiro's flat $99 or $250 a month puts the agent on those existing seats instead. [12] If you are one developer who loves the IDE, stay.

## What happens to our .kiro/specs?

They stay exactly where they are. A Kiro spec is three markdown files in `.kiro/specs/<name>/`, and markdown committed to a repository is just a file. [10]

Jiro's environment has your repositories checked out, so it can open `design.md` the way a new teammate would and act on it. [13] A request such as "implement task 3 in .kiro/specs/checkout/tasks.md" works today.

What does not come across is the machinery around the files. There is no spec mode, no requirements-then-design wizard, no task runner that marks items complete in an editor panel. If you want a plan before code, ask for one in the thread; Jiro will draft it, and it will argue if the plan looks wrong, but the output is a reply and then a pull request, not a tracked artifact. [14]

## How do steering files become a skillset?

By copying, not by conversion. Kiro keeps persistent guidance in `.kiro/steering/`, usually `product.md`, `tech.md` and `structure.md`, with front matter that decides whether a file loads always, on a file-pattern match, manually or automatically. [15]

Nori's analogue is the skillset. You write guidance once and Nori renders it into each agent's native file, so Claude Code picks up a CLAUDE.md while Codex gets an AGENTS.md. [1] Skillsets are portable across the organization, so one copy serves every session and every harness. [16]

Paste the rules that still earn their keep: test commands, module boundaries, "ask before touching payments". Drop anything stale; steering folders collect it. The `fileMatch` mode has no direct counterpart, so fold path-specific rules into one document with clear headings. Then run `npx nori-skillsets install public/jiro`; it brings Nori's own engineering baseline on reviews, tests and documentation into every session.

## What replaces Kiro hooks?

Two different things, and one gap.

Kiro hooks are JSON files in `.kiro/hooks/` that run a shell command or inject a prompt when something happens inside a session: a prompt is submitted, a tool is about to run, a file is saved, a spec task finishes, the agent stops. [17] [18]

Hooks that exist to run on a schedule or on an outside event map cleanly. Nori cron triggers run recurring jobs, reminders fire once at a chosen time, and webhooks start a session when another system calls. [2] A nightly "lint the whole repo and open a PR" hook becomes a cron trigger with that instruction.

Hooks that prepare the environment move into the setup script, which installs dependencies and tooling before each session starts. [3]

The gap is per-edit hooks. Jiro offers no documented way to run a command every time the agent saves a file. Put linters and formatters in the repository's own pre-commit configuration instead, so they run in the environment regardless of who is typing.

## How do I set up Jiro, step by step?

Budget an afternoon, most of it waiting on the first task.

1. **Open the trial.** No card; it lasts a month and gives you five runtimes. [12]
2. **Grant repository access** by installing Nori's GitHub App on every repository or only the pilot set; a personal access token works if your org forbids apps. [9]
3. **Connect Slack.** Mentioning the bot in a channel opens a thread, and that thread is the session. [5]
4. **Sign in with your model account.** For Claude, the step is `claude setup-token`, typed into the Claude command line on your own machine. Twelve months of validity, inheriting your paid Claude plan at whatever tier you hold, is what that token gives you; Anthropic built the command for hosts that cannot open a browser window, which describes Jiro's environment exactly. [19] Paste it into Nori. ChatGPT users sign in through Codex OAuth or supply an OpenAI key; Cursor Agent needs a Cursor key. [4]
5. **Write the setup script** that installs your toolchain and dependencies into each environment. [3]
6. **Import steering** into a skillset as described above.
7. **Send one small task** and read the pull request with the same care you would give a new hire.

## What should the first week look like?

Small, checkable, boring. You are calibrating trust, not running a benchmark.

Day one, a documentation fix: stale README sections, a missing changelog entry. Day two, tests for a helper that has none. Day three, a real backlog ticket you would estimate at an hour. Day four, a read-only audit: "list what is sloppy in the payments module" and judge the answer before asking for changes. Day five, set a cron trigger for a recurring chore and let it run unattended over the weekend. [2]

Each job ends in a PR, a commit or a comment you can inspect, so the measure is simple: how many did you merge, how many did you send back, and how long did review take? [14] Nori records each session and every action, and the record is searchable, so when something looks odd you can read what happened rather than guess. [20]

## What has no Jiro equivalent?

Be clear-eyed about this list before you commit.

- **The spec workflow.** Requirements, design and task files executed in waves from an editor. [10]
- **An editor.** Kiro ships an IDE and plugs into JetBrains and Zed over `kiro-cli acp`; Jiro has no editor and never will be one. [21]
- **Per-edit hooks.** Commands on file save or before tool use. [17]
- **A native phone app.** Kiro for iOS is in early access for paid plans; Jiro's phone story is Slack and the web dashboard. [22]
- **GitLab.** Kiro Web connects GitLab repositories; Jiro connects to GitHub through an App or token. [23] [9]
- **Issue-label triggers.** Labelling an issue kiro, or commenting /kiro, starts Kiro; Jiro starts from messages, schedules and webhooks. [24]
- **One vendor for models.** Kiro meters Claude, GPT and open models through one credit pool. [25]

## When Kiro is the better choice

Stay on Kiro if the spec flow is doing real work for you. Requirements, design and tasks files, executed in dependency waves with live status, is a genuine engineering discipline and Jiro does not replicate it. [10]

Stay if hooks shape your process. Triggers on prompt submit, tool use, file save and spec-task completion, each able to run a command or steer the agent, give you control at a granularity Jiro does not expose. [18]

Stay if you are an AWS organization. Kiro signs in with IAM Identity Center or Builder ID, existing Amazon Q Developer Pro logins keep working, Enterprise billing flows through the AWS account, and credits pool at $20 per seat. [26] [27]

Stay if you value the breadth: an IDE, a V3 CLI, a web app, JetBrains and Zed support, the open-source Kiro Crew workspace, and an iOS app in early access. [28] [29] [30]

And stay if you are one person. Pro at $20 a month with cloud sessions included is cheaper than Developer. [11] [31]

## Will Jiro cost more or less than Kiro?

It depends on what you already pay, so do the sum for your own team.

Kiro's four paid tiers cost $20, $40, $100 and $200 per user each month, carrying 1,000, 2,000, 5,000 and 10,000 credits respectively, and extra credits are $0.04 apiece; Enterprise pooling is $20 per seat with 500 credits each. [11] [27] Ten engineers on Pro+ is a real monthly line item before overage.

Jiro is $99 a month for one user, or $250 monthly for a team that shares five runtimes. [12] The token cost lands on the Anthropic or OpenAI invoice you already receive; Claude Max, for reference, is $100 a month, and Nori adds no markup to usage. [32] [33]

For one developer, Kiro is cheaper. For a team already holding Claude or ChatGPT seats, Jiro's flat fee often comes out ahead because nobody buys model access twice. If you hold neither subscription, the comparison is closer and Kiro's bundled credits may win.

## Can we run Kiro and Jiro side by side?

Yes, and a two- or three-week overlap is the sensible way to decide.

The two do not touch. Kiro's cloud sessions run in AWS-managed sandboxes attached to your Kiro account. [31] Jiro's sessions each claim a machine in your organization's own fleet behind a single-tenant broker. [34] [35] Separate credentials, separate repository permissions, separate bills.

Route by shape of work. Anything that needs a spec stays in Kiro. Small tickets, docs, test gaps and scheduled chores go to Jiro. At the end, count what merged, what you returned, and the review time per tool. If Jiro's numbers are not there, you have spent a free trial and nothing else.

Still weighing options? The [Kiro alternatives](https://jiro.bot/alternatives/kiro) page covers five other tools, and [Jiro vs Kiro](https://jiro.bot/compare/kiro) sets the two side by side.

## Jiro at a glance

| Fact | Jiro |
|---|---|
| What it is | A background coding agent: it works in the cloud and returns pull requests for review [14] |
| 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 [4]; Your keys, zero token markup [33] |
| Price | Free 30-day trial; Developer $99/mo; Team $250/mo [12] |
| Runtimes | Developer: up to 3; Team: 5 shared; trial: 5 for 30 days [12] [6] |
| Where work starts | Slack, web, Discord, terminal, schedules, webhooks [38] |
| Where it runs | Isolated cloud environment with your repos and tools [13]; Single-tenant per organization [35] |
| Repos | GitHub App (all or selected repos) or a PAT [9] |
| 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] [39] Clifford Ressel is Nori's co-founder and CTO. [40] Nori's customers include Corvus and Miravoice. [41] [42]

## FAQ

### Is Jiro a rebrand of Kiro?

No. Kiro is AWS's product and Jiro is Nori's; nothing connects them. [43]

### Can I spend Kiro credits in Jiro?

No. Kiro credits meter models inside Kiro at per-model multipliers. [25] Jiro runs on your own Claude, ChatGPT or Cursor credential. [4]

### Why does the guide include claude setup-token?

Because Jiro's environment has no browser for the usual Claude login; the command produces a token good for a year, tied to the Claude plan you pay for, which you paste into Nori. [19]

### Do my Kiro steering files need rewriting?

Copy, do not rewrite. Put the rules you keep into a Nori skillset and it is rendered as CLAUDE.md or AGENTS.md for each agent. [1]

### Can Jiro start from a GitHub issue label like Kiro?

Not from a label. Jiro's entry points are webhooks, schedules, a terminal, Discord, the web dashboard and Slack. [38]

### How long does the switch take?

Setup is an afternoon; trusting the pull requests takes about a week of small tasks. The trial lasts 30 days with no card. [12]

## 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 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)
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. 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)
5. 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)
6. 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)
7. The Miravoice team set up an agent entirely in the cloud from their phones. Source: https://noriagentic.com/#miravoice-story (checked 2026-11-06)
8. 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)
9. 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)
10. A Kiro spec lives in .kiro/specs/<name>/ as requirements.md (or bugfix.md for bug fixes), design.md and tasks.md, and tasks can run one at a time or all at once in dependency-ordered waves from the IDE, CLI or Web. Source: https://kiro.dev/docs/specs/ (checked 2026-11-06)
11. Kiro's plans are Free (50 credits a month), Pro at $20 with 1,000 credits, Pro+ at $40 with 2,000, Pro Max at $100 with 5,000 and Power at $200 a month per user with 10,000 credits, with add-on credits at $0.04 each on paid tiers; Kiro Web needs a paid plan. Source: https://kiro.dev/pricing/ (checked 2026-11-06)
12. 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)
13. 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)
14. 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)
15. Kiro steering files are markdown in .kiro/steering/ (or ~/.kiro/steering/ for every workspace), with foundation files product.md, tech.md and structure.md and front-matter inclusion modes always, fileMatch, manual and auto. Source: https://kiro.dev/docs/steering/ (checked 2026-11-06)
16. 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)
17. Kiro agent hooks are JSON files in .kiro/hooks/ (or ~/.kiro/hooks/) that run a shell command with session context on stdin, under a 60-second default timeout, or inject a prompt into the conversation, on triggers such as PostFileSave, PreToolUse, PostToolUse and Stop. Source: https://kiro.dev/docs/hooks/ (checked 2026-11-06)
18. Kiro's hook triggers include Prompt Submit, Agent Stop, Session Start, Session End, Pre Tool Use, Post Tool Use, File Create, File Save, File Delete, and Pre and Post Task Execution around spec tasks. Source: https://kiro.dev/docs/hooks/types/ (checked 2026-11-06)
19. 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)
20. Nori logs every session and every action, and makes them searchable. Source: https://noriagentic.com/for-security-leaders.html (checked 2026-11-06)
21. Kiro CLI implements the Agent Client Protocol, so JetBrains IDEs, Zed and other compatible editors can launch `kiro-cli acp` and talk to it over JSON-RPC on stdio, provided the user is signed in to a Kiro account. Source: https://kiro.dev/docs/cli/acp/ (checked 2026-11-06)
22. Kiro for iOS is in early access through Apple TestFlight and lets you start and steer cloud sessions from your phone, sharing sessions and settings with Kiro Web. Source: https://kiro.dev/docs/mobile/ (checked 2026-11-06)
23. Kiro Web at app.kiro.dev offers a default interactive mode, a Spec mode and an autonomous mode, connects GitHub or GitLab repositories, requires a Pro, Pro+, Pro Max or Power subscription, runs only in us-east-1, and never merges to the default branch without your review. Source: https://kiro.dev/docs/web/ (checked 2026-11-06)
24. Kiro Web starts work when a GitHub issue gets the kiro label or a /kiro comment, pushes a feature branch, opens a pull request with a detailed description, cannot push to protected branches, and leaves review and merging to your normal GitHub workflow. Source: https://kiro.dev/docs/web/github.md (checked 2026-11-06)
25. Kiro offers Claude, GPT-5.6 and open-weight models such as Kimi K3, GLM-5, DeepSeek 3.2 and Qwen3 Coder Next through its own credits, charged at multipliers relative to Auto at 1.0x, for example Claude Opus 5.5 at 2.0x, Claude Sonnet 5.5 at 1.3x and GPT-5.6 Sol at 4.4x. Source: https://kiro.dev/docs/models.md (checked 2026-11-06)
26. Kiro needs no AWS account, signs you in with GitHub, Google, AWS Builder ID or AWS IAM Identity Center, lets Amazon Q Developer Pro subscribers use their existing credentials, and bills Enterprise plans through AWS. Source: https://kiro.dev/faq/ (checked 2026-11-06)
27. Kiro credit pooling, announced 2026-11-04 for Enterprise customers, costs $20 per seat a month with a two-seat minimum and 500 pooled credits per seat each cycle, with add-on credits at $0.04 that roll over for up to 12 months, billed through your AWS account. Source: https://kiro.dev/blog/credit-pooling/ (checked 2026-11-06)
28. Kiro CLI 3.0.0 became the default on 2026-11-03, retiring the Classic interface and desktop app; `/autonomous on` runs tasks without per-command approval with sandboxing on, and cloud sessions can be resumed from `/sessions`. Source: https://kiro.dev/changelog/ (checked 2026-11-06)
29. Kiro Crew is a free, open-source development workspace that runs on your machine and keeps working across sessions. Source: https://kiro.dev/ (checked 2026-11-06)
30. Kiro announced Kiro for iOS on 2026-06-17 as a native app for starting, monitoring and steering sessions with chat, spec and autonomous modes, available by early-access request to Pro, Pro+, Pro Max and Power customers on iOS 26 or later. Source: https://kiro.dev/blog/introducing-kiro-for-ios/ (checked 2026-11-06)
31. Kiro cloud sessions run in a managed, isolated cloud sandbox with the same agent harness as the IDE and CLI, up to 10 at a time, with no separate charge for cloud compute; `kiro-cli --cloud` starts one from a terminal and the IDE lists them in Agent Focus Mode. Source: https://kiro.dev/docs/cloud-sessions.md (checked 2026-11-06)
32. 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)
33. 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)
34. 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)
35. 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)
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. 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)
39. 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)
40. Clifford Ressel is Nori's CTO and co-founder. Source: https://ai.engineer/orgs/nori (checked 2026-11-06)
41. 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)
42. 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)
43. Kiro's own site says it is built and operated by AWS, that its agent is compatible with the Agent Client Protocol so you can bring it to other tools, and that Kiro Web sessions keep going when you close your laptop. Source: https://kiro.dev/ (checked 2026-11-06)

---

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