Continue a terminal session in a task
Started Claude Code or Codex in a terminal and want to carry on in uuBright Console? A new task can pick up that conversation, with its history, and keep working on it.
#When it works
The task has to run on the computer that holds the session:
- in the desktop app, This Mac;
- a server in host mode, for sessions you started on that server.
A session on your Mac can't be continued from a remote Linux host's console, and a session on the Linux host can't be continued from This Mac. Tasks that run in Docker containers can't see your sessions either.
#Continue a session
- End the session in the terminal first: type
/exit, or press Ctrl-C. - In the desktop app, open This Mac, then select New task.
- In Project, pick the project whose folder is the one you ran
claude(orcodex) in. Sessions from the project's Git worktrees count too. - Open Continue a session….
- Pick the session. The list shows the 30 newest, each with what it was about, the agent, how many messages it has and when it last changed.
- Write a first message if you like. It's optional: the task can start from the history alone.
- Start the task.
Picking a session sets the task's Agent to match it. To go back, pick Start a new conversation.
#What happens
The task continues a copy of the session in its own worktree:
- Claude Code starts with
--resume <id> --fork-session, so the continued conversation gets a new session ID. - Codex forks the thread with
thread/fork. See Codex host tasks.
The original stays as it was. You can still resume it in the terminal later.
A session marked may still be open changed in the last two minutes, so it's probably still running somewhere. You can continue it, but what happens there from now on won't reach the task. That's why you end the terminal session first.
The task works in its own worktree, not in the folder you ran the CLI in. Commit and push from the task, then pull the branch where you need it.
#Privacy
The list reads only the summary of each session. Nothing is moved or edited, and session contents aren't sent to your browser or phone.
#Troubleshooting
The list is empty. The list says why when it can. Otherwise check:
- You picked the right project. The session must have run in the project's folder or one of its Git worktrees.
- Where your sessions are saved. uuBright Console looks in
~/.claude/projectsand~/.codex/sessions. If you setCLAUDE_CONFIG_DIRorCODEX_HOMEto a different location in your shell, uuBright Console must use the same setting. - The workspace uses the computer's agent login. A workspace with its own Claude Code or Codex login can't see sessions made with the computer's login. Continue from the Default workspace instead. See Workspaces.
- The project is a checkout on this computer, not one cloned from a URL for each task.
I can't continue a Claude Code session with Codex, or the other way round. Each agent can only resume its own conversations. The task's agent always follows the session you pick.
For more on starting tasks, see Run and control tasks.