Skip to content

Pick up where it left off

This page reopens a Claude Code conversation after its sandbox has stopped, with the files and conversation history it had.

  1. Choose a past conversation on this repo.

    Terminal window
    cd ~/src/my-repo
    droneship resume claude

    Claude opens with a list of your past conversations on this repo. If no sandbox is running for this repo, the CLI starts one on your saved workspace first:

    No claude sandbox is running; starting one on your saved workspace for https://github.com/you/my-repo to resume in.

  2. Or go straight to one conversation.

    Terminal window
    droneship resume claude <session>

    Use the session id Claude printed when it exited.

  3. Continue a stopped task.

    Terminal window
    droneship list -a
    droneship resume claude <id>
    Using your ANTHROPIC_API_KEY (BYOK); --sub uses your plan instead.
    Restoring <id> from its snapshot...
    Restored as <new-id>

    The run’s own key was never kept, so resume sends your exported key again. To use your plan instead, add --sub. With neither, it uses the key you saved in the console (Using your saved Anthropic key). With none of these, resume stops before anything starts.

    Claude opens in the task’s conversation, in a sandbox restored from the task’s snapshot. Reply to its question, or continue the work yourself.

What you’ll see in the console

Section titled “What you’ll see in the console”

A stopped task whose snapshot is still kept has a Resume button on the Sandboxes and Tasks pages and on its own page. It restores the task into a new sandbox and takes you to that sandbox’s page. To reopen the conversation itself, use droneship resume claude <id> from your terminal. A task that can’t be restored says why: snapshot expired or sandbox lost.

What’s kept

Section titled “What’s kept”
  • Your interactive sandbox: when it stops, its workspace is saved, including Claude’s conversations. That is what droneship resume claude reads. The workspace lasts until you run droneship workspace delete or launch with --fresh. Core concepts lists what it keeps.
  • A task: it doesn’t use your workspace. Its sandbox is snapshotted when it stops, and droneship list -a keeps it for 7 days. A restore keeps the task’s egress bundle, isolation and time limit, and uses the project’s egress rules as they are when you restore.

Credentials aren’t saved with either. A task’s own --byok key isn’t kept, so pass --byok again on resume to bill with your key, or --sub to use your Claude plan.

Inside Claude, /resume opens the same list of past conversations.

More: Auto-stop and resume, Workspaces, droneship resume.

Next

Section titled “Next”