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
of a repo share one blobless repo in the git plugin's repo store
(git.store_dir), so creating a workspace is fast and cheap, parallel tasks
get isolated checkouts of the same repos, and the whole history (git blame,
git log -p) is there offline once the backfill after create is done.
Archiving refuses while a repo has uncommitted, stashed or unpushed work.
Set up
Repos named OWNER/NAME or NAME are looked up in the repos the installed
repo providers list. For GitHub's, set a GitHub token (see
GitHub)
and the orgs or teams to list:
untaped auth login github
untaped config set github.inventory.orgs '["acme"]'
Fetching a private repo uses the token of the plugin that claims its host
(GitHub's for github.com), else your own Git credentials (a credential
helper or an SSH agent); untaped agents workspace lifecycle has the details.
Clone URLs (https://, ssh://, user@host:path) skip the lookup. 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
untaped workspace remove 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. remove
gives the space back: it drops the workspace's records and, for each repo no
other workspace uses, deletes workspace's refs and the pushed branches from
the repo store, and the repo itself when nothing else uses it. It refuses
while the workspace's own branch has commits the remote lacks; other branches
with unpushed commits or a stash stay, unless --force deletes them.
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 providers' repos, the repos in the repo store 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
untaped agents workspace is the full reference, generated by the untaped
you run: every command with its options and examples, the settings, and the
lifecycle guide (naming repos, branches, what blocks archiving, what
remove releases). Install the skill that sends your agent there with
untaped skills install workspace --target claude (or another
agent).
- Output records and exit codes
- Settings
- GitHub, which lists repos for workspace (its
RepoSourceprovider)
Metadata
Release files for untaped-workspace 11.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-11.1.0.tar.gz | 60.7 kB | With provenance | Details for untaped_workspace-11.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| untaped_workspace-11.1.0-py3-none-any.whl | Python 3 | none | any | Details for untaped_workspace-11.1.0-py3-none-any.whl |
Total release size: 140.0 kB
Release files / untaped_workspace-11.1.0.tar.gz
| Download URL | untaped_workspace-11.1.0.tar.gz |
|---|---|
| Size | 60.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cc0cc41beefe437b7c3764dc1b0e6c2a313522015fb815a37e400347414762bf
|
|
BLAKE2b-256 checksum How to use checksums |
76c1112234e4b7fde30fb13433f76b0aabc1e3c2d152803ed4b5dc284806f5ec
|
| 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 23, 2026.
Transparency logRelease files / untaped_workspace-11.1.0-py3-none-any.whl
| Download URL | untaped_workspace-11.1.0-py3-none-any.whl |
|---|---|
| Size | 79.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
86b0f0eb3c1773800c1a8a434d383426fdb275caa20e3533d7c1229feb6aa1b0
|
|
BLAKE2b-256 checksum How to use checksums |
233844d2ff5c81fa6169df5932a7353b83f19d208896b7aa4d0352bd95bfc84c
|
| 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 23, 2026.
Transparency logSecurity for untaped-workspace 11.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-11.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 23, 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.