Repository navigation
Dashboard and Security
Svwergio_mel edited this page Nov 12, 2026
·
3 revisions
URL: http://127.0.0.1:8765/dashboard/ (static build from chat-export-dashboard).
| Section | Purpose |
|---|---|
| Overview | Server health, MCP tool stats, resource use |
| Browsers | Connected profiles, ceb_ enrollment |
| Queues | Job lanes (queued, running, done, …) |
| Cache | Temp chat cache entries |
| Logs | Tail of server.log with level filter |
Admin login uses a server-side session (not your cem_ MCP key). Configure credentials via server env / config — see server SECURITY.md.
Themes: dark/light/auto and eight provider skins (ChatGPT, Grok, Grok-X, Copilot, Claude, Qwen, DeepSeek, Perplexity — match extension popup).
| Asset | Scope |
|---|---|
cem_* |
MCP API on localhost only |
ceb_* |
One browser profile gateway |
| Chat content | Stays in your browser + ~/.chat-export exports/DB |
| Delete | Off unless allowDestructive + confirm: true
|
No telemetry, no cloud relay. Audit log appends MCP/RPC events locally (audit.log).
- Keep
keys.jsonmode600; rotate keys after sharing a machine. - Do not expose port
8765beyond loopback. - Review Dependabot PRs (notably zod 3→4 for MCP SDK).
- Read module
SECURITY.mdin each repo.
Detailed threat notes: server SECURITY.md.
To protect users from accidental account flags on provider platforms, the stack separates consent into two explicit tiers (see LEGAL.md in each repository):
- Tier 1 — General Legal / Account Ban Risk ToS: Required for baseline extension use (manual DOM/API chat export). Clarifies that the software is provided "as is" and that automated or bulk export may violate provider Terms of Service.
-
Tier 2 — Advanced MCP Mode ToS: Required before activating the WebSocket server bridge (
serverOn) or enabling MCP automation gates (allowCreate,allowProjects,allowDestructive). Warns that programmatic prompting (chat_ask,chats_send) and batch operations run through your live browser session and carry elevated account suspension risk.
-
Native, Docker, and Kubernetes Deployment — macOS
launchd, Linuxsystemd --user, Windows Task Scheduler / NSSM / PM2, Docker/Colima, and Kubernetes (deploy/k8s+ loopback port-forward). - Optional use case: local LLM + Bonsai-27B — example of driving the eight web providers from an external local MCP client.
- Verified listings: MCP Servers (
mcpservers.org) and Glama (svergio/chat-export-server).