session-start-check

To prevent merge conflicts during parallel Claude coding sessions, run a session-start-check to detect recent overlapping code-path edits. This passive alert warns you early if another concurrent session has touched the same files, reducing duplicated effort.

Concurrent session coordination for Laravel modules works by calling the whats-active MCP tool to check recent developer activity. It performs a path-overlap comparison against your intended files and issues a brief warning only if another session recently modified the same code paths.

Yes, you need to call the whats-active MCP tool to check for code overlap between sessions. It queries recent active sessions within default time windows, allowing the system to perform path-overlap comparisons and decide whether to emit a passive coordination alert.

You should skip session overlap warnings during very short sessions, when the MCP tool is unavailable, or when explicitly instructed to ignore checks during debugging. The system also avoids repeated tool calls within the same session to maintain operational safety.

Yes, you can use session-start-check for Tier-1 parallelism scenarios defined in ADR 0119 within the oimpresso project. It is designed to run after brief-fetch for any agent or human session to coordinate overlapping code paths.

The best way to avoid duplicated work with AI-driven coding agents is to passively alert developers about overlapping code paths at session start. By comparing intended file modifications with recent concurrent session activity, it prevents duplicated effort before it happens.