# Hand off from your terminal

Returns: A run you pick up later. Starts: from the terminal.

Start a run from the rush CLI, close your laptop, and pick it up from the console or the CLI where it left off.

## Best for

- Engineers who start work locally and want it to keep going
- Long tasks you do not want to babysit

## Uses

- The rush CLI
- A connected GitHub repository

## The command

```bash
rush run claude -r acme/web --keep "Set up the dev environment and get the e2e tests passing"
```

## While it works

Live stream events (`GET /o/{org}/sessions/{session}/events`):

- `tool_use`: bash · bun install
- `tool_use`: bash · bun run test:e2e
- `tool_result`: 3 failed, 41 passed
- `message`: Two failures were a missing env var; one is a real bug.

## What comes back

- `status`: paused
- `result`: 41 of 44 e2e tests pass; one real bug found

## Steps

1. **Start it.** `rush run` with `--keep` keeps the sandbox, so you can write to it later. It follows the run live; `-d` prints the id and returns.
2. **Walk away.** The run keeps going in the cloud. When the turn ends, the sandbox parks with its disk and memory and costs nothing while parked.
3. **Pick it back up.** `rush logs <run>` picks the stream back up, `rush send <run> "…"` sends a follow-up and wakes it, and the console shows the same run.

Field names are the API's; the values are an example.