Developer settings

The MCP pane with the token shown.

Caution

Preferences, Developer is for troubleshooting and advanced users. Most people never need it, and Reset deletes all your data. When you report a problem, support may ask you to copy something from here.

Network

Every HTTP and WebSocket request the app makes, filterable and searchable. Useful when a connection will not come up.

Control	What it does	Default	Notes
HTTP / WS → / WS ← / WS state chips	Show or hide requests by kind: HTTP, outgoing WebSocket frames, incoming frames, WebSocket connection state.	all shown
Method filter	Hide or show individual HTTP methods; Show all / Hide all.	all shown
Filter - method, URL, topic, body…	Text search over the list.	empty
Row details (click a row)	Shows the request and response. copy copies a section; copy as cURL builds a command; close shuts the drawer.	closed	Secrets are redacted in the log (see redact.ts), but check before pasting anywhere.
Clear	Deletes the recorded requests after a confirmation.	n/a

Logs

The live application log stream.

Control	What it does	Default	Notes
Minimum level	Most detailed level written to the log database: error, warn, info, debug, trace.	info in an installed app, debug in a development run (the LOG_LEVEL environment variable overrides)	Lower levels are not recorded at all. More detail can slow the app (the row warns).
Level chips (trace, debug, info, warn, error)	Hide or show stored entries by level.	all on except trace	Display filter only.
Process and Categories filters	Hide or show log entries by process or by category; Show all / Hide all.	all shown
Filter - message, category, process…	Text search.	empty
Jump to live	Resumes following new entries after you scrolled up.	n/a
Copy all	Copies the log to the clipboard.	n/a	May contain personal details. Review first.
Clear	Deletes stored log entries after a confirmation.	n/a

MCP

Heading “MCP Server”. Credentials for the local MCP server, which lets outside tools (such as Claude Code or Cursor) drive TeamHUD on this machine. Anyone with a token can act within its scopes, so treat tokens like passwords.

Control	What it does	Default	Notes
Server URL	Address the MCP server listens on. Copy.	n/a
Admin token	Token for external clients. Reveal/Hide, Copy, Regenerate.	generated	Regenerating invalidates the old one.
.mcp.json snippet	Ready-made config for an external client. Copy snippet.	n/a
Scope chips (on each token)	Click to grant or deny a scope.	admin token has all	Scopes: all, quest-log, window-activity, overlay, widgets, pipelines, teams, audio, development, logs. all grants everything.
Require auth, advanced	Require a Bearer token on every request.	On	Turning it off removes that protection. Leave on.
Second HTTP port, advanced	Extra listener on its own port. Still needs a token unless auth is off.	Off
HTTP port, advanced	Port for the second listener (also MCP_SERVER_HTTP_PORT).	28080 unless the build says otherwise	Shown when the second port is on.
HTTP URL, advanced	The second listener’s address. Copy.	n/a
ai-chat-internal token, advanced	Token the built-in AI chat uses. Reveal, Copy, Regenerate.	generated
Custom tokens: token name, scopes, optional expiry date, Create token	Make a named token limited to chosen scopes, optionally expiring. Each existing one has Reveal, Copy, Regenerate, Delete.	new token preselects logs; no expiry	Create is disabled without a name and at least one scope.

Performance

Rolling health of the main process. Event-loop delay is the figure that matters: overlay cursor tracking runs on it, so a stall shows up as laggy hover.

Control	What it does	Default	Notes
Refresh	Re-reads the numbers.	n/a
Reset	Discards the history and measures from now.	n/a
Copy report	Copies a report for support.	n/a
Status banner	One line saying whether health is OK, with the reason.	n/a
Event loop table	Delay (mean), Delay (p99), Worst stall, with Last / Mean / Worst columns.	n/a
Resource detail, Hardware (collapsed)	CPU, per-process, rendering, memory, sampler, GPU and system detail.	collapsed	Read-only.

Reset

Control	What it does	Default	Notes
Erase all data & restart (under Danger zone)	Permanently deletes everything this TeamHUD instance has stored on disk, then restarts it fresh: appearance, profiles, connected accounts and sign-in tokens, widget preferences and layouts, plugin settings, search index, logs and cached data.	n/a	Cannot be undone. A confirmation asks “Erase all TeamHUD data?” first; confirm with Erase all data. You will need to reconfigure and reconnect everything.