---
title: "Switching from Jules to Jiro (2026): Migration Plan Before the Read-Only Date"
canonical: https://jiro.bot/switch/jules-to-jiro
last_updated: 2026-11-06
---

# Switching from Jules to Jiro (2026): Migration Plan Before the Read-Only Date

Updated 2026-11-06

> **How do I switch from Jules to Jiro before it shuts down?**
>
> Export first, then rebuild: pull your sessions, scheduled tasks, memories, setup scripts and repo list out of Jules with the Jules Tools CLI before 2026-11-11, when Jules turns read-only ahead of its 2026-12-31 wind-down [1] [2], then set Jiro up with the GitHub App, Slack, a Claude subscription token (`claude setup-token`) or the Codex login, and an org setup script. Jiro is a background coding agent by Nori. Scheduled Tasks become cron triggers, the jules label becomes a Slack mention with the issue link or a webhook, and Gemini is the one thing with no equivalent. It is not Amazon's Kiro or Atlassian's Jira.

## Export order before 2026-11-11

| Order | Export from Jules | Why first | Where it lands in Jiro |
|---|---|---|---|
| 1 | Unfinished sessions: finish and Publish branch or Publish PR [3] | Only unpublished work can be lost; code, branches and PRs stay in GitHub [2] | Nothing to import; the branch is already in GitHub [2] |
| 2 | Scheduled Tasks (prompt, cadence, repo) [2] | They stop when Jules goes read-only after 2026-11-11 [1] | Cron triggers [4] |
| 3 | Setup scripts and environment variables [2] | Needed before the first Jiro task can build | Org setup script [5] |
| 4 | Memories and repo instruction files [2] | House rules you will otherwise rediscover | Org skillset plus the repo's CLAUDE.md or AGENTS.md [6] |
| 5 | Connected repository list [2] | Your pilot scope for the GitHub App install | GitHub App repo selection [7] |
| 6 | Session history (prompts, plans, logs, patches) [2] | Reference only; useful for writing the first Jiro requests | Keep in a private folder; Jiro imports nothing from it |

The export set comes from Google's turndown notice of 2026-10-29 [2]. Read-only begins after 2026-11-11 [1].

## What maps to what

| Jules concept | Jiro equivalent | Notes |
|---|---|---|
| Gemini models | No equivalent | Claude Code, Codex, Cursor, OpenCode, pi-acp [8] |
| Web app at jules.google.com | Web dashboard | Slack, web, Discord, terminal, schedules, webhooks [9] |
| GitHub issue labelled jules | Slack mention with the issue link, or a webhook | Mention in Slack; works in the thread [10]; Cron, one-off reminders, webhooks [4] |
| Jules Tools CLI | Handroll terminal | Slack, web, Discord, terminal, schedules, webhooks [9] |
| Jules API | Webhooks | Cron, one-off reminders, webhooks [4] |
| Scheduled Tasks | Cron triggers | Cron, one-off reminders, webhooks [4]; recreate each by hand |
| Short-lived machine per task | Isolated cloud environment per session | Isolated cloud environment with your repos and tools [11]; One machine per active session [12] |
| Setup script | Org setup script | Org setup script prepares each environment [5] |
| Memories | Org skillset | One skillset, translated per agent [6] |
| Publish branch or Publish PR | PR, commit or comment returned for review | PRs, commits, comments for review [13] |
| CI fixer (commit as you) | Reply in the Slack thread to request the fix | Mention in Slack; works in the thread [10] |
| Daily task caps | Runtimes | Sized by runtimes; they sleep when idle [14] |
| Personal Google account billing | Developer or Team plan | Free 30-day trial; Developer $99/mo; Team $250/mo [15] |
| Google AI Pro / Ultra subscription | Your Claude or ChatGPT plan, or an API key | Your Claude/ChatGPT login or API key; Cursor key [16] |

## Why is there a deadline?

Because Google set one. The Jules changelog entry of 2026-10-29 gives users until 2026-11-11 to finish sessions, switches Jules to read-only after that, and winds the product down on 2026-12-31 [1]. Read-only means you can open old tasks but not start, resume or schedule anything.

That turns a leisurely evaluation into a dated project. The good news is that the blast radius is small: your source code, branches and pull requests were always in GitHub, and Google's own notice confirms they are not part of the export [2]. What you stand to lose is workflow state, meaning scheduled jobs, the setup script that made Jules's machine useful, memories, and the prompts that worked. This guide moves those into Jiro in a specific order, with the irreversible items first.

