Charlotte
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHARLOTTE_NO_SANDBOX | No | Set to 1 to disable the Chromium sandbox (equivalent to the --no-sandbox CLI flag or "browser": { "noSandbox": true } in the config file). The Chromium sandbox is enabled by default and is the primary defense between an untrusted page and the account Charlotte runs as; opt out explicitly where the kernel sandbox is unavailable, such as in containers or when running Charlotte bare-metal as root. | |
| CHARLOTTE_OUTPUT_DIR | No | Directory where large tool results are written to disk (used by the output_file parameter when a response exceeds maxResponseBytes). | |
| CHARLOTTE_INIT_SCRIPT | No | Path to a script that should run on every new document before page JS executes (equivalent to the --init-script <path> CLI flag, which is repeatable, or browser.initScripts in the config file). | |
| CHARLOTTE_CDP_ENDPOINT | No | Chrome DevTools Protocol endpoint URL used to connect to an existing Chromium instance instead of launching a new browser. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityActive
ResponsivenessNo issues