untaped-workspace
Install it as part of untaped: uv tool install 'untaped[workspace]' or pip install 'untaped[workspace]'.
To add it to an existing install, see Getting started.
workspace is experimental and may change in
a minor release.
A workspace is one directory per task. It holds a git worktree for each repo you need, all on the same branch, so you (or an agent) can change several repos for one ticket and archive the lot when the work is pushed. Worktrees share a bare cache of each repo, so creating a workspace is fast and cheap, and parallel tasks get isolated checkouts of the same repos. Archiving refuses while a repo has uncommitted, stashed or unpushed work.
Set up
Repos named OWNER/NAME or NAME are looked up in the GitHub inventory, so
set a GitHub token (see
GitHub)
and the orgs or teams to list:
untaped auth set github
untaped config set github.inventory.orgs '["acme"]'
Cloning private repos needs Git credentials set up in advance; see the skill's setup. Full git URLs skip the inventory. Directories, branch naming and parallelism are in the configuration reference.
Create, work, archive
untaped workspace create PROJ-123 --repo acme/api --repo acme/web --read-only acme/docs
cd "$(untaped workspace path PROJ-123)"
# commit and git push in each repo, then:
untaped workspace status PROJ-123 --check
untaped workspace archive PROJ-123
Each repo gets a new branch from its base, or resumes an existing one;
--read-only repos are reference checkouts. status --check exits 3 while
anything would block archiving. archive removes the worktrees; the branches
stay, so a later workspace on the same branch resumes the work.
Add repos
untaped workspace add PROJ-123 --repo acme/infra
untaped github repos list --team acme/platform --format pipe | untaped workspace add PROJ-123 --stdin
untaped workspace add PROJ-123
add takes repos by name, from a pipe, or, with no repos in a terminal, from
a picker over the GitHub inventory, the repo cache and any git URL you paste.
create opens the same picker, which also creates the workspace with no
repos selected. create NAME --empty makes an empty workspace to add to
later.
Find a workspace
untaped workspace list
untaped workspace list --archived
cd "$(untaped workspace path PROJ-123)"
Inside a workspace directory, the name may be left out.
Run a command in every repo
untaped workspace status PROJ-123
untaped workspace run PROJ-123 'git push -u origin HEAD'
untaped workspace run PROJ-123 ./bump.sh
run has no preview, so check the selection with status first. It runs in
every writable repo and exits 1 if any repo failed.
Reference
The packaged skill is the full reference: every workflow, safety rule and pitfall. Install it for your agent with untaped skills install workspace --target claude (or another agent); untaped workspace COMMAND --help lists each command's options.
- Output records and exit codes
- Settings
- GitHub, which supplies the repo inventory
Metadata
Release files for untaped-workspace 10.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| untaped_workspace-10.1.0.tar.gz | 44.9 kB | With provenance | Details for untaped_workspace-10.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| untaped_workspace-10.1.0-py3-none-any.whl | Python 3 | none | any | Details for untaped_workspace-10.1.0-py3-none-any.whl |
Total release size: 106.0 kB
Release files / untaped_workspace-10.1.0.tar.gz
| Download URL | untaped_workspace-10.1.0.tar.gz |
|---|---|
| Size | 44.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b291cdc0797e8dfe1280f85676ebbf53ddda086c0bad04b5778374c8174c5275
|
|
BLAKE2b-256 checksum How to use checksums |
ef8e155f8af05bee779dc237b9e9b32602de9d9421cda24544c008f92e6a459c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 9, 2026.
Transparency logRelease files / untaped_workspace-10.1.0-py3-none-any.whl
| Download URL | untaped_workspace-10.1.0-py3-none-any.whl |
|---|---|
| Size | 61.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2ad50c05bf599d0145b0e49edb522fae7031841e32123f205e45c8c51882edb4
|
|
BLAKE2b-256 checksum How to use checksums |
c89381d3f999aecf268ecdce2007167aec002f5e0fe213255b890d02e6c1a86e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 9, 2026.
Transparency logSecurity for untaped-workspace 10.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for untaped_workspace-10.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 9, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.