waking-another-session

To wake a running Claude Code session without spawning a new one, write a durable cross-session signal file that preserves handoff intent for the target session to read on its next turn. This directs the correct handoff path for sprint and phase coordination.

Cross-session signal file orchestration coordinates handoffs when one running Claude Code session needs another to react to state changes like slot allocation, merge approval, blocker escalation, or regression follow-up without losing context or starting a new session.

To trigger a cross-session handoff when direct operator input is unavailable, use the legacy paste-block and push-notification fallback path. This delivers the handoff signal to the target session when the default operator ping-pong path is not possible.

Yes, cross-session wakeups require a known remote-control session name, a writable status-board path, and support for the ping-pong default or paste-block and push-notification fallback to direct the correct handoff path for leadership coordination.

Yes, cross-session signaling coordinates merge approvals across multiple worktrees and phases. The durable signal file ensures the target leadership or phase lead session reacts to the state change on its next turn without losing existing context.

A session wakeup signal fails if the writable status-board path is missing, the remote-control session name is unknown, or the operator ping-pong and paste-block fallback paths are unsupported, preventing the target session from reading the handoff intent.