## What should you export from Jules, and in what order?

The turndown entry recommends Jules Tools together with an agent prompt; between them they export account settings, environment variables, scheduled tasks, connected repositories, memories, setup scripts and every session with its prompt, plan, activity log and patches [2]. Run it once, early, into a private folder. Then work the table above from the top.

Start with unfinished sessions, since a Jules task that never reached Publish branch or Publish PR [3] is the only thing that cannot be reconstructed from GitHub. Next come Scheduled Tasks [17]: write down each prompt, cadence and target repo, because they will stop without warning when read-only begins [1]. Then the setup script and environment variables, which you will paste into Jiro before its first task can build. Memories and instruction files follow, then the repo list, which becomes your pilot scope.

Session history is last on purpose. It is reference material, not something Jiro imports, but the prompts that worked in Jules are a good seed for your first Jiro requests. Keep the export private: it may include credentials and environment values.

## Quickstart: setting up Jiro

You need GitHub org admin rights, Slack app permission, and a Claude or ChatGPT plan or API key.

1. **Start the free trial.** No card for 30 days, and five runtimes during the trial [15] [14].
2. **Install Nori's GitHub App** on all repos or only those from your Jules export; a PAT also works [7].
3. **Connect Slack.** Requests arrive as a channel mention and continue in the thread [10].
4. **Mint a Claude token.** From your own terminal, run `claude setup-token`. It lasts a year, is bound to your paid Claude plan (Team, Enterprise, Pro, Max or Ultra), and suits headless machines [18]. Give that token to Jiro.
5. **Or connect ChatGPT or Cursor.** Codex takes an OpenAI key or the Codex sign-in; Cursor Agent wants its own Cursor key; OpenCode and pi-acp want three values, an API base URL, a key and a model name [16].
6. **Write the org setup script** from your exported Jules script [5]. Every session's isolated cloud environment runs it [11].
7. **Send a small first task** from Slack, then review the PR that comes back [13].
8. **Optional:** Jiro's conventions ship as a skillset: `npx nori-skillsets install public/jiro`.

## How do Jules Scheduled Tasks move to Jiro?

By hand, one at a time, and before 2026-11-11 [1]. Jules ran recurring work as Scheduled Tasks [17]; Jiro's equivalents are cron triggers when something should recur, a one-time reminder for a single later run, and webhooks when an outside event should start it [4].

For each exported task, carry over three things: the prompt, the cadence and the repository. Rewrite the prompt the way you would brief a colleague in Slack, naming the repo and the acceptance criterion, because Jiro will run it through Claude Code or Codex rather than Gemini [8] and the phrasing that suited Gemini may need adjusting. A scheduled run claims a runtime while it works and releases it when idle [14], so stagger start times if you have more schedules than runtimes on your plan.

Anything that called the Jules API from your own automation should post a webhook to Jiro instead.

## What replaces the jules GitHub label?

Nothing identical. Jules started work when you labelled an issue jules, or from its web app, CLI or API [19]. Jiro does not watch issue labels. Work reaches it from Slack or Discord, from the web dashboard, from the Handroll terminal, or via a schedule or webhook [9].

The practical substitute is a Slack mention with the issue link pasted in. Jiro replies in a thread, and each later reply in the thread keeps the same session going [10], which gives you something Jules never had: a running conversation about the task where reviewers can redirect it mid-flight. For teams that want the label behaviour back, wire a webhook that fires on a GitHub label event and posts the issue to Jiro [4].

Expect a slightly different rhythm. Jules tasks were fire-and-forget; Jiro tasks are fire-and-discuss.

## Where do Jules memories and setup scripts go?

Two different homes. The setup script goes into Jiro's org setup script, the thing that installs dependencies and readies each session's environment [5], so paste your exported Jules script there and test it with a trivial task before anything else. Missing steps show up as odd early failures, which is the first place to look.

Memories map onto skillsets. Nori keeps org-wide context as portable skillsets alongside credentials, integrations and transcripts [20], and a skillset written once is rendered into the file each harness reads, which means CLAUDE.md where Claude Code is the harness and AGENTS.md elsewhere [6]. Repo-level instruction files stay where they are in the repo. Memories that were really rules ("always run the linter", "never touch the billing module without a test") belong in the skillset; memories that were facts about one repo belong in that repo's file.

Environment variables from the export are set through the org setup script, which runs before each session starts [5].

## What changes about pull requests and review?

