eve 0.33.0 → 0.33.1

package/docs/guides/frontend/use-eve-agent-vue.mdx

@@ -88,28 +88,51 @@ async function onFileChange(event: Event) {
 
 ## Human-in-the-loop prompts
 
-A tool opts into approval with `approval` ([Tools](../../tools)). When it triggers, the pending request shows up as a `dynamic-tool` part on the latest message at `part.toolMetadata?.eve?.inputRequest`. Read it, then answer through the same session with `respond(inputResponses)`:
+A tool opts into approval with `approval` ([Tools](../../tools)). When it triggers, the pending request shows up on a `dynamic-tool` part at `part.toolMetadata?.eve?.inputRequest`. Scan every message because an unrelated turn can add newer messages while the approval stays open, then answer through the same session with `respond(inputResponses)`:
 
-```ts
-import type { EveDynamicToolPart, EveMessagePart } from "eve/vue";
+```vue
+<script setup lang="ts">
+import { computed } from "vue";
+import { useEveAgent } from "eve/vue";
 
 const { data, respond } = useEveAgent();
 
-const isDynamicToolPart = (part: EveMessagePart): part is EveDynamicToolPart =>
-  part.type === "dynamic-tool";
-
-const request = data.value.messages
-  .at(-1)
-  ?.parts.filter(isDynamicToolPart)
-  .map((part) => part.toolMetadata?.eve?.inputRequest)
-  .find((value) => value !== undefined);
+const pendingRequests = computed(() =>
+  data.value.messages.flatMap((message) =>
+    message.parts.flatMap((part) => {
+      if (part.type !== "dynamic-tool" || part.state !== "approval-requested") return [];
+      const request = part.toolMetadata?.eve?.inputRequest;
+      return request ? [request] : [];
+    }),
+  ),
+);
+</script>
 
-if (request) {
-  await respond([{ requestId: request.requestId, optionId: "approve" }]);
-}
+<template>
+  <fieldset v-for="request in pendingRequests" :key="request.requestId">
+    <legend>
+      {{
+        request.kind === "tool-approval"
+          ? "Approval required"
+          : request.kind === "question"
+            ? "Question"
+            : "Session limit"
+      }}
+    </legend>
+    <p>{{ request.prompt }}</p>
+    <button
+      v-for="option in request.options ?? []"
+      :key="option.id"
+      type="button"
+      @click="respond([{ requestId: request.requestId, optionId: option.id }])"
+    >
+      {{ option.label }}
+    </button>
+  </fieldset>
+</template>
 ```
 
-The find-and-answer flow is the same across every framework. The [React hook reference](./overview) covers the longer walkthrough.
+For a question with `allowFreeform`, bind a text input and send `{ requestId, text }`. The [React hook reference](./overview) covers the shared behavior.
 
 ## Stop, reset, and resume
 

package/docs/tools/human-in-the-loop.md

@@ -109,7 +109,7 @@ semantics.
 
 The run picks back up exactly where it parked. Because the pause is durable, nothing is held in memory while it waits — the process can restart and the parked turn survives.
 
-For approval requests, unrelated follow-up text does not deny the tool call. eve keeps the approval pending and holds that text until the approval is answered, then replays it as the next message in the session.
+For approval requests, unrelated follow-up text does not deny the tool call — and it does not wait behind it either. The message runs as an ordinary turn while the approval stays pending and answerable; a later structured answer still resolves the original tool call. Text that exactly matches an option (like `approve`) still resolves the request directly.
 
 See [Sessions, runs & streaming](/docs/concepts/sessions-runs-and-streaming) for the full event and resume contract that this builds on.
 
@@ -117,7 +117,7 @@ See [Sessions, runs & streaming](/docs/concepts/sessions-runs-and-streaming) for
 
 Channels turn requests into native UI: the Slack adapter renders approvals as buttons and questions as select menus, and writes the user's choice back as the answer. You get this for free on every [channel](/docs/channels/overview).
 
-From your own frontend, read the pending request off the latest message and answer through the same session — see [Building a frontend](/docs/guides/frontend/overview#human-in-the-loop-prompts) for the client-side reducer and `inputResponses` shape.
+From your own frontend, scan all messages for pending requests and answer through the same session — see [Building a frontend](/docs/guides/frontend/overview#human-in-the-loop-prompts) for the client-side reducer and `inputResponses` shape.
 
 ## What to read next
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "eve",
-  "version": "0.33.0",
+  "version": "0.33.1",
   "private": false,
   "description": "Filesystem-first framework for durable backend AI agents that run anywhere.",
   "keywords": [