wisp GitHub

GuidesAgents side by side

Moving off Jules

Jules goes read-only on 11 November and closes on 31 December 2026. Here is how its tasks, setup scripts, schedules and PRs carry over to wisp.

wisp guidesUpdated · 5 min read
A wisp report for a finished task: headline, numbers, the real diff and the test run, with Ship it

Google is winding Jules down: finish your sessions by 11 November 2026, then it’s read-only until it closes on 31 December. Your branches and pull requests stay on GitHub; export the rest with the Jules CLI. To keep handing off tasks and coming back to a PR, run wisp: each task runs in its own git worktree with the agent CLIs you already have, Antigravity included, and ends with a short report and Ship it to open the PR.

macOS · Linux and Windows in beta · Node 20+ · MIT

The dates, and what to export

WhenWhat happens
Until 11 November 2026Finish the sessions you have open
11 November to 31 DecemberJules is read-only
31 December 2026Jules shuts down

Nothing on GitHub goes away: branches and PRs Jules opened are yours. The export covers what lives only in Jules. Google’s steps start with the Jules CLI:

npm install -g @google/jules
jules login

Then follow the export prompt in the Jules changelog (29 October 2026 entry). Keep the export folder private: env-variables.json holds your environment variables’ values. The pieces you’ll reuse below are your setup scripts, environment variables and scheduled tasks.

Dates from Google’s Jules changelog, 29 October 2026.

Jules, mapped onto wisp

The big difference is where the agent runs. Jules ran in Google’s VMs on Gemini. wisp runs the agent CLIs you install (Claude Code, Codex, Cursor, opencode, Antigravity, Grok, Copilot) on your computer, your other machines, or your own cloud wisp, signed in with your own plans.

In JulesIn wisp
A task on a repo, in a cloud VMA task in its own git worktree and branch from origin/main, on this computer, a machine you added, or wisp Cloud
Setup script.wisp/worktree.json: { "setup": ["npm ci"] } runs in each new worktree
Environment variablesIgnored files copied into each worktree: the root’s .env files, or what .worktreeinclude lists
Approve the plan firstAsk for it in the prompt (write a plan and ask me before you change anything): the agent asks you and the task waits under Needs you until you answer. Or launch in Plan mode, read-only
Publish a branch, open a PRShip it commits, pushes and opens the PR with gh; the card follows checks and reviews; Merge squash-merges and syncs your local main
Fix CI on its PRsA CI failed trigger starts a task when a GitHub Actions run fails, or a crew member like Scout · CI watcher checks CI every 30 minutes and fixes what breaks
Scheduled tasksA Schedule trigger runs a saved prompt (a recipe) on a cron, or a crew member works on its own schedule
MemoryA crew member’s notebook carries what it learned from job to job; the agent CLIs also read the repo’s AGENTS.md or CLAUDE.md
Jules CLI and APIThe wisp CLI (every command takes --json), the HTTP API and webhooks
GeminiAntigravity, where Google points Jules users, through its CLI (agy): one harness among the others

Set up a repo the Jules way

  1. Start wisp in the repo with npx wisp-agents. Install and sign in to the agent CLIs you want, and sign in to the GitHub CLI (gh auth login) so Ship it can open PRs.
  2. Bring your setup script into .wisp/worktree.json, so every task’s worktree installs its dependencies before the agent starts.
  3. Bring your environment variables as a .env file in the repo’s root folder, kept out of git. Each worktree gets a copy; list other ignored files in .worktreeinclude.
  4. Send a task off and go do something else. Several at once is fine: each has its own worktree, so they never touch each other or your checkout.
  5. Read the report, then Ship it. Each task ends with a headline, the real diff and the test run. Follow up if it’s not right, or press Ship it (S).
cd ~/code/app
npx wisp-agents "fix the flaky auth test"          # the agent you last picked
npx wisp-agents --agent antigravity "add a test"   # or pick one

Schedules, CI and a crew

Jules’ scheduled tasks become triggers (⌘K → Triggers): a Schedule on a cron like 0 9 * * 1-5, CI failed on a GitHub Actions run, or Issue labelled for an open issue with a label you pick. They poll GitHub with your gh login, so nothing has to reach your machine, and they run while wisp is open.

For work that should keep going on its own, add a crew member: a named agent with a brief, a schedule and a notebook. Templates include Scout · CI watcher, Quill · PR reviewer and Tinker · Dependency keeper. Every job is a task of its own, with its worktree, report and Ship it. See Organize your crew.

With the laptop shut, from your phone

  • A computer that stays on. Run tasks on a desktop or a server through Machines, or on wisp Cloud: your own wisp on a server, free during the preview, that sleeps when nothing runs.
  • From your phone. Open grid.trywisp.dev in any phone browser to reach your cloud wisp and every computer you added, or use the Android app (a prototype you build from the repo). See use your agents from anywhere.
  • Told when it needs you. Questions and finished tasks go to ntfy or Telegram, with the answers as buttons.

Questions

Does wisp run my tasks in the cloud like Jules did?

Only if you want it to. By default tasks run on your own computer. wisp Cloud gives you your own wisp on a server (free during the preview), and Machines runs tasks on any computer you can reach over SSH or the grid.

Can I keep using Gemini?

Through the Antigravity CLI, which wisp runs like any other harness. You can also send the same task to Antigravity and Claude Code or Codex at once and keep the better result (Compare).

What happens to the PRs Jules opened?

Nothing: they’re on GitHub, where you review and merge them as before. New work from wisp opens PRs the same way, with Ship it.

Is it free?

wisp is free and MIT. The agents run on your own plans and accounts, and wisp doesn’t charge for or resell model usage.

Try it on your own repo

One command starts wisp in this folder. It runs the agent CLIs you already have, signed in as you.

macOS · Linux and Windows in beta · Node 20+ · MIT

Source on GitHub

Runs Claude Code, Codex, Cursor CLI, opencode, Antigravity CLI, Grok Build and Copilot CLI