Rabbitty Download

Tips

Short recipes for getting the most out of Rabbitty day to day.

The worktree loop

The fastest way to work with Rabbitty is to stop working in your project folder and start working in worktrees — one per task, each on its own branch, each with its own agent. The whole loop is two commands.

1. Create the worktree. From any terminal in your project, press ⌘N (or run New Worktree… from the command palette, ⌘⇧P). Type what you want built, in plain language:

add rate limiting to the public API

That single line does double duty: Rabbitty derives the worktree name from it (add-rate-limiting) and hands it to the agent as its opening prompt. Press Enter.

2. Carry the files git leaves behind — once. git worktree add only materializes tracked files, so a fresh worktree has no .env, no local certs, nothing gitignored. The first time you create a worktree in a repo, the create dialog offers to fix that: press ⇥ to open the file checklist, tick what should travel (.env, .env.local, and friends are detected for you), and save.

Your choice is written to .worktreeinclude at the repo root, so it holds for every worktree you create from then on — you only do this once per project. To change it later, run Configure Carried Files… from the palette.

3. Let the agent work. Rabbitty opens a terminal in the new worktree and starts your current agent there with your description as the prompt. It appears in the sidebar under its parent repo, so you can walk away or press ⌘N again and start a second task in parallel. You get a notification when it finishes or needs a decision.

4. Delete the worktree when you're done. Click the delete icon on the worktree in the sidebar, or run Delete Worktree from the palette. Rabbitty looks at where the branch actually stands and only asks what it needs to:

  • Merged or clean → a single delete confirmation. Nothing to lose.
  • Unmerged work → merge back or discard. Merging commits anything still dirty (as wip: <branch>), merges the branch into your base branch with --no-ff, then removes the worktree and the branch.

Either way the worktree's terminals are closed first, and a failed merge is aborted cleanly and reported — the worktree is left standing rather than half-deleted.

That's the loop: ⌘N, describe, walk away, delete. No git worktree add, no copying .env around, no git merge and cleanup afterwards.

Next