move-session

Migrate live coding agent sessions between Directors with verified handover and source deletion.

96|11|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/thefrederiksen/devthrottle --skill move-session-thefrederiksen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: move-session
Source: https://github.com/thefrederiksen/devthrottle/tree/main/.claude/skills/move-session
Command: npx skills add https://github.com/thefrederiksen/devthrottle --skill move-session-thefrederiksen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you need to empty or upgrade a DevThrottle Director, its running agent sessions block the shutdown. This Skill moves a live session to another Director or slot by writing a right-sized handover document, recreating the session on the same agent and model, verifying the target picked the work up, and only then deleting the original. ## Core Features & Use Cases - Verified handover workflow: Commissions a seven-heading handover document from the source session, spawns a same-agent/same-model target via the cc-devthrottle CLI, and gates deletion of the source on an un-bluffable verification of the target's pickup. - Move-or-close triage: Step 0 decides whether a session should be moved at all, closing finished or owner-blocked sessions for free instead of spending a fresh context window recreating them. - Self-move support: Handles the final session on a Director moving itself, including self-written handovers, target self-verification, and relaying late facts before flagging itself done. - Use Case: You are emptying a Director running seven sessions so it can be updated. The Skill moves each continuing session to the new Director, closes the finished ones, rolls up all owner-blocked questions into one list, and confirms the old Director is empty. ## Quick Start Ask the agent to move a session by saying "move this session to the new Director" and it will capture the session record, commission a handover, spawn and verify the target, then delete the source.

Frequently Asked Questions about move-session

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I move a coding agent session to another Director?▼

Capture the source session's record with cc-devthrottle session list, ask the source for a seven-heading handover document, spawn a target on the same agent and model with --director, verify the target read the document, then flag the source done with session done.

Does moving a session migrate the running process or transcript?▼

No. A move recreates the session from scratch with no transcript or memory; everything the target knows comes from one handover document you write. The original is deleted after the target demonstrably picks the work up.

When should I close a session instead of moving it?▼

Close it when the handover's next action says the work is finished or merged, or when the next action is just a question for the owner. Moving spends a whole fresh context window, so only sessions with continuing work are worth moving.

What happens if the target session fails verification?▼

Nothing is deleted. The source keeps running untouched, the failed target is deleted instead, and the handover document is fixed before retrying. Verification is the only gate on deleting the source.

Can I move a session if the source is unresponsive or out of context?▼

Yes, as a fallback use the Gateway's POST /handover endpoint with fromSessionId and toRepoPath. It produces a mechanical scrape of prompts, files, and commands without intent or decisions, so prefer an agent-written handover when possible.

Why does the moved session run on a different model than the source?▼

With --args omitted the target inherits the Director's default model, which is wrong when the source was not on the default. Verify by reading the target's terminal header, not the Gateway's currentModel field, and restart if they differ.