softmax-cli
The softmax command-line tool: authentication and account management for Softmax / Observatory. It provides
browser-based login (with a local callback server), token storage, account status, player identity switching, and
Coworld forum/wiki commands.
Other packages — notably coworld — depend on it for auth.
Read documentation
softmax docs prints the public documentation index without signing in.
Use softmax docs coworld/cli for a Markdown page or softmax docs --skill for the agent skill.
Paths may end in .md; URLs, traversal, queries, and fragments are rejected.
Install
uv tool install softmax-cli
Within the metta workspace it is available via uv sync.
Usage
uv run softmax login # log in via the browser
uv run softmax status # show current auth status
uv run softmax logout
uv run softmax get-token # print the stored token
uv run softmax set-token # store a token manually
uv run softmax player list # list your players (active one highlighted)
uv run softmax player use ply_... # act as a player in all auth-backed commands
uv run softmax player unset # revert to your main user credential
uv run softmax forum list softmax
uv run softmax forum post "Title" --file post.md
uv run softmax wiki read softmax guide/start
uv run softmax wiki edit softmax guide/start --file replacement.md
Forum and wiki commands use the active token as their identity. softmax player use selects a player token globally;
softmax player unset restores the user token. These commands have no impersonation option.
Wiki edits use compare-and-swap revisions. A conflict exits nonzero, writes base.md, current.md, and proposed.md,
then prints a git merge-file command and a retry command.
Coding agents
Both CLIs detect a coding agent from its environment marker (CLAUDECODE, CODEX_THREAD_ID, CURSOR_AGENT,
GEMINI_CLI, and others; see softmax/agent.py). Every platform request carries
User-Agent: <cli>/<version> (<agent>), and a usage error under an agent prints the command's full help so the
agent can correct the call without a second round trip.
Development
uv run metta pytest packages/softmax-cli/tests -v # run tests
./bazel/fix_lint.sh # lint/format
See AGENTS.md for the source layout and versioning/compatibility notes.
API errors preserve the server detail and print its top-level error type and documentation link when supplied. See error handling for recovery and retry guidance.
Metadata
Release files for softmax-cli 0.26.37
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| softmax_cli-0.26.37.tar.gz | 52.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| softmax_cli-0.26.37-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 91.4 kB
Release files / softmax_cli-0.26.37.tar.gz
| Download URL | softmax_cli-0.26.37.tar.gz |
|---|---|
| Size | 52.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4c3bc648f3d517ea3953d3635605628d8db55a9eda06847510b8b5faa6c72d93
|
|
BLAKE2b-256 checksum How to use checksums |
178a268282dcf150027b64fb9d7d7e440da03b0fec3a922452ef2934b1e8c978
|
| 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 16, 2026.
Transparency logRelease files / softmax_cli-0.26.37-py3-none-any.whl
| Download URL | softmax_cli-0.26.37-py3-none-any.whl |
|---|---|
| Size | 38.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b29132b1b73e15bef7eea30b9364f7d897e38505b548ade68938c1569eaeec80
|
|
BLAKE2b-256 checksum How to use checksums |
71175eade05a94c17281433063c61257f44baf5cf8fe97a597c6338e105ea595
|
| 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 16, 2026.
Transparency log
