mirror of
https://github.com/openclaw/openclaw.git
synced 2026-05-06 16:20:43 +00:00
feat: add forked subagent context
This commit is contained in:
@@ -69,9 +69,11 @@ Primary goals:
|
||||
- Keep the tool surface hard to misuse: sub-agents do **not** get session tools by default.
|
||||
- Support configurable nesting depth for orchestrator patterns.
|
||||
|
||||
Cost note: each sub-agent has its **own** context and token usage. For heavy or repetitive
|
||||
tasks, set a cheaper model for sub-agents and keep your main agent on a higher-quality model.
|
||||
You can configure this via `agents.defaults.subagents.model` or per-agent overrides.
|
||||
Cost note: each sub-agent has its **own** context and token usage by default. For heavy or
|
||||
repetitive tasks, set a cheaper model for sub-agents and keep your main agent on a
|
||||
higher-quality model. You can configure this via `agents.defaults.subagents.model` or per-agent
|
||||
overrides. When a child genuinely needs the requester's current transcript, the agent can request
|
||||
`context: "fork"` on that one spawn.
|
||||
|
||||
## Tool
|
||||
|
||||
@@ -98,6 +100,10 @@ Tool params:
|
||||
- `mode: "session"` requires `thread: true`
|
||||
- `cleanup?` (`delete|keep`, default `keep`)
|
||||
- `sandbox?` (`inherit|require`, default `inherit`; `require` rejects spawn unless target child runtime is sandboxed)
|
||||
- `context?` (`isolated|fork`, default `isolated`; native sub-agents only)
|
||||
- `isolated` creates a clean child transcript and is the default.
|
||||
- `fork` branches the requester's current transcript into the child session so the child starts with the same conversation context.
|
||||
- Use `fork` only when the child needs the current transcript. For scoped work, omit `context`.
|
||||
- `sessions_spawn` does **not** accept channel-delivery params (`target`, `channel`, `to`, `threadId`, `replyTo`, `transport`). For delivery, use `message`/`sessions_send` from the spawned run.
|
||||
|
||||
## Thread-bound sessions
|
||||
|
||||
Reference in New Issue
Block a user