Danny Avila 5c9f7ac789 feat: gate ask_user_question behind its own agent capability ... Add a first-class AgentCapabilities.ask_user_question (in defaultAgentCapabilities, on by default) so admins can enable/disable questions independently via endpoints.agents.capabilities, exactly like execute_code / web_search — not lumped under the generic tools capability. - ToolService: both filteredTools predicates (definitions-only and instance loaders) gate ask_user_question on checkCapability(ask_user_question) before the generic tools fallthrough. When off, the tool is dropped from toolDefinitions/toolRegistry, so run.ts's agentRequestsAskUserQuestion (which keys on the loaded surface) declines to install it and attach a checkpointer — the capability is enforced end-to-end at the loader, no run.ts change needed. - Tools dialog catalog: surface the ask builtin under its own capability rather than the generic tools one, so the UI matches the backend gate. - Tests: ToolService capability on/off filtering + defaults membership; catalog builtin visibility keyed on the dedicated capability.		2026-07-07 15:57:14 -04:00
..
api	fix: Codex round 6 — composer submit lock + abort stamp before emit	2026-07-07 15:46:17 -04:00
client	🧰 feat: Redesign Agent Builder with Unified Tools Marketplace, Skills & Orchestration (#13952)	2026-07-05 11:30:12 -04:00
data-provider	feat: gate ask_user_question behind its own agent capability	2026-07-07 15:57:14 -04:00
data-schemas	🗄️ fix: Return Cached Transaction-Support Value on Cache Hit (#13999)	2026-07-05 12:02:55 -04:00