Configuration

The Chamber CLI stores configuration and credentials in ~/.chamber/.

Configuration Files

File	Purpose
`~/.chamber/config.json`	CLI settings (API URL, organization ID, default registry)
`~/.chamber/token.json`	Authentication credentials
`~/.chamber/chat_history`	AI chat readline history (up to 500 entries)

The token.json file contains sensitive credentials. It’s created with 0600 permissions (owner read/write only). Do not share or commit this file.

Settings

Organization ID

Set your default organization for API requests:

chamber config set organization_id your-org-id

Most commands require an organization context. Setting this avoids having to specify it on every command.

Find your organization ID in the Chamber Dashboard under Settings > Organization.

API URL

By default, the CLI connects to https://api.usechamber.io/v1. Override this for development or private deployments:

chamber config set api_url https://your-api-endpoint.com/v1

Default Registry

Set your container registry for the chamber run command to avoid specifying it on every run:

chamber config set default_registry 123456789012.dkr.ecr.us-east-1.amazonaws.com/my-repo

When using ECR, chamber run automatically authenticates using your AWS CLI credentials and creates the repository if it doesn’t exist.

View Configuration

See all current settings:

chamber config show

Output:

Current configuration:
  API URL:          https://api.usechamber.io/v1
  Organization ID:  my-org-id
  Default Registry: 123456789012.dkr.ecr.us-east-1.amazonaws.com/my-repo

Config directory: /Users/you/.chamber

Get a specific value:

chamber config get organization_id

Environment Variables

You can override configuration using environment variables:

Variable	Description
`CHAMBER_API_URL`	Override API URL
`CHAMBER_ORG_ID`	Override organization ID
`CHAMBER_TOKEN`	Override authentication token
`CHAMBER_DEBUG`	Set to `1` for verbose API logging

Example:

CHAMBER_ORG_ID=other-org chamber workloads list

Multiple Profiles

For working with multiple organizations or environments, you can use shell aliases:

# In ~/.bashrc or ~/.zshrc
alias chamber-prod="CHAMBER_ORG_ID=prod-org chamber"
alias chamber-dev="CHAMBER_ORG_ID=dev-org CHAMBER_API_URL=https://dev-api.example.com/v1 chamber"

Usage:

chamber-prod workloads list
chamber-dev workloads list

Reset Configuration

To reset all configuration and credentials:

rm -rf ~/.chamber

Then re-authenticate:

chamber login --token ch.your-api-token
chamber config set organization_id your-org-id

Troubleshooting

”Not logged in” error

Error: not logged in - run 'chamber login' first

Your token may have expired or been deleted. Re-authenticate:

chamber login --token ch.your-api-token

“No organization configured” error

Error: no organization configured - run 'chamber config set organization_id <id>'

Set your organization:

chamber config set organization_id your-org-id

Check your setup

Verify everything is configured correctly:

# Check health
chamber health

# Check authentication
chamber whoami

# Check configuration
chamber config show

Early Access — The Chamber CLI is currently in early access. Contact support@usechamber.io to get started.

​Configuration

​Configuration Files

​Settings

​Organization ID

​API URL

​Default Registry

​View Configuration

​Environment Variables

​Multiple Profiles

​Reset Configuration

​Troubleshooting

​”Not logged in” error

​“No organization configured” error

​Check your setup

Configuration

Configuration Files

Settings

Organization ID

API URL

Default Registry

View Configuration

Environment Variables

Multiple Profiles

Reset Configuration

Troubleshooting

”Not logged in” error

“No organization configured” error

Check your setup