Headless Workflow
Use OAuth providers on servers or remote machines without browser access.Usage
How It Works
- CCS generates an authentication URL
- You open the URL on any device with a browser
- Complete OAuth login
- CCS detects when tokens are cached
- Session continues
Use Cases
- SSH sessions on remote servers
- Docker containers
- CI/CD pipelines (with pre-cached tokens)
- Headless Linux environments
Commands
Pre-Caching Tokens
For automated environments, authenticate locally first:- Run
ccs gemini --authon local machine - Copy
~/.ccs/cliproxy/auth/*.jsonto remote server - Use without
--headlessflag
