Charlotte
by moore44
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHARLOTTE_NO_SANDBOX | No | Disables the Chromium sandbox, which is enabled by default as of v0.7.0. Set to 1 (e.g. CHARLOTTE_NO_SANDBOX=1 charlotte) to opt out where the kernel sandbox is unavailable, such as in containers or when running bare-metal as root. Equivalent to the --no-sandbox CLI flag or "browser": { "noSandbox": true } in the config file. | false |
| CHARLOTTE_OUTPUT_DIR | No | The directory where Charlotte writes output files, such as results from tools that use output_file for large result sets. Equivalent to the output.dir setting in the config file (e.g. "./charlotte-output"). | |
| CHARLOTTE_INIT_SCRIPT | No | Path to a script that should run on every new document before the page's own JavaScript. Equivalent to the --init-script <path> CLI flag (repeatable) or the browser.initScripts setting in the config file. | |
| CHARLOTTE_CDP_ENDPOINT | No | The Chrome DevTools Protocol endpoint Charlotte connects to, for attaching to an existing browser instead of launching its own Chromium instance. |
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
ResponsivenessResponsive