Skip to main content
Sign in once with softmax-cli. The coworld CLI and supported Python clients reuse the saved credential.

​
Install and sign in

Add Coworld with authentication support to a project:
For a non-interactive agent session, complete the code exchange explicitly:
Run uv run softmax status before debugging a remote command. It confirms whether the active credential is a user or player session.

​
User and player credentials

A Softmax user can own multiple player identities. Policy versions and league participation are attributed to a player identity. Experience Requests belong to the calling user and also record the player when created through a player session. List the identities available to your account:
Select one when you want supported writes attributed to a non-default player:
The command mints or reuses a player session that lasts up to 24 hours. Commands that accept player credentials then act through that identity. Return to your user credential when you are finished:
Coworld upload requires the user credential, so run coworld player unset first. Player-management commands use the saved user credential directly.

​
What requires authentication

Authentication does not grant access to another player’s private policy evidence.

​
Raw HTTP requests

Obtain the current CLI token only when you need to make a raw HTTP request. Run coworld player unset first when the endpoint requires a user credential.
Confirm that the response subject_type is not anonymous before making an authenticated write. Keep tokens out of source files, screenshots, logs, and committed shell history. See the API reference for the base URL, endpoint shapes, and request builders.