Terminal login

Run terminal commands from command-centre in the Agentic OS repository.

Keep the -- after npm run team. It tells npm to pass the rest of the command to Team OS.

cd command-centre
npm run team -- login --api-url https://team.example.com --email user@example.com --password "<password>"

By default, the CLI saves a server-issued session token outside the repository. It does not save the password. If you set a custom AGENTIC_OS_TEAM_CONFIG_DIR, keep that directory outside version control.

Choose the initial Team

Use the Team slug or ID when the account can access more than one Team:

npm run team -- login --api-url https://team.example.com --email user@example.com --password "<password>" --team acme

The server accepts only an active Team that the signed-in user can access. A different Team ID cannot widen access.

To choose another Team from the terminal, sign in again with a different --team value. In Command Centre, use the Team control instead. Selecting a Team changes the default for new work. Existing work keeps its original Team.

A Company Admin can sign in without access to any Team. Team commands require a Team selection, so request access before using them.

Check the selected Team

Show the server-resolved user, Team, and role label:

npm run team -- whoami

Example output:

Signed in as: user@example.com
Team: Acme
Role: member

Show the clients available in the selected Team:

npm run team -- clients

Example output:

acme     read     Acme
globex   write    Globex

Team Members see clients from active grants. Users with Full access see every active client with implicit write access.

If a Team Member has no client grants, the command prints:

No clients are available for this account.

Sign out

npm run team -- logout

Signing out removes the saved local connection. If a session expires, sign in again with the same server URL and account.

Next: Saved config directory