Skip to content

docs(maka-cli): clarify waits for idle and busy sessions #6213

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
me2seeks merged 2 commits into from
Oct 21, 2026
Merged

docs(maka-cli): clarify waits for idle and busy sessions #6213

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6ea7a28
docs(maka-cli): clarify waits for idle and busy sessions
me2seeks Oct 21, 2026
4bd264e
docs(maka-cli): show busy session statuses and wait sequence
me2seeks Oct 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 11 additions & 2 deletions skills/maka-cli/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,13 +55,22 @@ Wait when ready for the next interaction or result; avoid repeated status pollin
```sh
maka run --session "$session" --status
maka run --session "$session" --recap --json
maka run --session "$session" "Inspect the tests next" --no-wait
maka run --session "$session" "Inspect the tests next" --json
maka run --session "$session" "Focus on the parser" --steer --no-wait
```

Status returns lifecycle and pending interactions; `--status --recap` returns both state/boundary and progress as JSON. If installed help advertises `--recap`, use it to summarize recorded progress during execution. Each recap calls the model independently and can lag execution; it is neither final output nor a direct worker reply. Portable `session-export` is not a progress query.

An added prompt queues by default; `--queue` is optional. `submission` confirms admission, while `status` describes the observed Session, possibly an earlier Turn. Service current questions/approvals before expecting queued work to execute. Status and admission receipts already return JSON; use `--json` on waits/results/recaps to keep their output structured.
For an idle Session, send the next prompt and wait as above; `--no-wait` is only needed when intentionally detaching. A busy Session has status `running`, `needs_input`, or `needs_approval`. Submit its follow-up with `--no-wait`, then use Session-only waits to handle the current Turn's questions/approvals before queued work can execute:

```sh
maka run --session "$session" "Inspect the tests next" --no-wait
maka run --session "$session" --wait --json
```

Waiting on the new prompt does not return an earlier Turn's interactions.

An added prompt queues by default; `--queue` is optional. `submission` confirms admission, while `status` describes the observed Session, possibly an earlier Turn. Status and admission receipts already return JSON; use `--json` on waits/results/recaps to keep their output structured.

## Handle decisions and interruption

Expand Down
2 changes: 1 addition & 1 deletion skills/maka-cli/references/session-control.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ Permission requests, MCP forms, and other unsupported kinds remain waiting when

## Queue, steering, and Inbox

For coordination, submit a follow-up with `--no-wait`, then use Session-only wait/answer calls. Each queued message gets its own later Turn. Omit `--no-wait` and use `--json` only when following that message's exact result while separately servicing earlier Turns: that wait does not return an earlier Turn's AskUser and can leave the queue blocked.
If the Session is idle, send the next prompt with `--json` and wait for its result or interaction. If it is busy (`running`, `needs_input`, or `needs_approval`), submit a follow-up with `--no-wait`, then use Session-only wait/answer calls to service the current Turn. Each queued message gets its own later Turn. Waiting on a follow-up selects that message's result and does not return an earlier Turn's AskUser, so it can leave the queue blocked.

Steering is delivered at Host execution boundaries and can carry over if it misses the current Turn. Admission does not prove consumption. Steer with `--wait` observes the Turn selected on attachment. `--result` reads the latest Turn, not an arbitrary previous assignment.

Expand Down