This release is a pre-release and may not be stable for production use.
Commensa bootstrap
This small public package installs verified Commensa releases and keeps one
stable commensa command in front of them. It does not contain the private
Report, Cockpit, Project X-Ray, commensa me tracking, or Commensa Manager
runtimes.
Install the free Core:
pipx install commensa
commensa install core
After purchasing an entitled product on commensa.ai, install the matching
capability. Commensa privately asks first for the secure access link in the
delivery email, then for the activation key. Neither belongs in a shell command.
commensa install report
commensa install cockpit
commensa install xray
commensa install me
For example, a new Report customer can use one shell line:
pipx install commensa && commensa install report
Approved Manager Early Access operators can install Manager into selected AI interfaces:
commensa install manager --interface codex --interface claude-code
Verified members of an approved organization receive one individual, revocable organization key. It installs all current paid capabilities without placing the key in shell history:
commensa install organization --interface codex --interface claude-code
Update the public command and every installed entitled release with one command. Manager users repeat the interfaces they want kept current:
commensa update --interface codex --interface claude-code
The updater exchanges the existing device credential for a short-lived release grant. It does not retain the activation key or require the old checkout link. It reports each detected runtime family with its observed before/after version and whether it updated, verified the same release, skipped, or failed. The paid runtime includes Core. An unknown version is reported explicitly rather than inferred from the newest retained archive. Any skipped or failed product makes the command exit nonzero; a Core update never counts as a Manager update.
Some older installations have capability records but no reusable registration. These cannot obtain a protected update grant automatically. The updater preserves their entitlement records and prints the normal reinstall command, for example:
commensa install manager --interface codex --interface claude-code
Enter the delivery-email access link and activation key only at the private prompts. If those are unavailable, use Commensa support. The updater does not invent or migrate credentials, and it does not bypass protected download authorization. Release directories retained after removal are diagnosed conservatively as detected installations; their active version can be unknown. An installation verification is separate from confirmation that the public bootstrap's pinned release is the newest published release.
Normal product commands continue through the verified local runtime:
commensa capabilities --json
commensa privacy --json
commensa doctor --json
Current platform boundary
The release candidate supports the same command-line installation flow on
macOS, Linux, and native Windows 11. On Windows, pipx supplies the isolated
Python runtime and Commensa creates managed .cmd launchers; PowerShell or
Command Prompt can run the same commensa install ... commands. WSL remains a
separate Linux route.
The Windows route has automated contract coverage but still requires its first acceptance pass on a physical Windows 11 x64 host before it can be described as host-verified. It is not the separately signed Windows desktop installer.
This PyPI command is the normal customer installation route across supported operating systems. Signed native applications may be added later as optional one-click distribution, but they are not required for the product or for paid licensing. The lower-level download and installer files remain protected implementation and support infrastructure behind this command.
Metadata
Release files for commensa 0.1.0rc9
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 |
|---|---|---|---|---|
| commensa-0.1.0rc9.tar.gz | 13.0 kB | With provenance | Details for commensa-0.1.0rc9.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| commensa-0.1.0rc9-py3-none-any.whl | Python 3 | none | any | Details for commensa-0.1.0rc9-py3-none-any.whl |
Total release size: 28.5 kB
Release files / commensa-0.1.0rc9.tar.gz
| Download URL | commensa-0.1.0rc9.tar.gz |
|---|---|
| Size | 13.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2755c7b413a107ae3da52fc4f334dee904b345adf7b82a4e6dc2016574299322
|
|
BLAKE2b-256 checksum How to use checksums |
009281e34d6739d7bdab212c535361b3a5f68b237a1a64f600d085a597c4bf36
|
| 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 10, 2026.
Transparency logRelease files / commensa-0.1.0rc9-py3-none-any.whl
| Download URL | commensa-0.1.0rc9-py3-none-any.whl |
|---|---|
| Size | 15.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e764d9102c5f529d62473fa5ed084578a2d97bc2a29b66755662742c96f51b10
|
|
BLAKE2b-256 checksum How to use checksums |
83b21d9b56045a7131ace2812860a5da4f6611a2a4d0c890b04a74e08918d729
|
| 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 10, 2026.
Transparency logSecurity for commensa 0.1.0rc9
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
Both files in this release have been uploaded with provenance metadata.
Attestation for commensa-0.1.0rc9.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 Sep 10, 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.