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; opt out explicitly where the kernel sandbox is unavailable, e.g. in containers or when running bare-metal as root. The provided Dockerfiles set CHARLOTTE_NO_SANDBOX=1 for you. | 0 |
| CHARLOTTE_OUTPUT_DIR | No | Directory where Charlotte writes output artifacts, such as screenshots and large result sets written via output_file. Equivalent to "output": { "dir": ... } in the config file. | ./charlotte-output |
| CHARLOTTE_INIT_SCRIPT | No | Path to a script that Charlotte runs on every new document before page JS (repeatable). Equivalent to "browser": { "initScripts": [...] } or --init-script <path> on the command line. | |
| CHARLOTTE_CDP_ENDPOINT | No | Chrome DevTools Protocol endpoint used to connect to an existing Chromium instance instead of launching a new one. |
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