Jules ended each task with a choice between Publish branch and Publish PR [3]. Jiro hands back a pull request, or a commit, comment or completed task, and your team reviews it, merges it or sends it back [13]. The review step stays with your team either way, so branch protection rules you had for Jules carry over unchanged.

What you lose is the CI fixer that Jules added on 2026-02-19 along with committing as you [21]. Jiro has no automatic equivalent; the substitute is to reply in the same Slack thread when CI fails and ask for the fix, which continues the original session [10]. Each session and every action inside it ends up in a log you can search [22], so an auditor can trace who asked for what. Repo access is governed by the GitHub App scope you chose at install time [7].

## How do limits and billing change?

Jules counted tasks: a free account could run 15 in a day with 3 going at once; on the Pro bundle the ceilings were 100 and 15; on Ultra, 300 and 60 [23]. The paid tiers cost $19.99 monthly for AI Pro, or AI Ultra starting at $99.99 [24], and were sold to personal Google accounts only [25].

Jiro meters nothing per task. Plans are measured in runtimes, and idle runtimes go to sleep [14]. Developer, $99 monthly, is a single-user plan carrying up to three runtimes. Team, at $250 monthly, is the multi-user plan and shares five among everyone [15]. One active session takes one machine [12], so parallel Slack threads need parallel runtimes.

The model bill moves to your existing provider. Whatever Claude or ChatGPT plan or API key you connect is what Claude Code and Codex draw on [16], with zero markup from Nori [26]. Anthropic's published planning figure for Claude Code is around $13 a day for every developer who is active [27], and Max, at $100 monthly, gives five times what Pro allows [28]. Per person, Jules at $19.99 a month [24] cost less than Jiro's $99 Developer plan [15]; the difference is that Jiro's model usage draws on a Claude or ChatGPT plan the team already pays for [16].

## When Jules was the better choice

For a solo developer on a personal Google account, Jules was hard to beat, and the shutdown does not change that assessment of what it was. Free accounts got 15 tasks per day, three in parallel, without paying [23], and paid access came as part of a consumer Google AI subscription, $19.99 monthly at the entry tier [24]. It ran Gemini first-party, with Gemini 3.1 Pro reaching Pro users on 2026-03-09 [29], which mattered to teams already deep in Google Cloud. The GitHub loop was simple: put the jules label on an issue [19], let the task run on a throwaway machine that already had Docker and common toolchains [30], publish the branch or PR when done [3], and leave recurring chores to Scheduled Tasks [17]. From 2026-02-19 it could also fix its own CI failures [21].

If staying with Google is the priority, the Google-native successor is Google Antigravity, which the turndown notice credits Jules with shaping [31] and which is offered at no charge [32]. Jiro is the better fit when Claude or ChatGPT seats are already in the budget and the team wants a shared agent in Slack.

## First week on Jiro

Keep every task small enough to review in a few minutes, and use the prompts from your Jules export as raw material.

1. **Day one:** paste the exported setup script into Jiro and ask for a README fix, purely to prove the environment builds [5].
2. **Day two:** recreate your most important Scheduled Task as a cron trigger and watch the first run [4].
3. **Day three:** hand over a ticket Jules used to handle, as a Slack mention with the issue link [10].
4. **Day four:** ask for missing tests on one module and review the PR as you would a new hire's [13].
5. **Day five:** route one boring on-call fix to it and time the round trip.

Write requests like tickets: goal, file or module, and how you will judge it done. Expect pushback on vague asks. Miravoice reached the point where Nori handles over 25% of merged PRs [33]; that took weeks, not days, so judge the first week on review quality rather than volume.

## What if you miss 2026-11-11?

Read-only mode still lets you open old sessions until 2026-12-31 [1], so session history and prompts can be copied out by hand, slowly. What you cannot do is finish an in-flight task, which means any code that never reached Publish branch or Publish PR [3] is effectively gone unless the patch is in the export [2]. Scheduled Tasks simply stop, and nothing warns the person who relied on them.

If you are reading this after the date, skip straight to the quickstart, rebuild schedules from memory, and treat the Jules session log as read-only documentation while it lasts. Prioritize the schedules: a missed nightly job is the failure your team will notice first.

## Jiro at a glance

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

## FAQ

### When does Jules stop working?

Open sessions can be completed through 2026-11-11; after that Jules is read-only, with the final wind-down on 2026-12-31 [1].

### How do I export my Jules sessions and scheduled tasks?

