Files
windmill/frontend/src/lib/components/agentRequest.ts
T
hugocasaandClaude Opus 5.5 a1bc9ec0c2 feat: tool approval and a question tool for ai agent steps (#11826)
* feat(ai-agent): built-in approval tool that parks the agent

An AI agent step can now be given a built-in "Request approval" tool. The model
calls `request_approval` with a message; the agent stores its conversation in
the new `ai_agent_checkpoint` table, releases its worker by parking its own
queue row like a workflow-as-code parent, and resumes with the answer (approved,
approver, comment) or a timeout once someone answers from the run page.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(ai-agent): tie approval answers to their request and hold the turn

- A turn that asks for approval runs none of its other calls; they are refused
  so the model repeats them after the answer.
- The run page sends the request's call id. An answer naming another request is
  ignored and the agent parks again for the time left; `suspend` is zeroed when
  the answer is read, so answers sent while the agent runs are refused.
- The checkpoint is read whatever the current roster holds, the answer's
  outcome is written by position, and a cancel that beats the park completes
  the job as cancelled.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(ai-agent): say why calls beside an invalid approval request were refused

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(ai-agent): one approval form per request, none on a finished run

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* feat(ai-agent): answer approval requests from a flow's chat

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(ai-agent): show chat approvals for agents that do not stream

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* feat(ai-agent): approval as a per-tool setting, built-in tool asks a question

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(ai-agent): say when a nested agent leaves out tools that require approval

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* feat(ai-agent): show chat approvals and questions on the tool's own card

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* feat(ai-agent): question choices, and approval buttons shared with approval steps

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* feat(ai-agent): show a waiting agent as suspended, and refused calls as not run

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(ai-agent): each added chat card shows its own call, answered marker keyed by job

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test(ai-agent): approve and reject a held call through resume_suspended

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* feat(ai-agent): require approval in a tool settings tab, plain descriptions on built-in tool panes

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(ai-agent): sentence case for the web search tool label

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* feat(ai-agent): built-in tool drawers explain themselves in the header subtitle

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(ai-agent): clearer question tool subtitle

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(ai-agent): badge the tool settings tab like run settings

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* chore(ai-agent): regenerate system prompts and MCP session files

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 19:22:45 +01:00

61 lines
2.0 KiB
TypeScript

import { JobService, type FlowStatus, type FlowStatusModule } from '$lib/gen'
export type AgentRequest = Extract<
NonNullable<FlowStatusModule['agent_actions']>[number],
{ type: 'approval' | 'question' }
>
/** The approval or question an agent step's actions end on, while nobody has answered it. */
export function waitingRequest(
mod: Pick<FlowStatusModule, 'agent_actions' | 'agent_actions_success'>
) {
const actions = mod.agent_actions
const last = actions?.[actions.length - 1]
if (
!last ||
(last.type !== 'approval' && last.type !== 'question') ||
mod.agent_actions_success?.[actions!.length - 1] !== undefined
) {
return undefined
}
return last
}
/** The approval or question a flow's current agent step is parked on: the step stays in
* progress while its own job waits. */
export function pendingAgentApproval(job: { flow_status?: FlowStatus } | undefined) {
const mod = job?.flow_status?.modules?.[job?.flow_status?.step]
if (mod?.type !== 'InProgress' || !mod.job) return undefined
const action = waitingRequest(mod)
return action && { agentJobId: mod.job, action }
}
/** Suspended, as the run's badge and icon say: an approval step, or an agent waiting on a person. */
export function isSuspended(job: { suspend?: number; flow_status?: FlowStatus }) {
return !!job.suspend || !!pendingAgentApproval(job)
}
export type PendingAgentRequest = NonNullable<ReturnType<typeof pendingAgentApproval>>
/** `answer` is the question's answer, a list when several choices were picked, or the reason given
* with a rejection. Its call id goes with the answer, so a page left open on an earlier request
* cannot answer the one waiting now. */
export async function answerAgentRequest(
workspace: string,
{ agentJobId, action }: PendingAgentRequest,
approved: boolean,
answer?: string | string[]
) {
await JobService.resumeSuspended({
workspace,
jobId: agentJobId,
requestBody: {
approved,
payload: {
call_id: action.call_id,
...(answer?.length ? { [action.type === 'question' ? 'answer' : 'comment']: answer } : {})
}
}
})
}