AI Productivity

Recover a Team Member Onto Its Worktree

A stopped team writer can come back on the same dedicated worktree it was already using. Closing a seat no longer forces its replacement into the project root or a brand-new checkout, so dirty, allowed changes stay where they were — and the replacement inherits the transcript of the seat it took over from.

Screenshot coming soon

Why You Need This

How this feature boosts your daily productivity

Losing a seat should not mean losing the seat's work. When a replacement landed in the project root or a fresh checkout, any work in progress in the original's dedicated worktree was suddenly somewhere the new agent was not looking — doing exactly what you asked, in a directory nobody was reading. Recovery now keeps the checkout. From the team host, team capabilities reports what recovery can actually do before you rely on it, and team recover brings the member back with its transcript handed over so it knows what the previous seat had established. Pointing a new terminal team member at an existing worktree keeps that worktree rather than recreating it, and a path that does not exist is refused instead of being silently replaced with a fresh one.

How It Works

Get started in 4 simple steps

1
1

Ask what recovery can do

From the team host, team capabilities reports what recovery supports for this team before you rely on it.

2
2

Recover the member

team recover --team --member --expected-run --client-request-id brings the seat back, optionally on a different agent or model.

3
3

Keep the checkout

The replacement lands on the same dedicated worktree the stopped writer was using, so dirty, allowed changes stay where they were.

4
4

Inherit the transcript

The replacement receives the previous seat's transcript, so it knows what was already established instead of starting cold.

5
5

Reuse a worktree deliberately

Point a new terminal team member at an existing worktree and it is kept, not recreated. A missing path is refused rather than silently replaced.

Without 1DevTool

The manual way vs. the 1DevTool way

The Hard Way

# a team writer stops
# its replacement lands in the project root
# or in a brand-new checkout
# the worktree with the real work is untouched
# and nobody is looking at it
# re-explain everything to the new seat

The 1DevTool Way

team capabilities -- what recovery can do
team recover -- the seat comes back
Same dedicated worktree, changes intact
Transcript handed to the replacement
A missing path is refused, not replaced

Key Capabilities

Everything included with Recover a Team Member Onto Its Worktree

Bring a stopped team writer back into its seat
Keep the member's dedicated worktree instead of a new checkout
Preserve dirty, allowed changes across the replacement
Hand the previous seat's transcript to its replacement
Ask team capabilities what recovery supports first
Recover onto a different agent or model when you want
Reuse an existing worktree for a new team member
Refuse a missing worktree path instead of replacing it silently

Why It Matters

The productivity impact of having ai productivity built into your workspace

Searchable Prompt Library

Every prompt you've ever sent is captured and searchable. Find and reuse your best AI interactions.

Visual AI Communication

Annotate screenshots and embed them in prompts. Show your AI agent exactly what you see.

Session Knowledge Base

AI conversations become searchable history. Find how you solved a similar problem last week.

Power Navigation

Command palette gives you instant access to any feature. Navigate 1DevTool at the speed of thought.

Ready to boost your workflow?

Download 1DevTool for free and experience Recover a Team Member Onto Its Worktree along with 287 other features — all in one app.