{ "@context": "https://schema.org", "@id": "https://aggr.aymericbeaumet.com/items/ampcode-com/2026-09-22-one-runner-many-worktrees/#webpage", "@type": [ "WebPage", "ArchiveComponent" ], "articleBody": "A [runner](https://ampcode.com/docs/cli/runners) can now create Git worktrees. Pick a repository the runner serves, hit Tab, name the branch, and the thread starts in a fresh checkout. Your main checkout stays untouched.\n\n![The new thread composer on ampcode.com with the runner mac-mini selected and the directory picker open. The amp repository is highlighted and offers Current or New Worktree.](https://static.ampcode.com/news/one-runner-many-worktrees-picker-dark.png)\n\nIn the directory picker, every Git checkout on the runner gets a **New Worktree** option next to it. Choose it and you get a small form:\n\n![The worktree form in the new thread composer: New worktree of amp, name fix-flaky-login-test, directory ~/code/amp-fix-flaky-login-test, branch fix-flaky-login-test, from current HEAD, and a Create Worktree button](https://static.ampcode.com/news/one-runner-many-worktrees-form-dark.png)\n\nThe name you chose becomes the branch name and the folder name. The runner then creates the worktree as a sibling of the repository: `~/code/amp` gets `~/code/amp-fix-flaky-login-test`, checked out on a new branch `fix-flaky-login-test` off the current `HEAD`. Uncommitted changes stay where they are, in the original checkout. The new directory shows up in the picker right away, marked with a branch icon, and the thread starts in it.\n\n[Puck](https://ampcode.com/docs/puck) can do this too: ask it to start a thread on your runner in a new worktree and it passes a `worktree` name to `create_thread`.\n\n## Clean Up When You're Done\n\nA thread that runs in a worktree the runner created gets a new action: **Archive and Remove Worktree**. It archives the thread, runs `git worktree remove`, and deletes the branch.\n\n![The thread actions menu on ampcode.com with a new entry, Archive and Remove Worktree, between Archive and Delete](https://static.ampcode.com/news/one-runner-many-worktrees-menu-dark.png)\n\n## New Folders and Projects Too\n\nThe picker can also create things. Type the name of a directory that doesn't exist yet and you get **New Directory** or **New Project**. [Read more.](https://ampcode.com/docs/cli/runners#create-a-directory-or-project)\n\n![The directory picker in the new thread composer with a name typed that doesn't exist yet, offering New Directory and New Project](https://static.ampcode.com/news/one-runner-many-worktrees-create-dark.png)\n\n## Oh, They Understand Secrets Now Too\n\nRunners can also use the [Secrets & Env Vars](https://ampcode.com/docs/orbs/handling-secrets) you configure on ampcode.com. Same variables that orbs get. It's off by default; opt in with `--amp-env`:\n\n```shell-session\n$ amp --no-tui --runner-id mac-mini --discover-dirs --amp-env\n```\n\nEvery time a thread starts, the runner fetches the variables that apply to it (personal, then project, then workspace) and adds them to the environment of the thread's shell commands, MCP servers, and plugins. Change a variable on ampcode.com and the next thread gets the new value. No restart, no SSH.\n\nBoth need a runner on the current Amp version. If yours has been running for a while, it has [updated itself](https://ampcode.com/docs/cli/runners#keep-a-runner-updated) already.\n\nRead more about [worktrees](https://ampcode.com/docs/cli/runners#create-a-worktree) and [Secrets & Env Vars](https://ampcode.com/docs/cli/runners#secrets-env-vars) in the runner docs.\n", "authors": [], "captured_at": "2026-10-03T23:09:50.514863041+00:00", "category": "programming", "content_html": "

A runner can now create Git worktrees. Pick a repository the runner serves, hit Tab, name the branch, and the thread starts in a fresh checkout. Your main checkout stays untouched.

\n

\"The

\n

In the directory picker, every Git checkout on the runner gets a New Worktree option next to it. Choose it and you get a small form:

\n

\"The

\n

The name you chose becomes the branch name and the folder name. The runner then creates the worktree as a sibling of the repository: ~/code/amp gets ~/code/amp-fix-flaky-login-test, checked out on a new branch fix-flaky-login-test off the current HEAD. Uncommitted changes stay where they are, in the original checkout. The new directory shows up in the picker right away, marked with a branch icon, and the thread starts in it.

\n

Puck can do this too: ask it to start a thread on your runner in a new worktree and it passes a worktree name to create_thread.

\n

Clean Up When You're Done

\n

A thread that runs in a worktree the runner created gets a new action: Archive and Remove Worktree. It archives the thread, runs git worktree remove, and deletes the branch.

\n

\"The

\n

New Folders and Projects Too

\n

The picker can also create things. Type the name of a directory that doesn't exist yet and you get New Directory or New Project. Read more.

\n

\"The

\n

Oh, They Understand Secrets Now Too

\n

Runners can also use the Secrets & Env Vars you configure on ampcode.com. Same variables that orbs get. It's off by default; opt in with --amp-env:

\n
$ amp --no-tui --runner-id mac-mini --discover-dirs --amp-env\n
\n

Every time a thread starts, the runner fetches the variables that apply to it (personal, then project, then workspace) and adds them to the environment of the thread's shell commands, MCP servers, and plugins. Change a variable on ampcode.com and the next thread gets the new value. No restart, no SSH.

\n

Both need a runner on the current Amp version. If yours has been running for a while, it has updated itself already.

\n

Read more about worktrees and Secrets & Env Vars in the runner docs.

\n", "content_markdown": "A [runner](https://ampcode.com/docs/cli/runners) can now create Git worktrees. Pick a repository the runner serves, hit Tab, name the branch, and the thread starts in a fresh checkout. Your main checkout stays untouched.\n\n![The new thread composer on ampcode.com with the runner mac-mini selected and the directory picker open. The amp repository is highlighted and offers Current or New Worktree.](https://static.ampcode.com/news/one-runner-many-worktrees-picker-dark.png)\n\nIn the directory picker, every Git checkout on the runner gets a **New Worktree** option next to it. Choose it and you get a small form:\n\n![The worktree form in the new thread composer: New worktree of amp, name fix-flaky-login-test, directory ~/code/amp-fix-flaky-login-test, branch fix-flaky-login-test, from current HEAD, and a Create Worktree button](https://static.ampcode.com/news/one-runner-many-worktrees-form-dark.png)\n\nThe name you chose becomes the branch name and the folder name. The runner then creates the worktree as a sibling of the repository: `~/code/amp` gets `~/code/amp-fix-flaky-login-test`, checked out on a new branch `fix-flaky-login-test` off the current `HEAD`. Uncommitted changes stay where they are, in the original checkout. The new directory shows up in the picker right away, marked with a branch icon, and the thread starts in it.\n\n[Puck](https://ampcode.com/docs/puck) can do this too: ask it to start a thread on your runner in a new worktree and it passes a `worktree` name to `create_thread`.\n\n## Clean Up When You're Done\n\nA thread that runs in a worktree the runner created gets a new action: **Archive and Remove Worktree**. It archives the thread, runs `git worktree remove`, and deletes the branch.\n\n![The thread actions menu on ampcode.com with a new entry, Archive and Remove Worktree, between Archive and Delete](https://static.ampcode.com/news/one-runner-many-worktrees-menu-dark.png)\n\n## New Folders and Projects Too\n\nThe picker can also create things. Type the name of a directory that doesn't exist yet and you get **New Directory** or **New Project**. [Read more.](https://ampcode.com/docs/cli/runners#create-a-directory-or-project)\n\n![The directory picker in the new thread composer with a name typed that doesn't exist yet, offering New Directory and New Project](https://static.ampcode.com/news/one-runner-many-worktrees-create-dark.png)\n\n## Oh, They Understand Secrets Now Too\n\nRunners can also use the [Secrets & Env Vars](https://ampcode.com/docs/orbs/handling-secrets) you configure on ampcode.com. Same variables that orbs get. It's off by default; opt in with `--amp-env`:\n\n```shell-session\n$ amp --no-tui --runner-id mac-mini --discover-dirs --amp-env\n```\n\nEvery time a thread starts, the runner fetches the variables that apply to it (personal, then project, then workspace) and adds them to the environment of the thread's shell commands, MCP servers, and plugins. Change a variable on ampcode.com and the next thread gets the new value. No restart, no SSH.\n\nBoth need a runner on the current Amp version. If yours has been running for a while, it has [updated itself](https://ampcode.com/docs/cli/runners#keep-a-runner-updated) already.\n\nRead more about [worktrees](https://ampcode.com/docs/cli/runners#create-a-worktree) and [Secrets & Env Vars](https://ampcode.com/docs/cli/runners#secrets-env-vars) in the runner docs.\n", "dateCreated": "2026-10-03T23:09:50.514863041+00:00", "date_created": "2026-09-22T00:00:00+00:00", "date_modified": "2026-09-22T00:00:00+00:00", "date_published": "2026-09-22T00:00:00+00:00", "description": "A runner can now create Git worktrees. Pick a repository the runner serves, hit Tab, name the branch, and the thread starts in a fresh checkout. Your main checkout stays untouched. In the directory picker, every Git checkout on the runner…", "external_url": "https://ampcode.com/news/one-runner-many-worktrees", "git": { "commit": "ebb0941c5c06a2ab2377342d607535262a3e969e", "path": "items/ampcode-com/2026/09/2026-09-22-one-runner-many-worktrees.md", "permalink": "https://github.com/aymericbeaumet/aggr-instance/blob/ebb0941c5c06a2ab2377342d607535262a3e969e/items/ampcode-com/2026/09/2026-09-22-one-runner-many-worktrees.md" }, "id": "urn:aggr:item:1a8097ab868a8b27b2b8f174cca1795d0ea44d61", "isBasedOn": { "@id": "https://ampcode.com/news/one-runner-many-worktrees" }, "mainEntity": { "@id": "https://ampcode.com/news/one-runner-many-worktrees", "@type": "CreativeWork", "archivedAt": { "@id": "https://aggr.aymericbeaumet.com/items/ampcode-com/2026-09-22-one-runner-many-worktrees/#webpage" }, "dateModified": "2026-09-22T00:00:00+00:00", "datePublished": "2026-09-22T00:00:00+00:00", "headline": "One Runner, Many Worktrees", "timeRequired": "PT2M", "url": "https://ampcode.com/news/one-runner-many-worktrees", "wordCount": 355 }, "name": "Archived snapshot: One Runner, Many Worktrees", "preview": null, "reading_minutes": 2, "replicated_at": null, "source": "ampcode-com", "source_name": "Amp News", "summary": "A runner can now create Git worktrees. Pick a repository the runner serves, hit Tab, name the branch, and the thread starts in a fresh checkout. Your main checkout stays untouched. In the directory picker, every Git checkout on the runner gets a New Worktree option next to it. Choose it and you get a small form: The name you chose becomes the branch name and the folder name. The runner then creates the worktree as a sibling of the repository: ~/code/amp gets ~/code/amp-fix-flaky-login-test, checked out on a new branch fix-flaky-login-test off the current HEAD. Uncommitted changes stay where they are, in the original checkout. The new directory shows up in the picker right away, marked with a branch icon, and the thread starts in it. Puck can do this too: ask it to start a thread on your runner in a new worktree and it passes a worktree name to create_thread. Clean Up When You're Done A thread that runs in a worktree the runner created gets a new action: Archive and Remove Worktree. It archives the thread, runs git worktree remove, and deletes the branch. New Folders and Projects Too The picker can also create things. Type the name of a directory that doesn't exist yet and you get New Directory or New Project. Read more. Oh, They Understand Secrets Now Too Runners can also use the Secrets & Env Vars you configure on ampcode.com. Same variables that orbs get. It's off by default; opt in with --amp-env: $ amp --no-tui --runner-id mac-mini --discover-dirs --amp-env Every time a thread starts, the runner fetches the variables that apply to it (personal, then project, then workspace) and adds them to the environment of the thread's shell commands, MCP servers, and plugins. Change a variable on ampcode.com and the next thread gets the new value. No restart, no SSH. Both need a runner on the current Amp version. If yours has been running for a while, it has updated itself already. Read more about worktrees and Secrets & Env Vars in the runner docs.", "tags": [], "temporalCoverage": "2026-10-03T23:09:50.514863041+00:00", "title": "One Runner, Many Worktrees", "url": "https://aggr.aymericbeaumet.com/items/ampcode-com/2026-09-22-one-runner-many-worktrees/", "word_count": 355 }