session-start-check

What problem does it solve?

Prevents avoidable merge conflicts and duplicated effort by passively alerting when another developer’s Claude session has recently touched overlapping code paths.

Core Features & Use Cases

• Session-aware coordination (non-blocking): Calls the MCP tool to check whether another session is active in the recent time window and raises a one-line overlap warning only when relevant.
• Targeted overlap heuristic: Compares the other session’s touched paths with the module/file you intend to modify, then either stays silent or emits a brief confirmation prompt.
• Operational safety guardrails: Skips checks for very short sessions, tool unavailability, or explicit instructions to ignore during debugging, and avoids repeated tool calls within the same session.

Quick Start

After running brief-fetch, ask your system to run session-start-check so it calls whats-active and issues a short overlap warning only if needed.