The --debug Flag
If the workstation isn't starting correctly, run it with the --debug flag to see detailed diagnostic output:
npx ticket-house --debugWhat It Shows
Debug mode outputs information about each step of the startup process:
- Configuration loading — which
.ticket-house.jsonwas found and its parsed contents - Git state — the repository root, current branch, and remote URL
- Server connection — attempts to connect to the remote server and any authentication steps
- Worktree discovery — existing worktrees found in
.ticket-house/worktrees/ - Container pool — if containers are configured, the state of the pool (images, running containers, idle slots)
- MCP server — whether the MCP server started and on which port
- HTTP server — the local HTTP server address and port
Reading the Output
Each line is prefixed with a timestamp and a subsystem label (e.g., [config], [git], [server]). Look for lines marked [error] or [warn] to find problems.
Common issues visible in debug output:
- Config not found — no
.ticket-house.jsonin the repository root - Connection refused — the remote server URL is unreachable
- Port in use — another process is using port 3412
- Auth failure — the session cookie is expired or invalid