Configuration

Dashcat Agent and Dashcat Bridge keep their files in one directory per user. Files holding keys, trust decisions or activity are created readable by the current user only (0600 on Unix; on Windows the user profile’s ACL applies).

OS	Directory
Linux	$XDG_CONFIG_HOME/dashcat/, default ~/.config/dashcat/
macOS	~/Library/Application Support/dashcat/
Windows	%APPDATA%\dashcat\

File	Owner	Contents
agent.toml	agent	Settings: listen = "0.0.0.0:7420", and hosted = "allow" or "deny": whether the Dashcat connector may reach this node (set by dashcat-agent join). paused = true while Pause remote access is on in the tray
agent-account.toml	agent	The Dashcat account this node joined, and the account’s connector key when hosted = "allow"
agent-identity.key	agent	The agent’s private key
agent-trusted.toml	agent	Paired bridges and their permissions, and the Dashcat connector’s
agent-pairing.toml	agent	The active pairing code, if any (deleted when used or expired)
agent-activity.log	agent	The activity log; agent-activity.1.log holds older entries
nodes.toml	bridge	Paired nodes: address and pinned fingerprint
bridge-identity.key	bridge	The bridge’s private key

Deleting an identity key gives that machine a new identity: every pairing with it must be redone.

Environment variable	Effect
DASHCAT_AGENT_CONFIG	Agent config path (same as dashcat-agent --config); the agent’s other files live beside it. Login sessions don’t see it, so dashcat-agent autostart enable records the path as --config.
DASHCAT_AGENT_NO_TRAY	Set to true to run the agent without a tray icon (same as serve --no-tray)
DASHCAT_NODES	Node registry path (same as dashcat-bridge --nodes); the bridge key lives beside it
DASHCAT_PAIRING_CODE	Code for dashcat-bridge nodes add when --code is omitted
RUST_LOG	Log level, e.g. debug. Agent default info, bridge default warn. Logs go to stderr.