feat: add SpawnPod profile selection
This commit is contained in:
@@ -65,3 +65,16 @@ The following workflows are advertised resident. When a user request matches one
|
||||
|
||||
{{ entries }}\
|
||||
"""
|
||||
|
||||
spawn_pod_tool_description = """\
|
||||
Spawn a new Pod process to work on a delegated task. The spawner's write scope is reduced by the scope passed here; the spawned Pod receives its own socket and starts running `task` immediately. The spawned Pod outlives the spawner's current turn and can be contacted again through its socket path.
|
||||
|
||||
Profile selection: `profile` may be omitted or set to `default` to use the effective child default profile, set to `inherit` to derive reusable child configuration from this Pod, or set to one of the registry selectors below. Raw/path profile selectors are not accepted by SpawnPod. `scope` is always the only delegated filesystem capability; profile scope is replaced by the explicit SpawnPod scope.
|
||||
|
||||
Default profile: {{ default_profile }}
|
||||
Special selector: inherit — derive reusable model/worker/tool policy from the spawner while replacing pod.name and scope.
|
||||
Available registry profiles:
|
||||
{{ available_profiles }}{% if profile_diagnostic %}
|
||||
|
||||
Profile discovery diagnostic: {{ profile_diagnostic }}{% endif %}\
|
||||
"""
|
||||
|
||||
Reference in New Issue
Block a user