docs: add request_next_turn to turn-loop.md (follow-up to c99261b)
This commit is contained in:
parent
4a27ef7304
commit
96f93f3b5e
1 changed files with 6 additions and 0 deletions
|
|
@ -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.
|
scheduling a new one fails if the cap is already hit.
|
||||||
- `whoami()` — `{ name, role, pronouns, hyperhive_rev }` for
|
- `whoami()` — `{ name, role, pronouns, hyperhive_rev }` for
|
||||||
self-identification without scraping the system prompt.
|
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
|
### Waking the agent from inside the container
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue