agents-workspace
One root for every agents domain.
AGENTS_HOME grew from a memory override into a de-facto workspace root, but six
domains never followed it. This package makes the root explicit and resolves
every domain from it in one place.
from agents_workspace import Workspace
ws = Workspace.from_env()
ws.root # AGENTS_WORKSPACE_ROOT, else AGENTS_HOME, else ~/.agents
ws.workdir # AGENTS_WORKDIR, else AGENTS_WORKSPACE_DIR, else root/workspace
ws.memory # AGENTS_MEMORY_PATH, else root/memory
ws.traces # AGENTS_TRACES_DIR, else root/traces
ws.schedules # AGENTS_SCHEDULES_DIR, else root/schedules
ws.personas # AGENTS_PERSONAS_DIR, else root/personas
Domains
| Domain | Env override | Default |
|---|---|---|
memory |
AGENTS_MEMORY_PATH |
root/memory |
rules |
— | root/rules |
skills |
AGENTS_SKILLS_DIR |
root/skills |
modules |
AGENTS_MODULES_DIR |
root/modules |
schedules |
AGENTS_SCHEDULES_DIR |
root/schedules |
traces |
AGENTS_TRACES_DIR |
root/traces |
routine-runs |
AGENTS_ROUTINE_RUNS_DIR |
root/routine-runs |
relay |
AGENTS_RELAY_STATE |
root/relay |
personas |
AGENTS_PERSONAS_DIR |
root/personas |
claude |
— | root/claude when the root is explicit, else ~/.claude |
identity |
AGENTS_IDENTITY_PATH |
root/identity.json |
config |
— | root/config.json |
secrets |
— | root/secrets.json |
store |
— | root/store.db |
Precedence is always: explicit env, then the workspace default, then the global
fallback. AGENTS_HOME and AGENTS_WORKSPACE_DIR stay readable as legacy
aliases; new code writes AGENTS_WORKSPACE_ROOT and AGENTS_WORKDIR.
Registry
Additional workspaces live under AGENTS_WORKSPACES_DIR (default ~/.agents-workspaces). Workspace.list_all() returns the default workspace plus every child with a workspace.json. Workspace.resolve(ref) matches an id, label, directory name, or path. Workspace.create(label) mints a slug directory and initializes it.
CLI
agents-workspace info
agents-workspace path traces
agents-workspace init --label personal
agents-workspace list
agents-workspace create --label personal
agents-workspace migrate --dry-run
migrate moves legacy ~/.agents/<domain> directories into the workspace when
the workspace root is not ~/.agents and the target does not exist yet.
What this is not
- No daemon, no network, no keyring.
- No persona logic. Personas are a domain path.
- No config schema beyond
workspace.json.
Metadata
Release files for agents-workspace 0.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 |
|---|---|---|---|---|
| agents_workspace-0.1.0.tar.gz | 10.6 kB | Without provenance | Details for agents_workspace-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agents_workspace-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for agents_workspace-0.1.0-py3-none-any.whl |
Total release size: 19.5 kB
Release files / agents_workspace-0.1.0.tar.gz
| Download URL | agents_workspace-0.1.0.tar.gz |
|---|---|
| Size | 10.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1f2623298c8182dcd3c977ff3f0c88e72bd1450551e437892679b7915a9f3a0e
|
|
BLAKE2b-256 checksum How to use checksums |
998d282ee336d1f0b97a2cda6fafcd553a70861f44fa5012161894d9f37c5c10
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.6
|
Release files / agents_workspace-0.1.0-py3-none-any.whl
| Download URL | agents_workspace-0.1.0-py3-none-any.whl |
|---|---|
| Size | 8.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e44b8d0427e497a54bb26a8ac191ad12cb910c753043c1c36a65e1d5c5094f73
|
|
BLAKE2b-256 checksum How to use checksums |
7042cf1ded3abecb9e916ffe051c713d0407f3ec5c0b0a22c17306ad929a5719
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.6
|
Security for agents-workspace 0.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.