What feature would you like to see?
A repeatable CLI flag, e.g. --disabled-tools Agent,AgentSwarm, that applies the same denylist as [tools] disabled but only for that process.
Additional information
Today the only switch is [tools] disabled in the user config file, and the docs say that table applies to every agent in all sessions. kimi --help (2.1.1) has no flag for tools or subagents. A one-off session that must not spawn Agent / AgentSwarm therefore has to edit the shared config and remember to revert it — and any other session started in the meantime inherits the change.
Please reuse the matching rules already documented for [tools] (exact built-in names, case-sensitive, MCP globs allowed). If unknown names in [tools] become errors (#4037), an unknown name on this flag should fail the same way.
When the flag is omitted, behaviour stays as it is today.
What feature would you like to see?
A repeatable CLI flag, e.g.
--disabled-tools Agent,AgentSwarm, that applies the same denylist as[tools] disabledbut only for that process.Additional information
Today the only switch is
[tools] disabledin the user config file, and the docs say that table applies to every agent in all sessions.kimi --help(2.1.1) has no flag for tools or subagents. A one-off session that must not spawnAgent/AgentSwarmtherefore has to edit the shared config and remember to revert it — and any other session started in the meantime inherits the change.Please reuse the matching rules already documented for
[tools](exact built-in names, case-sensitive, MCP globs allowed). If unknown names in[tools]become errors (#4037), an unknown name on this flag should fail the same way.When the flag is omitted, behaviour stays as it is today.