Skip to content

Continue sessions from other CLIs ​

A harness session is a conversation you had in a coding CLI outside Humanize. You can list these sessions per folder, read what was said, and continue one as a Humanize chat.

A Claude Code session is opened from the sidebar, continued in a chat, and answeredA Claude Code session is opened from the sidebar, continued in a chat, and answered

Continuing a session copies its files into a new chat. The original CLI files are never changed.

Supported sessions ​

Humanize lists a session when its CLI is installed on your machine, it ran in the folder you are looking at, and no Humanize chat or epic started it.

CLIListed and readContinued in a chat
Claude Code (claude)yesyes
Codex (codex)yesyes
Grok Build (grok)yesyes
Pi (pi)yesyes
Oh My Pi (omp)yesyes
Qwen Code (qwen)yesyes
Kimi Code (kimi)yesno
MiniMax Code (mcode)yesno
DeepSeek Harness (dsh)yesno
OpenCode (opencode)yesno
MiMo Code (mimo)yesno
Antigravity (agy)yesno

In the app ​

Show sessions in the sidebar ​

The list is off by default.

  1. Open Settings and select General.
  2. Under Harness sessions, tick List in sidebar.
  3. Click Save.

In Settings, General, List in sidebar is ticked and saved, and three sessions appear in the sidebarIn Settings, General, List in sidebar is ticked and saved, and three sessions appear in the sidebar

Sessions appear in the sidebar after the folder's chats. Each row shows your first message in italics and the CLI name. The sidebar lists up to 50 sessions per folder and refreshes every 15 seconds.

Read a session ​

Click a row to read the full session, including your messages, the agent's answers, tool calls, thinking, and any sub-agents it started. Because the session is read-only, there is no message box.

A Claude Code session open in the app, with the Continue in chat button under itA Claude Code session open in the app, with the Continue in chat button under it

Right-click a row to open its menu: Open, Copy first message, and Copy session ID.

The menu of a Codex session row in the sidebarThe menu of a Codex session row in the sidebar

Continue in chat ​

Click Continue in chat below the session. Humanize copies the session into a new chat in the same folder using the same CLI and last-used model. Type your next message as in any chat.

Once continued, the row moves from the harness session list to your chats.

If a CLI cannot be continued, the button is hidden and a note explains why.

An OpenCode session that can be read but not continuedAn OpenCode session that can be read but not continued

In the terminal ​

Enable the session list ​

  1. Type /settings general.
  2. Select Harness sessions, press enter, and pick on.
  3. Select Save.

The Harness sessions row of /settings general, with on and off to pick fromThe Harness sessions row of /settings general, with on and off to pick from

Resume a session ​

Type /resume in a chat. The list shows the current directory's chats followed by up to 200 harness sessions. Each session row ends with read-only: a copy goes on as a chat or read-only: cannot be continued in a chat.

The /resume list with one chat and three harness sessionsThe /resume list with one chat and three harness sessions

Select a session and press enter. Humanize copies it into a new chat, shows what was said, and waits for your input. Picking a session that cannot be continued only shows a refusal. You cannot preview a session or open a row menu in the terminal.

In the terminal, /resume lists the sessions, one is picked, and the chat goes onIn the terminal, /resume lists the sessions, one is picked, and the chat goes on

Good to know ​

  • The harness_sessions setting in ~/.hmz/settings.yaml applies to the whole machine, so toggling it in the app also toggles it in the terminal (see Settings). With the app switched to a remote daemon, the switch and the sessions are those of the daemon's machine. The terminal always lists this machine's sessions. There is no hmz CLI command for harness sessions; use the app or the terminal interface.
  • Each row is titled after your first line in the session. Sub-agent sessions started by another session are not listed on their own. Sessions that Codex archived are listed too.
  • You can continue a session once. To branch again, use Fork on the new chat (see Organise chats). If you delete the chat, the original session returns to the list.
  • If a session's log omits the model name, you cannot continue it and Humanize shows does not say the model it ran on. If the CLI deleted the session files, Humanize shows cannot be continued: its files are gone.

Open source on github.com/humanfia · RSS: blog · news