Appearance
Server Mode
Server mode lets you run Chippery as a headless service, enabling remote access and integrations.
Quick Start
Generate an auth token:
/server-authEnable server mode:
/server-enableStart the server:
/server-start
Commands
| Command | Description |
|---|---|
/server-enable | Enable headless server mode |
/server-disable | Disable headless server mode |
/server-start | Start the headless server |
/server-stop | Stop the headless server |
/server-status | Show server status and port |
/server-auth | Manage authentication tokens |
Authentication
Before enabling the server, you need to create an auth token. Run /server-auth to open the token management dialog.
Creating a Token
- Run
/server-auth - Enter a name for your token (optional, helps you identify it later)
- Select permissions:
- Read - Can read files and view content
- Write - Can edit files and make changes
- Execute - Can run commands and tools
- Select expiry (30 days, 90 days, 180 days, 1 year, or never)
- Click Generate
Important: The token is shown only once. Copy it immediately and store it securely.
Using Your Token
When connecting to the server remotely, provide your token for authentication. The exact method depends on how you're connecting (API client, integration, etc.).
Server Status
Check if the server is running and which port it's using:
/server-statusThis shows:
- Whether server mode is enabled
- Whether the server is currently running
- The port number
Typical Workflow
Enable and Start
/server-auth # Create a token (first time only)
/server-enable # Enable server mode
/server-start # Start the serverStop and Disable
/server-stop # Stop the server
/server-disable # Disable server modeSettings
You can also manage server settings through the config UI:
/configNavigate to the Server section to:
- Enable or disable server mode
- Configure session limits
- Manage auth tokens