UniloomDocs
Use Uniloom

Your terminal and Uniloom

A session can move between your own terminal and Uniloom. Continue a terminal session here when you want Uniloom's panel and tabs around it; hand one back when you want it in your terminal again.

Continue a session from your terminal#

Click the session's row. Uniloom shows its conversation, live, read from its transcript, with its details in the side panel. Nothing on that screen types into your terminal. One button above the conversation says what continuing it would do:

SessionButtonWhat happens
A Claude Code background job, or a Cursor persist sessionOpen in UniloomThe session itself opens in Uniloom. Nothing is copied or interrupted
Claude Code in a terminal, Codex, OpenCodeContinue in a copyUniloom starts a second conversation with the whole history. The original keeps running where it is
Cursor, GeminiMove hereThe original ends first, then the session continues here. Click twice, because a turn in progress is lost

A copy has its own transcript, so the two never mix. Its row says Copy in Uniloom. The original's row offers Open your copy to read or stop it. Uniloom uses the session's own account, so the copy finds the same conversation.

Hand a session back to your terminal#

Hand back to my terminal, in a row's ⋯ menu, detaches a Claude Code session that Uniloom runs and leaves it running. Only Claude Code can do this.

  1. Uniloom sends Claude Code its detach input and closes the session's terminal in Uniloom.
  2. A message, Handed back to your terminal, gives the command to attach to it again, such as claude attach <handle>, with Copy resume command.
  3. If Uniloom cannot name the command, the message says It keeps running in the background.

Run the command in any terminal to pick the session up.

Last updated