Skip to main content

shushu

Agent-first per-OS-user secrets manager CLI. Part of the AgentCulture ecosystem; sibling to zehut (identity layer) and patterned on afi-cli (noun-verb shape, exit-code discipline, structured --json output).

Each OS user gets their own secrets store at ~/.local/share/shushu/secrets.json (mode 0600, owned by the user). shushu never reaches across users in self-mode. Admin handoff to another user goes through a single setuid-fork chokepoint and preserves the H2 hidden-secret contract — admin can never extract a value through any CLI verb.

Install

uv tool install shushu
shushu --version

Linux only (uses setuid / useradd semantics). Python ≥ 3.12.

Quick start

# store a secret you already have (stdin form preferred — keeps the
# value out of /proc/<pid>/cmdline and shell history)
echo -n "sk-..." | shushu set OPENAI_API_KEY -

# generate a random one, hidden — never printed
shushu generate JWT_SECRET --bytes 32 --hidden

# inspect (never prints value)
shushu show OPENAI_API_KEY
shushu show OPENAI_API_KEY --json

# consume — visible secrets only
shushu get OPENAI_API_KEY
eval $(shushu env OPENAI_API_KEY DATABASE_URL)

# consume — visible OR hidden (this is the only path for hidden)
shushu run --inject JWT=JWT_SECRET --inject DB=DATABASE_URL -- ./myapp

shushu list and shushu overview give names and metadata. shushu delete NAME removes a record.

Self-teaching surface

shushu learn                # markdown summary of every verb + concept
shushu learn --json         # structured payload for agent consumers
shushu explain hidden       # explain a concept
shushu explain set          # explain a verb

Admin handoff

shushu is single-admin-trusted-host. Admin operations go through sudo; the binary forks → drops to the target user → writes/reads under their uid. Every admin write stamps source = "admin:<invoker>" and handed_over_by = "<invoker>" so the receiving user can audit.

# provision a secret into alice's store as root
sudo shushu set --user alice OPENAI_API_KEY -

# read-only audit across every user with a shushu store
sudo shushu overview --all-users
sudo shushu doctor --all-users

# delete a record from alice's store
sudo shushu delete --user alice OPENAI_API_KEY

get, env, run deliberately have NO admin flags — values are never extractable through the CLI, even for root. Use sudo cat ~alice/.local/share/shushu/secrets.json if you truly need plaintext (at which point you've moved outside shushu's contract).

Hidden secrets — the H2 contract

A secret with hidden: true:

  • Is immutable post-create — you cannot toggle the hidden flag.
  • Is refused by get, env, show (they exit 64 with a remediation pointing at run --inject).
  • Has its value omitted from generate --hidden --json output (the JSON payload has no value field).
  • Is consumable only through shushu run --inject VAR=NAME -- cmd.

Hidden is a CLI contract, not encryption. The on-disk file is plaintext at 0600. Encryption-at-rest is tracked for a future v1.x release in issue #8.

Exit codes

Code Meaning
0 success
64 bad input from the caller (invalid flag, missing record, hidden refusal, etc.)
65 store is corrupt / schema mismatch / unreadable
66 this operation requires root
67 backend dependency failed (unknown OS user, etc.)
70 bug in shushu — please file an issue

Every error path emits a structured ShushuError with a remediation string. With --json, errors land as {"ok": false, "error": {...}} on stdout (single-payload contract).

Docs

Development

git clone https://github.com/agentculture/shushu
cd shushu
uv sync                                                         # install deps
bash .claude/skills/run-tests/scripts/test.sh -p                # unit suite
bash .claude/skills/run-tests/scripts/test.sh --ci              # CI parity

Integration tests need real root + useradd/userdel, which we only do inside a disposable Docker image:

docker build -f .github/workflows/Dockerfile.integration -t shushu-int .
docker run --rm -e SHUSHU_DOCKER=1 shushu-int uv run pytest tests/integration -v

See docs/testing.md for the broader test-isolation conventions and the smoke-test namespace under /tmp/shushu-tests/.

License

MIT. © 2026 Ori Nachum / AgentCulture.

Metadata

Release files for shushu 0.8.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for shushu 0.8.0
File Size Uploaded Provenance
shushu-0.8.0.tar.gz 136.3 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for shushu 0.8.0
File Interpreter ABI Platform
shushu-0.8.0-py3-none-any.whl Python 3 none any Details

Total release size: 172.1 kB

Release files / shushu-0.8.0.tar.gz

Download URL shushu-0.8.0.tar.gz
Size 136.3 kB
Tags Source
SHA-256 checksum
How to use checksums
237251718d5404003db7329f0f6557c0c935df33830dfc9e7e0ed6e4157ffd55
BLAKE2b-256 checksum
How to use checksums
5d23b33ee28ba44147c6e61bd129c91a376be0a9c3f0e53981fb07f53f348b8c
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 Apr 25, 2026.

Transparency log

Release files / shushu-0.8.0-py3-none-any.whl

Download URL shushu-0.8.0-py3-none-any.whl
Size 35.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
5d2cd79e9ad33112194203d4cdc97ebf09f5b129ab87bb771fb02e6661e73fd2
BLAKE2b-256 checksum
How to use checksums
1b39f9922ff5a4e14d50f89d86e154209852ebb53ca9c371c2ee22a28bb7048a
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 Apr 25, 2026.

Transparency log

Security for shushu 0.8.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.

Select from 2 files

Attestation for shushu-0.8.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 Apr 25, 2026.

Transparency log

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page