What problem does it solve? Sessions started outside the AI Agents Orchestrator dashboard (for example via claude --resume) are invisible to it: they have no notes.md, no category folder, and no entry in active-sessions.json, so the dashboard cannot track their status or preserve their context. ## Core Features & Use Cases - Session adoption: Resolves the current terminal's session ID by walking the process ancestry against ~/.claude/sessions/*.json, then binds it to a notes.md under the chosen category folder. - Collision guard: Detects when the terminal is already bound to a different workspace and asks before re-binding, preventing silent detachment of active sessions. - Registry integration: Writes a structured notes.md (goal, branch, decisions, session history) and registers the session in ~/.claude/active-sessions.json so the dashboard shows it as Running. - Use Case: After resuming an old conversation with claude --resume <id>, run /import-session FEAT payment-retry to bring that session under dashboard management without creating a fresh workspace or touching git. ## Quick Start Ask the assistant to run /import-session with a category and short name, for example: import this current session into the FEAT category as payment-retry.
