totebag
Portable, vendor-neutral project knowledge any AI Agent can restore over a CLI.
Built by StratoNext.
Your context shouldn't live inside one vendor's chat history. totebag keeps it in a portable
store you address with a single root URL — any agent that can run a shell command restores a
project with one call and writes back what it learns. No server, no API keys, no lock-in.
Install
uv tool install totebag
Quickstart
Create a project with a description, add work to it, then dump its context:
totebag init
PID=$(totebag project create --name "Payments API" --description "Billing service")
totebag project use $PID
totebag task add --title "Wire webhooks" --description "handle Stripe retries"
totebag tool add --name reconcile --description "ledger-reconciliation skill" --type skill
totebag project context
totebag workspace get --brief --recursive
That's the whole loop: describe a project, add tasks/skills to it, and project context is the
restore blob an agent reads. Point your agent at the bundled guide so it knows the rest of the
commands:
totebag --skill
What a project can hold
| Item | What |
|---|---|
| notes | one-line facts |
| links | URLs (typed) |
| docs | editable markdown documents |
| assets | arbitrary files |
| tools / skills | dependencies the project needs (file optional) |
| lists | schema-free entry collections, exportable as CSV |
| tasks | deferred future work, each with its own attachments |
Plus the project's own description and instructions. Everything you store carries a
description — so project context stays high-signal.
Store location
totebag defaults to ~/.totebag. Point it anywhere with TOTEBAG_ROOT (or --root) — the URL
scheme picks the backend:
export TOTEBAG_ROOT=s3://my-bucket/totebag
S3 and GCS need an extra: totebag[s3] / totebag[gcs].
Contributing
Prerequisites and the local development workflow are in CONTRIBUTING.md.
License
MIT
Credits
Release files for totebag 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| totebag-0.1.1.tar.gz | 198.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| totebag-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 233.4 kB
Release files / totebag-0.1.1.tar.gz
| Download URL | totebag-0.1.1.tar.gz |
|---|---|
| Size | 198.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
99315182bf1a1275f559e311288fcfe064d8c77f615ae393277048c09a92abe3
|
|
BLAKE2b-256 checksum How to use checksums |
847c8dbb9bef463fd07f99c39140563a5c7d84ebdc8b6bf8aa24a60bebbb627a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 8, 2026.
Transparency logRelease files / totebag-0.1.1-py3-none-any.whl
| Download URL | totebag-0.1.1-py3-none-any.whl |
|---|---|
| Size | 35.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
615ac197767901e94f77a51ae2701e902e95e10b1ac4fa0b41b8941ead58a471
|
|
BLAKE2b-256 checksum How to use checksums |
094ca44913b43e906373ce83b01d83dbe49a6dcf3ac91127c7455ba8f0fc6a07
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 8, 2026.
Transparency log