gsd-debug

Systematic debugging with persistent state preserves symptoms, hypotheses, and evidence across context resets by using dedicated subagents to manage checkpoints and continuations, preventing context bleed during root-cause analysis.

Root-cause analysis and fault diagnosis are orchestrated by coordinating subagents for session management, status checks, and continuation or diagnose paths, enforcing sandboxing and structured reporting to safely hand off to specialist tools.

Yes, listing, status checks, and continuing sessions are supported through a session-manager loop, allowing you to resume persistent debugging contexts and pick up exactly where the previous fault diagnosis left off.

To start systematic debugging, describe the bug you want to investigate to create a new session, which initiates the session-manager loop to guide context isolation, evidence collection, and structured root-cause reporting.

Agent orchestration enforces sandboxing and structured root-cause reporting to ensure safe handoffs to specialist tools, isolating the debugging environment and preventing context bleed across coordinated subagents.

Context bleed happens when prolonged debugging sessions lose track of original constraints, but it is isolated here through dedicated session-manager subagents that enforce context isolation and maintain persistent state across resets.