From 96f93f3b5e2a38a887da8387f26944dd9a337e0b Mon Sep 17 00:00:00 2001 From: lexis Date: Fri, 22 May 2026 21:44:53 +0200 Subject: [PATCH] docs: add request_next_turn to turn-loop.md (follow-up to c99261b) --- docs/turn-loop.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/turn-loop.md b/docs/turn-loop.md index e72df3b..19b7a25 100644 --- a/docs/turn-loop.md +++ b/docs/turn-loop.md @@ -216,6 +216,12 @@ it as a stdio child via `--mcp-config`. The hyperhive socket name is scheduling a new one fails if the cap is already hit. - `whoami()` — `{ name, role, pronouns, hyperhive_rev }` for self-identification without scraping the system prompt. +- `request_next_turn()` — ask the harness to start another turn + immediately after this one ends, even if the inbox is empty. Use for + multi-turn tasks (long builds, sequential steps) where you want to + continue without waiting for an external message. The next turn starts + with `from: "self"` and `body: "continue"`. No-op if new inbox + messages arrive before this turn ends. No args. ### Waking the agent from inside the container