{ "@context": "https://schema.org", "@id": "https://aggr.aymericbeaumet.com/items/ampcode-com/2026-09-24-shared-runners/#webpage", "@type": [ "WebPage", "ArchiveComponent" ], "articleBody": "You can now share a [runner](https://ampcode.com/docs/cli/runners) with your workspace. Start it with `--share` and everyone in your workspace can start threads on that machine from ampcode.com.\n\n![The new thread composer on ampcode.com with the location picker open. Under Runners is your own devbox. Under Shared Runners are gpu-runner, shared by Allison, and macos-builder, shared by Monty, each with its owner's avatar and running-thread count.](https://static.ampcode.com/news/shared-runners-picker-dark.png?v=2)\n\nIf you have a machine with GPUs, a Mac that's used to build and sign the iOS app, or a dev box in a specific network, you can now set it up and the whole team can spawn agents on it:\n\n```shell-session\n$ amp --no-tui --runner-id macos-builder --share\n```\n\nEveryone in your workspace now sees it in the picker under **Shared Runners**.\n\nWith [`--amp-env`](https://ampcode.com/docs/cli/runners#secrets-env-vars), a shared runner gets the workspace and project Secrets & Env Vars, but never your personal ones. That applies to your own threads on it too.\n\nWe need to offer a word of warning, though: everyone you share with runs code on your machine as you, with your files, your credentials, and your logins. Their threads can also work in the same directories at the same time. So only share a runner with people you'd trust with a shell on that machine. Even better, give the runner a machine of its own. (Better still: use [orbs](https://ampcode.com/what-are-orbs), so that every thread gets its own machine.)\n\nWorkspace admins can [turn off runner sharing](https://ampcode.com/docs/cli/runners#turn-off-runner-sharing-for-a-workspace) in **Member Settings**.\n\nRead more about [sharing a runner](https://ampcode.com/docs/cli/runners#share-a-runner-with-your-workspace) in the runner docs.\n", "authors": [], "captured_at": "2026-10-03T23:09:50.514863041+00:00", "category": "programming", "content_html": "

You can now share a runner with your workspace. Start it with --share and everyone in your workspace can start threads on that machine from ampcode.com.

\n

\"The

\n

If you have a machine with GPUs, a Mac that's used to build and sign the iOS app, or a dev box in a specific network, you can now set it up and the whole team can spawn agents on it:

\n
$ amp --no-tui --runner-id macos-builder --share\n
\n

Everyone in your workspace now sees it in the picker under Shared Runners.

\n

With --amp-env, a shared runner gets the workspace and project Secrets & Env Vars, but never your personal ones. That applies to your own threads on it too.

\n

We need to offer a word of warning, though: everyone you share with runs code on your machine as you, with your files, your credentials, and your logins. Their threads can also work in the same directories at the same time. So only share a runner with people you'd trust with a shell on that machine. Even better, give the runner a machine of its own. (Better still: use orbs, so that every thread gets its own machine.)

\n

Workspace admins can turn off runner sharing in Member Settings.

\n

Read more about sharing a runner in the runner docs.

\n", "content_markdown": "You can now share a [runner](https://ampcode.com/docs/cli/runners) with your workspace. Start it with `--share` and everyone in your workspace can start threads on that machine from ampcode.com.\n\n![The new thread composer on ampcode.com with the location picker open. Under Runners is your own devbox. Under Shared Runners are gpu-runner, shared by Allison, and macos-builder, shared by Monty, each with its owner's avatar and running-thread count.](https://static.ampcode.com/news/shared-runners-picker-dark.png?v=2)\n\nIf you have a machine with GPUs, a Mac that's used to build and sign the iOS app, or a dev box in a specific network, you can now set it up and the whole team can spawn agents on it:\n\n```shell-session\n$ amp --no-tui --runner-id macos-builder --share\n```\n\nEveryone in your workspace now sees it in the picker under **Shared Runners**.\n\nWith [`--amp-env`](https://ampcode.com/docs/cli/runners#secrets-env-vars), a shared runner gets the workspace and project Secrets & Env Vars, but never your personal ones. That applies to your own threads on it too.\n\nWe need to offer a word of warning, though: everyone you share with runs code on your machine as you, with your files, your credentials, and your logins. Their threads can also work in the same directories at the same time. So only share a runner with people you'd trust with a shell on that machine. Even better, give the runner a machine of its own. (Better still: use [orbs](https://ampcode.com/what-are-orbs), so that every thread gets its own machine.)\n\nWorkspace admins can [turn off runner sharing](https://ampcode.com/docs/cli/runners#turn-off-runner-sharing-for-a-workspace) in **Member Settings**.\n\nRead more about [sharing a runner](https://ampcode.com/docs/cli/runners#share-a-runner-with-your-workspace) in the runner docs.\n", "dateCreated": "2026-10-03T23:09:50.514863041+00:00", "date_created": "2026-09-24T00:00:00+00:00", "date_modified": "2026-09-24T00:00:00+00:00", "date_published": "2026-09-24T00:00:00+00:00", "description": "You can now share a runner with your workspace. Start it with --share and everyone in your workspace can start threads on that machine from ampcode.com. If you have a machine with GPUs, a Mac that's used to build and sign the iOS app, or a…", "external_url": "https://ampcode.com/news/shared-runners", "git": { "commit": "ebb0941c5c06a2ab2377342d607535262a3e969e", "path": "items/ampcode-com/2026/09/2026-09-24-shared-runners.md", "permalink": "https://github.com/aymericbeaumet/aggr-instance/blob/ebb0941c5c06a2ab2377342d607535262a3e969e/items/ampcode-com/2026/09/2026-09-24-shared-runners.md" }, "id": "urn:aggr:item:a3f7cd25e366ec00a9b31b99130161857cdbf08a", "isBasedOn": { "@id": "https://ampcode.com/news/shared-runners" }, "mainEntity": { "@id": "https://ampcode.com/news/shared-runners", "@type": "CreativeWork", "archivedAt": { "@id": "https://aggr.aymericbeaumet.com/items/ampcode-com/2026-09-24-shared-runners/#webpage" }, "dateModified": "2026-09-24T00:00:00+00:00", "datePublished": "2026-09-24T00:00:00+00:00", "headline": "Shared Runners", "timeRequired": "PT1M", "url": "https://ampcode.com/news/shared-runners", "wordCount": 214 }, "name": "Archived snapshot: Shared Runners", "preview": null, "reading_minutes": 1, "replicated_at": null, "source": "ampcode-com", "source_name": "Amp News", "summary": "You can now share a runner with your workspace. Start it with --share and everyone in your workspace can start threads on that machine from ampcode.com. If you have a machine with GPUs, a Mac that's used to build and sign the iOS app, or a dev box in a specific network, you can now set it up and the whole team can spawn agents on it: $ amp --no-tui --runner-id macos-builder --share Everyone in your workspace now sees it in the picker under Shared Runners. With --amp-env, a shared runner gets the workspace and project Secrets & Env Vars, but never your personal ones. That applies to your own threads on it too. We need to offer a word of warning, though: everyone you share with runs code on your machine as you, with your files, your credentials, and your logins. Their threads can also work in the same directories at the same time. So only share a runner with people you'd trust with a shell on that machine. Even better, give the runner a machine of its own. (Better still: use orbs, so that every thread gets its own machine.) Workspace admins can turn off runner sharing in Member Settings. Read more about sharing a runner in the runner docs.", "tags": [], "temporalCoverage": "2026-10-03T23:09:50.514863041+00:00", "title": "Shared Runners", "url": "https://aggr.aymericbeaumet.com/items/ampcode-com/2026-09-24-shared-runners/", "word_count": 214 }