Overview
Thestatus command displays comprehensive information about your PicoClaw installation, including configuration status, workspace location, model settings, provider authentication, and available API keys.
Usage
picoclaw s
Output
The command shows:- Version Information: PicoClaw version and build details
- Configuration Status: Location and validity of config file
- Workspace Status: Location and validity of workspace directory
- Model Configuration: Currently configured default model
- Provider Status: API key availability for all providers
- OAuth Authentication: Active OAuth sessions
Example Output
Fully Configured System
Minimal Configuration
Not Onboarded
picoclaw onboard first
Provider Status Indicators
✓ (Checkmark)
Provider is configured with an API key or endpoint.not set
Provider is not configured.With URL
Local providers show their endpoint:OAuth Authentication Status
When OAuth providers are authenticated, additional information is shown:Status Values
- authenticated: Valid credentials, ready to use
- expired: OAuth token has expired (needs refresh or re-login)
- needs refresh: Token is expiring soon (will auto-refresh)
Supported Providers
The status command checks for:Cloud Providers
- OpenRouter: Multi-model access (100+ models)
- Anthropic: Claude models
- OpenAI: GPT models
- Gemini: Google AI models
- Zhipu: Chinese AI models
- Qwen: Alibaba Cloud models
- Groq: Fast inference
- Moonshot: Chinese AI models
- DeepSeek: Chinese AI models
- VolcEngine: ByteDance AI
- Nvidia: NVIDIA AI Foundation
Local Providers
- Ollama: Local model runtime
- vLLM/Local: Self-hosted vLLM server
OAuth Providers
- OpenAI: OAuth authentication
- Anthropic: Token authentication
- Google Antigravity: Google Cloud Code Assist
Examples
Check Installation Status
Verify After Configuration
After editingconfig.yaml, check that changes are recognized:
Check OAuth Status
After logging in with OAuth:Verify Model Configuration
Check which model is currently default:List All Configured Providers
Configuration Paths
Default Locations
Config File:Custom Paths
You can use environment variables to override:Using Status for Diagnostics
Before First Use
Before Starting Gateway
- Config exists (✓)
- At least one provider configured (✓)
- Model is set
After Changing Providers
Debugging Authentication Issues
- Provider shows “not set” → Add API key
- OAuth shows “expired” → Re-login with
picoclaw auth login - OAuth shows “needs refresh” → Will auto-refresh on next use
Tips
- Quick Check: Run
picoclaw statusbefore starting work to ensure everything is configured - Provider Testing: After adding a new API key, use status to verify it’s recognized
- OAuth Monitoring: Check expiration dates to know when to re-authenticate
- Troubleshooting: Status is the first command to run when something isn’t working
- CI/CD: Use in scripts to verify deployment configuration
Common Issues
Config Not Found
Output:No Providers Configured
Output:OAuth Expired
Output:Model Not Set
Output:Output Format
The status command outputs human-readable text. For scripting, parse specific lines:Exit Codes
0: Always succeeds (displays status even if not configured)
See Also
- picoclaw onboard - Initialize configuration
- picoclaw auth - Manage authentication
- Configuration Guide - Detailed configuration options
- Provider Setup - Configure specific providers