Request
Provide a public way to pass a list of disallowed built-in tool names down to the SDK (disallowedTools) for the packaged Claude agent — e.g. a session-level option on the agentOS client API forwarded through ACP, an ACP config option, or an env var on the agent package. Default (no list) keeps current behavior.
Why
Some Claude Code built-in tools cannot work depending on the integration: AskUserQuestion has no answer channel in a headless client, WebFetch may be blocked by the deployment's network policy, etc. Without disallowedTools, these tools stay in the model's context, the model keeps trying them, and every attempt fails at runtime — visible to end users as noisy failed tool calls.
Request
Provide a public way to pass a list of disallowed built-in tool names down to the SDK (
disallowedTools) for the packaged Claude agent — e.g. a session-level option on the agentOS client API forwarded through ACP, an ACP config option, or an env var on the agent package. Default (no list) keeps current behavior.Why
Some Claude Code built-in tools cannot work depending on the integration:
AskUserQuestionhas no answer channel in a headless client,WebFetchmay be blocked by the deployment's network policy, etc. WithoutdisallowedTools, these tools stay in the model's context, the model keeps trying them, and every attempt fails at runtime — visible to end users as noisy failed tool calls.