A worktree is an isolated branch and checkout of your repository where a single task runs. Because it's isolated, an agent can work in it without touching anything else you have going. This article walks through your first task from start to finish — the prompt you type, the branch it creates, and the result you review.

1. Start a new task

In your workspace, start a new task and describe what you want the agent to do, in plain language. That first prompt is all it takes to kick things off — you don't have to name a branch or set anything up first.

2. Watch the worktree get its name

When you send that first prompt, Unstoppable Code creates a new worktree for the task and uses your prompt as the basis for the branch name. The task's label changes from a placeholder to the real branch name once it's ready.

You can shape how these names look with branch-naming rules and display-name rules in Settings — for example, prefixing branches with your username and the date, and showing a tidy display name instead of the raw branch. It's worth reviewing those settings once early on.

3. Let the setup script run

As the worktree is created, its setup script runs to prepare the checkout — for example, installing dependencies — if one is configured for your workspace. This is also where a teardown script and a launch script come in: teardown runs when you delete a worktree, and launch defines how to run your app for testing.

4. Work with the agent

The agent works on your task in the worktree's chat.

• For a small change, just talk to it and let it work.
• For something larger, turn on planning mode to review a step-by-step plan — with diagrams and diffs — before any code is written.
• You stay in the loop the whole time: every step the agent takes is visible in the chat.

5. Review the result

When the agent finishes, you'll get a notification (if enabled in settings).

Review what it did:

• Read the diffs to see exactly what changed.
• Run the app with your launch script, or open the in-app browser to test it.
• Follow up in the chat if you want changes.

6. Ship it, or clean up

When you're happy with the result, use the git actions to commit, push, and open a pull request. If the worktree was just an exploration, delete it when you're done — its teardown script runs on the way out, so nothing is left behind.

Do several at once

Because each worktree is fully isolated, you don't have to wait for one task to finish before starting the next. Start several, let them run at the same time, and check on each as it finishes — that's the workflow Unstoppable Code is built around.

Next steps

Working in parallel — run many worktrees at once and keep everything moving.

Core concepts & vocabulary — the terms behind everything you just did.