Charlotte
by Burke35546
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHARLOTTE_NO_SANDBOX | No | Disables the Chromium sandbox. The sandbox is enabled by default as of v0.7.0 (it is the primary defense between an untrusted page and the account Charlotte runs as), so you must opt out explicitly where the kernel sandbox is unavailable — e.g. containers, or bare-metal running as root. Equivalent to the --no-sandbox CLI flag or "browser": { "noSandbox": true } in the config file; the provided Dockerfiles set CHARLOTTE_NO_SANDBOX=1 for you. | |
| CHARLOTTE_OUTPUT_DIR | No | Directory where output artifacts (e.g. screenshots and results written via output_file) are stored. Defaults to ./charlotte-output. Equivalent to "output": { "dir": "./charlotte-output" } in the config file. | |
| CHARLOTTE_INIT_SCRIPT | No | Path to a script that should run on every new document before page JS. Equivalent to the repeatable --init-script <path> CLI flag or "browser": { "initScripts": [...] } in the config file. | |
| CHARLOTTE_CDP_ENDPOINT | No | CDP endpoint used to connect to an existing browser instead of launching a new headless 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
ResponsivenessNo issues