Docs
GitHubBlog

Search Documentation

Search for a page in the docs

Lifecycle & Offboarding

Removing a Workspace from daily use is not a blind directory delete. OpenAlice treats it like offboarding a desk and its coworkers: inspect active work, write a handoff, move the complete checkout out of the active floor, and retain enough history to explain old reports later.

Active and departed desks

<OPENALICE_HOME>/workspaces/
├── workspaces.json
├── workspaces/                 # active checkouts only
├── departed-workspaces/        # retained offboarded checkouts
└── state/
    ├── workspace-catalog.json
    ├── resume-identities.json
    ├── headless-tasks.json
    └── artifact-provenance.json

workspaces.json answers “what can Alice run now?” The catalog records everything that has existed, where it went, and whether it can be restored. Workspace ids are never reused.

Offboarding

Before a Workspace departs, OpenAlice inventories:

  • live headless runs;
  • interactive Sessions and their signatures;
  • open and scheduled Issues;
  • the current git branch, dirty state, and changed paths.

A live headless run is a hard blocker. Dirty files and open Issues are not: the complete checkout moves intact and the handoff records them.

OpenAlice writes two artifacts inside the Workspace before moving it:

  • .alice/HANDOFF.md — readable reason, notes, signatures, Issues, and uncommitted paths;
  • .alice/offboarding.json — the same transition snapshot in a stable structured form.

It then moves the checkout to departed-workspaces/<workspaceId>, removes it from the active registry, and retires its Session identities. Scheduled scanning sees active Workspaces only, so local schedules stop after departure.

Restore versus purge

Restore returns the exact checkout to its original active path and recalls the same resumeId values and runtime mappings. Returning to the same path matters because agent trust stores and native conversation discovery may be cwd-dependent.

Purge is separate and irreversible. It removes the departed checkout, interactive Session records, and terminal scrollback. It deliberately retains the catalog tombstone, retired signatures, headless run history, Inbox entries, and artifact provenance. An old report therefore resolves to a known retired or purged author instead of an unexplained missing id.

Session retirement and handoff

Pausing or closing one terminal tab does not retire a Session. Offboarding retires every Session identity owned by the Workspace. A retired Session cannot resume or run a schedule, but its attribution remains valid.

An explicit successor may be recorded for handoff. The successor is a new coworker, not a rewrite of historical authorship: old work stays signed by the original @resumeId.

In the Web UI

The Workspaces page separates active and departed inventories. Offboarding shows blockers and the handoff snapshot before confirmation. Departed entries can be restored or purged; purge is available only after offboarding.

Next Steps