From the terminalNeeds a repository

Hand off from your terminal

A run you pick up later

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

View .md

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

From the terminal

$ rush run claude -r acme/web --keep "Set up the dev environment and get the e2e tests passing"
Fig. The command. The rush CLI sends the same request the API takes.

Watch it work, then read what comes back

GET /o/{org}/sessions/{session}/events
event: tool_usebash · bun install
event: tool_usebash · bun run test:e2e
event: tool_result3 failed, 41 passed
event: messageTwo failures were a missing env var; one is a real bug.
Fig. The live stream while it works. Event names are the stream's.
GET /o/{org}/sessions/{session}
status
paused
result
41 of 44 e2e tests pass; one real bug found
Fig. The session when it ends. Field names are the API's.

Steps

  1. 01

    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. 02

    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. 03

    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.

In the API and the docs

POSTSend a follow-upGETGet one sessionConceptRuns and sessionsConceptWatch and steer

Related

All use cases
From the console

Steer a run as a team

One run, many hands

A teammate starts a run; everyone in the org can read it as it works, and its starter or an org admin steers it with follow-ups or by taking control of its browser.

Open the recipe