Install the Jules Tools CLI, sign in, and run the export prompt from Google's turndown notice; the bundle covers sessions, schedules, memories, the setup script, env values and the repo list [2].

### Can Jiro use my Google AI Pro or Ultra subscription?

No. Jiro runs Claude Code or Codex, as well as Cursor Agent, OpenCode and pi-acp [8], signed in with a Claude or ChatGPT login, an API key or a Cursor key [16], not with Gemini.

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

It issues a twelve-month token bound to a paid Claude plan (Team, Enterprise, Pro, Max or Ultra) so a machine with no browser can use your subscription [18], which is how Jiro's cloud environments sign in to Claude.

### Do Jules Scheduled Tasks transfer automatically to Jiro?

No. Export them, then recreate each as a cron trigger; Jiro also offers one-off reminders and webhooks [4].

### Does Jiro work for a company on Google Workspace?

Yes. Jiro's plans are not tied to a Google account [15], and Google Drive, Sheets and Gmail are available as integrations [39].

### Should I move to Google Antigravity instead?

If staying inside Google matters more than reusing a Claude or ChatGPT plan, yes: Google's notice says Antigravity is where Jules's influence now shows up [31], and it is offered at no charge [32].

## 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. Google's Jules changelog entry dated 2026-10-29 says Jules will wind down on 2026-12-31, that users have until 2026-11-11 to finish sessions, and that after 2026-11-11 Jules turns read-only until the end of the year. Source: https://jules.google/docs/changelog/ (checked 2026-11-06)
2. Google's turndown notice points to the Jules Tools CLI, installed with npm install -g @google/jules and signed in with jules login, plus an agent prompt that exports account settings, environment variables, scheduled tasks, connected repositories, memories, setup scripts and every session with its prompt, plan, activity log and code patches; code, branches and pull requests stay in GitHub. Source: https://jules.google/docs/changelog/ (checked 2026-11-06)
3. When a Jules task finishes you choose Publish branch or Publish PR. Source: https://jules.google/docs/code (checked 2026-11-06)
4. 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)
5. 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)
6. 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)
7. 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)
8. 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)
9. 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)
10. 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)
11. 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)
12. 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)
13. 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)
14. 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)
15. 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)
16. 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)
17. Jules can run Scheduled Tasks on a recurring basis. Source: https://jules.google/docs/scheduled-tasks/ (checked 2026-11-06)
18. 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)
19. Jules takes work from its web app, GitHub issues labelled jules, the Jules Tools CLI and the Jules API. Source: https://jules.google/docs/changelog/ (checked 2026-11-06)
20. 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)
21. On 2026-02-19 Jules added automatic fixing of CI failures and a setting to commit as you. Source: https://jules.google/docs/changelog/ (checked 2026-11-06)
22. Nori logs every session and every action, and makes them searchable. Source: https://noriagentic.com/for-security-leaders.html (checked 2026-11-06)
23. Jules allows 15 tasks a day and 3 at once on the free tier, 100 a day and 15 at once with Google AI Pro, and 300 a day and 60 at once with AI Ultra. Source: https://jules.google/docs/usage-limits (checked 2026-11-06)
24. Paid Jules tiers come with Google AI Pro at $19.99 a month or AI Ultra from $99.99 a month. Source: https://gemini.google/subscriptions/ (checked 2026-11-06)
25. Paid Jules tiers are offered to personal Google accounts; Workspace users are directed to an interest form. Source: https://jules.google/docs/usage-limits (checked 2026-11-06)
26. 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)
27. 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. Source: https://code.claude.com/docs/en/costs (checked 2026-11-06)
28. 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)
29. Jules made Gemini 3.1 Pro available to Google Pro plan users on 2026-03-09. Source: https://jules.google/docs/changelog/ (checked 2026-11-06)
30. Google's Jules runs each task inside a short-lived VM with common toolchains and Docker installed. Source: https://jules.google/docs/environment (checked 2026-11-06)
31. Google's turndown notice says what people built with Jules is shaping products across Google, including its agent-first platform, Google Antigravity. Source: https://jules.google/docs/changelog/ (checked 2026-11-06)
32. Google Antigravity describes itself as an agentic development platform with an agent manager, and says it is available to developers at no charge. Source: https://antigravity.google/ (checked 2026-11-06)
33. 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)
34. 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)
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. 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)
37. Clifford Ressel is Nori's CTO and co-founder. Source: https://ai.engineer/orgs/nori (checked 2026-11-06)
38. 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)
39. 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)

---

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