Skip to main content

Documentation Index

Fetch the complete documentation index at: https://cobo.com/developers/llms.txt

Use this file to discover all available pages before exploring further.

Try Cobo WaaS Skill in your AI coding assistant (Claude Code, Cursor, etc.). Describe your needs in natural language to auto-generate production-ready SDK code and debug faster ๐Ÿš€
Cobo CLI allows you to switch between the development and production environments. This guide explains how to switch between environments effectively. Always remember to switch to the correct environment before executing commands to avoid unintended actions in the wrong environment.
Cobo CLI is designed for use in the development environment by default. Always exercise caution when using it in the production environment, and ensure you understand the implications of each command before execution.

โ€‹
View current environment

To check which environment is currently active, use: 
cobo env
This command will display the name of the currently active environment.

โ€‹
Set environment

To switch to a different environment, use the following command: 
cobo env <environment>
Replace <environment> with your desired environment (dev or prod). This command will set the specified environment as the active one for subsequent CLI commands.
If you donโ€™t specify an environment, Cobo CLI defaults to the โ€œdevelopmentโ€ environment.

โ€‹
Override environment for a single command

You can override the current environment for a single command by using the global -e or --env option: 
cobo -e <environment> {command}
This allows you to execute a command in a specific environment without changing the overall active environment.