Problem
When running multiple Claude Code sessions across different projects simultaneously, there's no quick way to see what tools (MCPs, Skills, Hooks) are active for the project you're currently working in. You have to switch to CCTM, find the project manually, and check — breaking your flow.
Proposed Feature
A secondary dashboard window designed to sit on a second monitor and stay visible while you work. It watches the system's active (foreground) window, detects when a Claude Code session is in focus, reads the working directory of that session, and instantly shows the full effective configuration for that project — across all levels that apply to it:
- Active MCPs
- Skills
- Hooks
- Commands
- Sub-Agents
- Any other useful project information
Crucially, the dashboard should distinguish between global and project-level configuration. A project is affected by both its own local settings and the global ones — the dashboard should make that clear, either through visual separation (e.g. two sections or tabs: Global / Project) or color coding, so you can tell at a glance where each item comes from.
When you switch to a different Claude Code window in a different folder, the dashboard updates automatically.
Behavior Detail
- Dashboard polls or listens for foreground window changes
- When the active window is a terminal running Claude Code, it reads the working directory
- It matches that path to a known project in CCTM's config
- It displays the full effective configuration in a compact read-only view, grouped by scope (global vs. project-level)
- If the active window is not a Claude Code session, it either holds the last state or shows a "no active project" placeholder
Out of Scope (for v1)
- Toggling tools on/off from the dashboard (view-only is fine to start)
- Non-Claude Code editors
Platform
Windows 11 (primary), but the concept applies to macOS too.
This feature request was ideated by a human user and written with the assistance of Claude Code.
Problem
When running multiple Claude Code sessions across different projects simultaneously, there's no quick way to see what tools (MCPs, Skills, Hooks) are active for the project you're currently working in. You have to switch to CCTM, find the project manually, and check — breaking your flow.
Proposed Feature
A secondary dashboard window designed to sit on a second monitor and stay visible while you work. It watches the system's active (foreground) window, detects when a Claude Code session is in focus, reads the working directory of that session, and instantly shows the full effective configuration for that project — across all levels that apply to it:
Crucially, the dashboard should distinguish between global and project-level configuration. A project is affected by both its own local settings and the global ones — the dashboard should make that clear, either through visual separation (e.g. two sections or tabs: Global / Project) or color coding, so you can tell at a glance where each item comes from.
When you switch to a different Claude Code window in a different folder, the dashboard updates automatically.
Behavior Detail
Out of Scope (for v1)
Platform
Windows 11 (primary), but the concept applies to macOS too.
This feature request was ideated by a human user and written with the assistance of Claude Code.