Skip to main content
Profiles are local named configurations. Each profile stores:
  • API base URL
  • Token
  • Whether it is the default profile
Profiles are useful when you manage multiple SiteGPT accounts, keep separate production and local environments, or create least-privilege tokens for different agents. Reference: profile commands and aliases.

​
List profiles

Human output shows the profile name, default marker, API base, and a masked token preview.

​
Show one profile

If you omit the profile name, the CLI shows the selected/default profile:

​
Create a profile

Profiles are created by logging in with --profile:
Use --api-base only when you need a non-default environment:

​
Change the default profile

Alias:
After this, commands without --profile use the selected profile.

​
Run a command with a specific profile

-p is an alias for --profile:

​
Delete a profile

Alias:
Deleting a profile removes the token from your local machine. It does not revoke the token in SiteGPT. To revoke a token server-side:

​
Environment overrides

Environment variables override the saved profile for a single command:
Create separate profiles for separate responsibilities:
ProfileExample scopes
setup-agentchatbots:read, chatbots:write, knowledge:write, settings:write, personas:write, instructions:write
knowledge-agentchatbots:read, knowledge:read, knowledge:write, knowledge:delete
support-agentchatbots:read, conversations:read, conversations:write, leads:read, leads:write
billing-readonlyaccount:read, billing:read, usage access through the account token
Use sitegpt profiles list at the start of agent sessions so the agent knows which profile is currently active. For a full agent setup workflow, see Use with AI agents.