How i can execute tool on client side?

[Zain-ul-din]

Even though this is a simple requirement, but i'm trying so hard for the last 3 hours to figure out how to execute the tool on the client side. I know there is a workaround using listening to events like onFinish and onEvent. Both seem not to be working for me.

Here is my code:

import { defineWorkflowTool } from "eve/tools";
import { always } from "eve/tools/approval";
import { z } from "zod";

export default defineWorkflowTool({
  description: "Returns Map polygons and bounds in feet",
  inputSchema: z.object({}),
  approval: always(),
  async execute(_, ctx) {
    "use workflow";
    const answer = await ctx.ask({
      prompt: "Access Map State",
      display: "text",
      allowFreeform: true,
    });
    console.log(answer);
    return answer.status === "answered" ? answer.text : "Tool call failed";
  },
});

const agent = useEveAgent({
    onFinish: (snapShot) => {
      const toolCallMessages = snapShot.data.messages.filter((message) => {
        return message.parts.find((part) => part.type === "dynamic-tool");
      });

      const lastToolCallMessage = toolCallMessages.at(-1);
      if (!lastToolCallMessage) return;

      const toolCall = lastToolCallMessage?.parts.find(
        (part) => part.type === "dynamic-tool",
      );

      console.log(toolCall);

      if (
        toolCall?.toolName === "get-map-state" &&
        toolCall.state === "approval-requested"
      ) {
        setTimeout(() => {
          void agent.respond(
            [
              {
                requestId: toolCall.toolMetadata?.eve?.inputRequest
                  ?.requestId as string,
                text: JSON.stringify({ polygons }, null, 2),
              },
            ],
            {
              turnPolicy: "steer",
            },
          );
        }, 0);
      }
    },
  });

Things I have tried:

• onEvent: always returns an error due to a race condition (turn is already in process; set turnPolicy: "steer") i tried setting it but i'm still getting the error.
• onFinish: this is indeed sending the tool response back but after that agents got stuck, no response back.

Things i don't want:

• I know there is way to send context with message on every turn, but for upcoming requirements i think, it is not good fit for me.

[BinaryBrain010]

The issue is that you have two pauses stacked on one tool.

approval: always() raises a tool-approval request first, and then ctx.ask() raises a separate question request. Both show up as state === "approval-requested", so your onFinish sends text to the approval request. The question that follows never gets answered, and the turn stays parked at session.waiting. That's why it looks stuck.

The onEvent error is a timing problem: you're calling respond() while the turn is still streaming. onFinish only fires once, so it never sees the second request.

Fix: drop the approval. ctx.ask() already pauses the run durably.

export default defineWorkflowTool({
  description: "Returns map polygons and bounds in feet",
  inputSchema: z.object({}),
  async execute(_, ctx) {
    "use workflow";
    const answer = await ctx.ask({ prompt: "map-state", allowFreeform: true });
    return answer.status === "answered" ? answer.text : "Map state unavailable";
  },
});

On the client, answer based on state instead of lifecycle callbacks:

const answered = useRef(new Set<string>());

useEffect(() => {
  if (agent.status !== "ready") return;
  for (const part of agent.data.messages.flatMap((m) => m.parts)) {
    if (part.type !== "dynamic-tool" || part.state !== "approval-requested") continue;
    const req = part.toolMetadata?.eve?.inputRequest;
    if (!req || req.kind !== "question" || part.toolName !== "get-map-state") continue;
    if (answered.current.has(req.requestId)) continue;
    answered.current.add(req.requestId);
    void agent.respond([{ requestId: req.requestId, text: JSON.stringify({ polygons }) }]);
  }
}, [agent.data.messages, agent.status]);

Notes:

• Check req.kind === "question" so you never answer an approval with text.
• Wait for status === "ready" before calling respond(). This avoids the race.
• Dedupe by requestId. The request stays pending until input.resolved arrives, so the effect can run more than once.
• You don't need turnPolicy: "steer" here.

[Zain-ul-din]

Well, after removing the approval part, it works for me, but we should avoid useEffect as much as possible.