Read the Session list, then answer, start, stop, or close a Session.

Machine, Project, Session

Read the list and its states

Open Session 清單 (Sessions). The header counts rows, for example 2 個在跑 (2 working). Rows that wait for you move to the top.

Press / to filter by task, project, or terminal. A Session started by another one is shown under it, marked └.

Answer and send

• A question: a card above the message box lists the options. Tap one; it reaches the Session as key presses.
• Text: type and press Return or 送出 (Send). ShiftReturn starts a new line. On a touch screen, send with the button.
• Pictures: press 附一張圖 (+, attach a picture), paste, or drag one in. Tap it to circle what to change with 紅筆 (red pen).
• Snippets: 常用句 fills the box with saved text; you still send it.
• Skills: type / (or $ for Codex) as the whole message to list the Session's skills and commands.
• Dictation: press 用說的寫一則訊息 (dictate), speak, press 停下來，轉成文字 (stop and transcribe). The machine transcribes with its own whisper-cli; the page must be 127.0.0.1 or HTTPS.

Expected result: your message appears in the transcript and the row goes back to working.

Reuse Playbooks and Snippets

Open Playbook to create a named launch message. In an existing Session, open the Playbook tab, choose the message and press Start Playbook. Edit or delete the saved definition on the Playbook page. A Snippet fills the composer; you review and send it yourself.

Let an Agent manage Playbooks

On a machine updated to a build with the Playbook CLI, an Agent in any Project can list, create, edit and delete saved definitions. Read the installed build's instructions first:

clawdline guide project
clawdline playbook list --session <terminal-id>
clawdline playbook create --project <returned-project-key> --body-file create.json
clawdline playbook edit --body-file edit.json <id>
clawdline playbook delete <id>

The create file contains title and body; the edit file contains only fields to change. Use the Project key returned by the list, including from a worktree. Use --global instead of --project for all Projects. For a custom message in a linked Playbook, include source: null to remove the link. Saving a definition does not send it.

The CLI reads credentials privately and prints the write's Idempotency-Key. After an uncertain result, reuse it with --key and the same content. HTTP clients use /v1/snippets with scope: "playbook"; see the API contract for fields, authentication, refusals and retry rules.

Read an Agent's attention note

An Agent can leave a concrete request above the Session conversation when it needs you to read, answer, or act. Open 關注 (attention) in the Session header when it shows a red dot. The note says what you need to do and why. If it offers choices, tapping one of multiple suggested replies sends that message to the Session; the note clears after the send is accepted. With one suggestion or none, the button fills the message box for you to edit and 送出 (Send) yourself. Use 移到已處理 (handled) only when you have handled it another way: that button sends no message and grants no approval.

Expected result: the red dot clears when no open notes remain. A note alone sends no push notification. A blocked Agent should also mark its Session as waiting and send an attention notification. Board decisions with deadlines stay on their Board card.

Start a Session

1. Press 開一個 session (Start a session) in the list header.
2. Under 要在哪裡開？ (Where), choose a project folder.
3. Under 要用哪一個開？ (With), choose Claude Code or Codex, or 接續之前的 (pick up an earlier conversation).

Expected result: 開好了。等它出現⋯ (Started, waiting for it), then a new row. With several Machines on Cloud, 機器 (Machine) chooses where it runs.

To set the default for new Codex Sessions, open 設定 (Settings) → 新 session 的預設設定 (Defaults for new sessions) → Codex 預設推理強度 (Codex reasoning effort): high, xhigh, or 由助理決定 (assistant decides). It applies only when nothing else chose an effort.

Stop and close

To stop the current turn, open the Session's ⋯ menu and choose 停止目前的工作（Esc）. It sends Esc; the conversation stays open.

To close it, choose ⋯ → 關閉 session, or swipe the row left on a phone. The dialog first says whether closing is safe:

Archive and bring back

Archiving ends a Session's process to free memory and keeps its conversation. On a touch screen, swipe the row left, choose 封存 (Archive), and confirm. To bring it back, open 封存 in the menu and press 叫回 (Bring back): it reopens in the same folder with the same assistant.

Documents

Choose ⋯ → 文件 (Documents) to read the Markdown and text documents of that Session. 分享 (Share) or 複製連結 (Copy link) gives a link to one.

Turn reports

A Session can leave one HTML page at the end of a turn: status cards, the changed files, and each commit's diff.

clawdline report --status status.md --open <commit>…

It prints a file:// address and, for a report in the state directory, http://127.0.0.1:7727/reports/<id>. Reports open on this machine only, never through Cloud.

Usage and quota

• ⋯ → Session 資訊 (Session info) shows context use, tokens, and plan limits when the assistant reports them.
• clawdline usage --session <id> lists what a Session spent, by category. clawdline assistants shows each assistant's quota and when it resets.
• Claude's 5h and 7d percentages need a Claude Code status line that writes ~/.claude/statusline-cache/rate-limits.json. Without one, the console shows plan limits as unknown. Codex needs nothing.

Keyboard shortcuts

See the keyboard shortcuts cheat sheet for navigation, common actions, Session controls, and message editing, with Mac and Windows/Linux keys.