crew

# crew - Crew Workspace Management

Manage persistent, human-guided workspaces in Gas Town.

## Overview

**Crew workspaces** are persistent developer environments within a rig. Unlike polecats
(ephemeral, autonomous workers), crew members are human-managed and long-lived.

| Aspect | Crew | Polecat |
|--------|------|---------|
| **Persistence** | Long-lived | Ephemeral |
| **Management** | Human-guided | Witness-managed |
| **Hook behavior** | Show, await confirm | Auto-execute |
| **Scope** | Flexible, multi-issue | Single issue |
| **Identity** | Named (dave, emma) | Auto-generated |

**Use crew when**: Interactive development with human oversight is needed.
**Use polecat when**: Autonomous parallel execution is needed.

---

## Quick Reference

```bash
# Lifecycle
gt crew add <name>                # Create workspace
gt crew start <name>              # Start session
gt crew stop <name>               # Stop session
gt crew remove <name>             # Delete workspace

# Workspace Management
gt crew pristine [<name>]         # Sync with remote
gt crew refresh <name>            # Context cycle with handoff
gt crew rename <old> <new>        # Rename workspace

# Status
gt crew list                      # List all crew
gt crew status [<name>]           # Detailed status
gt crew at <name>                 # Attach to session
```

---

## When to Use Crew vs Polecat

| Scenario | Use |
|----------|-----|
| Interactive development with human | Crew |
| Parallel autonomous execution | Polecat |
| Long-running project work | Crew |
| Single-issue batch processing | Polecat |
| Exploratory/research work | Crew |
| Epic wave execution | Polecat |

**Key difference**: Crew waits for human direction. Polecats auto-execute hooked work.

---

## Crew Behavior

Crew members operate under the Propulsion Principle but with human confirmation:

```
1. Check hook (gt hook)
2. If work hooked → Show human, await confirmation
3. If not hooked → Wait for human instructions
```

**Unlike