1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
//! Child runtime construction (B split from `runtime.rs`).
//!
//! Assembly of a child `AgentRuntime` from a [`ChildConfig`]:
//! the read-only nudge, the permission triple (prompt note / tool policy /
//! approval handler), the "先排除,再白名单" tool pipeline with post-exclusion
//! validation (§5.4), and the usage hook (§7.2). The permission-resolution
//! helpers (`spawn_permission` et al., §7.5) live here because they are the
//! build path's input; the spawn chain calls them via
//! [`build_child_runtime_with_config`](MultiAgentRuntime::build_child_runtime_with_config).
use super::*;
use crate::multi_agent::capability::{self, CapabilityResolution, ChildToolCapability};
use agent_base::{ApprovalDecision, ApprovalRequest};
/// D4(设计 2026-09-19):子 agent 的审批请求包装器——委托父 handler 前
/// 填充发起方标识(仅当为 None 时填充,不覆盖)。委托机制本身零改动。
pub(super) struct SourcedApprovalHandler {
pub(super) inner: Arc<dyn ApprovalHandler>,
pub(super) source: String,
}
#[async_trait::async_trait]
impl ApprovalHandler for SourcedApprovalHandler {
async fn approve(
&self,
mut request: ApprovalRequest,
cancel_token: tokio_util::sync::CancellationToken,
) -> AgentResult<ApprovalDecision> {
if request.source.is_none() {
request.source = Some(self.source.clone());
}
self.inner.approve(request, cancel_token).await
}
}
impl MultiAgentRuntime {
/// Legacy entry point used by the positional spawn path: registers every
/// non-excluded business tool, no whitelist, no turn/context overrides.
/// Retained for the existing unit tests' 2-arg call sites; the live
/// spawn path uses [`build_child_runtime_with_config`](Self::build_child_runtime_with_config)
/// directly (behavior byte-identical for `tool_names = None`).
#[cfg(test)]
pub(super) async fn build_child_runtime(
&self,
system_prompt: String,
full_permission: bool,
) -> AgentResult<AgentRuntime> {
let config = ChildConfig {
system_prompt: Some(system_prompt),
full_permission: Some(full_permission),
..Default::default()
};
let (runtime, _spawned, _res) = self
.build_child_runtime_with_config(&config, full_permission, None, "root/test-child")
.await?;
Ok(runtime)
}
/// Build a child runtime from a [`ChildConfig`] (design §5.4).
///
/// Returns the runtime, the **actually registered** tool names, and the
/// capability resolution (the "echo" the spawn output carries so the
/// parent can see what the child really got and whether the request was
/// degraded — §5.4 review M-3, T6). `full_permission` is already resolved
/// by the caller via [`effective_permission`](Self::effective_permission).
pub(super) async fn build_child_runtime_with_config(
&self,
config: &ChildConfig,
full_permission: bool,
capability: Option<&ChildToolCapability>,
child_path: &str,
) -> AgentResult<(AgentRuntime, BTreeSet<String>, CapabilityResolution)> {
// 能力解析(单一编码点,设计 2026-09-19 D2):per-spawn 调整后的
// 排除集在此产生,注册循环逐字消费——循环本身零改动,改的是门内的
// 名单。`capability = None` 是遗留程序化路径,行为与升级前逐字相同。
let resolution = capability::resolve_capability(
capability,
self.autonomy,
self.allow_child_write,
&self.child_excluded_tools,
&self.write_tools,
);
let mut system_prompt = config.system_prompt.clone().unwrap_or_default();
if let Some(role) = &resolution.role_prompt {
// preset 角色 prompt 在前,脚手架在后(D5)。
system_prompt = format!("{role}\n\n{system_prompt}");
}
// Read-only nudge (framework layer). The framework cannot classify which
// business tools mutate state, so this is a *suggestion* only — it does
// not gate any tool. The business layer hard-gates mutating tools via
// `child_excluded_tools` when it needs a guarantee. This is orthogonal to
// `full_permission` (approval vs. deny): even a full-permission child is
// nudged not to write when `child_read_only` is set. Under `Manual`
// (§7.5) the nudge is forced on regardless — belt and braces over the
// hard layers (exclusion + approval floor), never a substitute.
// (D3.1:nudge 条件是 per-child 纯函数——Manual 强制 / 偏执开关 /
// 解析后排除集仍含全部写工具。写子 agent 不再被灌输只读纪律。)
let system_prompt = if capability::read_only_nudge(
self.autonomy,
self.child_read_only,
&resolution.excluded_tools,
&self.write_tools,
) {
format!(
"{}\n\nYou are a read-only sub-agent: investigate, analyze, and report your findings in your final answer. Do not modify the workspace, mutate state, or run side-effecting commands — the parent agent owns all changes and will apply them based on your report.",
system_prompt
)
} else {
system_prompt
};
let (prompt, policy, approval): (
String,
Option<Arc<dyn ToolPolicy>>,
Arc<dyn ApprovalHandler>,
) = if full_permission {
// Full: no tool policy → every tool auto-approves (= current behaviour).
(system_prompt, None, Arc::new(AllowAllApprovalHandler))
} else {
// None: policy = parent's (if any) or DenyAllToolPolicy fallback.
let note = "If a tool call is rejected for lack of permission, explain in your final answer that you lacked permission for that action.";
let policy: Arc<dyn ToolPolicy> = match &self.tool_policy {
Some(p) => p.clone(),
None => Arc::new(DenyAllToolPolicy),
};
// Codex-style delegation: rather than hard-denying the child's own
// approval requests, route the decision up to the parent's approval
// handler (human-in-the-loop / auto). Falls back to DenyAll only when
// the parent itself carries no handler — which keeps the "no policy,
// no handler → read-only" invariant intact.
// D4: wrap with the source stuffer so the parent's UI can show
// which sub-agent is asking (fill-only, never overwrite).
let approval: Arc<dyn ApprovalHandler> = match &self.approval_handler {
Some(h) => Arc::new(SourcedApprovalHandler {
inner: h.clone(),
source: child_path.to_string(),
}),
None => Arc::new(DenyAllApprovalHandler),
};
(
format!("{}\n\n{}", system_prompt, note),
Some(policy),
approval,
)
};
let mut builder = AgentBuilder::new(self.client.clone())
.system_prompt(prompt)
.approval_handler(approval)
.language(self.language.clone());
if let Some(p) = policy {
builder = builder.tool_policy(p);
}
// Turn / context-window overrides (design §5.1 mapping table; wired
// straight to agent-base's builder). `None` = inherit framework
// default — i.e. the pre-config behaviour.
// preset 的 max_turns 优先;spawn 未带 preset 时回落 `ChildConfig`。
if let Some(max_turns) = resolution.max_turns.or(config.max_turns) {
builder = builder.execution_max_turns(max_turns);
}
if let Some(context_window) = config.context_window {
builder = builder.context_window(context_window);
}
// Register business tools (NOT multi-agent tools): global exclusion
// first, then the per-child whitelist (§5.4 "先排除,再白名单").
// `registered` records the names actually handed to the child — the
// post-exclusion, post-whitelist set that validation runs against.
//
// §7.5: under `Manual` the deployment-declared write set joins the
// exclusion *before* the whitelist runs, so a child asking for
// `write_file` gets the reduced set (warn, not error) — the hard
// floor of "children are read-only" is this merge, not the nudge.
//
// 能力解析(D2):排除集已由 `resolve_capability` 产出(Manual 合并
// 与 read_only/write 调整都在上游),这里原样消费——循环零改动,
// 改的是门内的名单,不是门。
let excluded = &resolution.excluded_tools;
// preset 白名单优先,未请求 preset 时沿用 `ChildConfig.tool_names`。
let tool_names: Option<&BTreeSet<String>> = resolution
.tool_names
.as_ref()
.or(config.tool_names.as_ref());
let mut registered: BTreeSet<String> = BTreeSet::new();
for tool in &self.business_tools {
let name = tool.name();
if excluded.contains(name) {
tracing::debug!(
tool = name,
"skipping excluded business tool for child runtime"
);
continue;
}
if let Some(allow) = tool_names
&& !allow.contains(name)
{
continue;
}
// D6 写门:注册面里的 write_file/edit_file 逐子包装(父豁免——
// 父的工具实例不经此路径)。只读子 agent 到不了这里(写工具已被
// 排除集拦下)。开关关闭时直接透传(纯 prompt 纪律)。
let hand_to_child: Arc<dyn Tool> = if self.write_gate_enabled
&& crate::multi_agent::write_gate::WRITE_GATE_TOOLS.contains(&name)
{
Arc::new(crate::multi_agent::write_gate::GatedTool::new(
tool.clone(),
Arc::clone(&self.write_gate),
child_path.to_string(),
))
} else {
tool.clone()
};
builder = builder.register_tool_arc(hand_to_child);
registered.insert(name.to_string());
}
// Post-exclusion whitelist validation (§5.4, review M-3). The check
// runs against `registered` — NOT the pre-exclusion business-tool
// list — so a preset that asks for a globally-excluded tool cannot
// "validate" while the child silently ends up read-only (the fake
// completion trap named in §6.1).
//
// Three outcomes for each requested name:
// 1. registered → satisfied;
// 2. excluded by deployment→ warn + drop it (intentional tightening;
// §5.4:298 — don't error, don't silently fake the permission);
// 3. resolves nowhere → ToolNotFound (unknown/typo/hallucinated
// name — fail loud per §5.4:297).
//
// NOTE (doc tension for stage-1 report): §6.1's prose says case 2
// should be a hard `ToolNotFound`, while §5.4:298, the M-3 change
// note (line 11), and the stage-1 acceptance list (§12:997) all say
// warn. This follows the acceptance criterion (warn); see report.
if let Some(allow) = tool_names {
for wanted in allow {
if registered.contains(wanted) {
continue;
}
if excluded.contains(wanted.as_str()) {
tracing::warn!(
tool = %wanted,
"requested tool is globally excluded from children; \
spawning with the reduced set (deployment-side tightening)"
);
continue;
}
return Err(AgentError::ToolNotFound {
name: wanted.clone(),
});
}
}
if let Some(ref recovery) = self.error_recovery {
builder = builder.error_recovery(recovery.clone());
}
let child = builder.build()?;
// Set model override from ChildConfig.model if specified.
// This allows sub-agents to use a different model tier (e.g., "lite").
if let Some(ref model) = config.model {
child.set_model_override(Some(model.clone()));
}
// Hook A (§5.4 / review M-4): child usage feeds the rollout budget.
// `run_turn`'s return value carries no usage, so the child runtime's
// turn-end callback is the only metering path — registered on the
// *child*, hence the parent's own spend is never metered (§7.2).
// Always on: with `child_max_tokens = None` the budget is unlimited,
// but `ControlStatus::used_tokens` stays observable.
let budget = Arc::clone(self.control.budget());
child.on_turn_end(move |ctx| {
if let Some(usage) = &ctx.usage {
budget.record_usage(usage_total(usage));
}
});
if let Some(effort) = self.child_reasoning_effort.clone() {
child.set_reasoning_effort(effort).await;
}
Ok((child, registered, resolution))
}
/// Resolve the effective full-permission flag for a spawn, applying the
/// configured [`ChildPermissionMode`]. `Full`/`None` override the LLM-supplied
/// flag; `PerSpawn` lets the LLM decide.
pub(super) fn effective_permission(&self, full_permission: bool) -> bool {
match self.child_permission_mode {
ChildPermissionMode::Full => true,
ChildPermissionMode::None => false,
ChildPermissionMode::PerSpawn => full_permission,
}
}
/// The permission a spawn **actually** gets, after the deployment autonomy
/// mode (§7.5 layer ②, the approval floor).
///
/// `Manual` forces `None`-mode semantics regardless of
/// [`ChildPermissionMode`]: policy with the parent (or `DenyAll` when the
/// parent carries none), approvals delegated to the parent's handler —
/// a child can never raise itself to `Full` in a manual deployment, and
/// the LLM-supplied `full_permission` flag is ignored (the same
/// attack-surface logic that keeps the bit out of `ChildConfig`).
/// `Auto` is exactly [`effective_permission`](Self::effective_permission).
pub(super) fn spawn_permission(&self, requested: Option<bool>) -> bool {
match self.autonomy {
AgentAutonomy::Manual => false,
AgentAutonomy::Auto => self.effective_permission(requested.unwrap_or(false)),
}
}
}