reoclo profile

A profile bundles an API URL, an API key, and metadata for one tenant. Profiles let you switch between staging and production, or between multiple tenants you have access to.

Subcommands

reoclo profile ls
reoclo profile use <name>
reoclo profile rm  <name>

`ls`

Lists all configured profiles. The active profile is marked with *.

$ reoclo profile ls
* default   https://api.reoclo.com         acme
  staging   https://api.staging.reoclo.com acme-staging

`use <name>`

Sets the active profile. All subsequent commands use this profile unless overridden by the --profile flag (where supported) or the REOCLO_PROFILE environment variable.

reoclo profile use staging

`rm <name>`

Removes the profile and any stored token. Cannot remove the only remaining profile if you have one active.

reoclo profile rm staging

Where profiles live

Profile metadata is stored in ~/.config/reoclo/config.json (or the platform-equivalent XDG config dir). Tokens are stored separately in the OS keyring; see reoclo keyring status for details.

Examples

Set up two environments and toggle between them:

reoclo login --profile staging --api https://api.staging.reoclo.com
reoclo login --profile prod    --api https://api.reoclo.com
reoclo profile use staging

reoclo servers ls    # against staging
reoclo profile use prod
reoclo servers ls    # against prod

Run a one-off command against a non-active profile (where supported):

reoclo mcp --profile staging

reoclo login — create a profile
reoclo logout — drop the token but keep the profile
reoclo keyring — manage where tokens are stored