Eve

Project Eve’s durable session view while preserving delivery and interaction semantics.

Bind the native session hook

Install eve@1.0.0-rc.0 and configure its server/framework integration. The recipe targets Eve's current release candidate, not older 0.x event shapes. Follow view setup. Mount a new keyed owner when replacing session configuration.

eve-conversation.tsx

12345678910111213141516171819202122232425262728import { useState } from "react";
import { Button } from "@ghost-ui/core/components/button";
import { useEveAgent, type UseEveAgentOptions } from "eve/react";
import { activeTurn } from "eve/events";
import { createEveAdapter } from "@ghost-ui/core/chat-adapter-eve";
import { useChatAdapter } from "@ghost-ui/core/chat-runtime-react";
import { Message, MessageBody } from "@ghost-ui/core/components/message";
import { MessageParts } from "@ghost-ui/core/components/message-parts";
const adapter = createEveAdapter();
export function EveConversation({ options, threadId, revision }: {
  options: UseEveAgentOptions; threadId: string; revision: number;
}) {
  const eve = useEveAgent(options);
  const runtime = useChatAdapter(adapter, { ...eve, canCancel: !!activeTurn(eve.view) }, {
    identity: { threadId, revision },
  });
  const [error, setError] = useState<unknown>();
  return <>
    {runtime.messages.map(message => <Message key={message.id} actor={message.actor}><MessageBody>
      <MessageParts parts={message.parts} />
    </MessageBody></Message>)}
    <Button disabled={runtime.capabilities.send.support !== "supported" || !runtime.capabilities.send.available}
      onClick={() => { setError(undefined); void Promise.resolve().then(() => runtime.controller.send({ text: "Review the brief", attachments: [] })).catch(setError); }}>Review brief</Button>
    {runtime.capabilities.stop.support === "supported" && runtime.capabilities.stop.available &&
      <Button onClick={() => { void Promise.resolve().then(() => runtime.controller.stop?.()).catch(setError); }}>Stop</Button>}
    {(error || runtime.controller.error) ? <p role="alert">The request could not complete.</p> : null}
  </>;
}

Pass { agent: "support" } for a named same-origin agent, or { baseUrl: "/api" } for your proxy; do not combine them. The identity must name the application/native session context, not a display label. Keep native session lifecycle in the owner that supplies these options.

Acceptance, completion and human input

send() resolves when delivery is accepted, not when every turn has finished. Eve owns its authoritative event log and projected messages; use its native follow/resume APIs for durable progress. An active turn paused for human input can report idle, so Ghost takes explicit canCancel from activeTurn(eve.view) rather than inferring cancellation from a busy label.

eve-interaction.ts

1234import type { UseEveAgentReturn } from "eve/react";
export function answerInteraction(eve: UseEveAgentReturn, interactionId: string, optionId: string) {
  return eve.respond([{ interactionId, optionId }]);
}

Interaction parts remain explicit eve-interaction data, separate from tool execution. Render their validated options in your application and send the actual native answer. Approval, clarification and a tool result have different payloads; do not manufacture a boolean approval from an arbitrary interaction.

Troubleshooting

A successful send with unfinished work may be an accepted delivery; inspect the native view rather than marking execution complete. A disabled stop may mean there is no active turn. A changed baseUrl or session option needs a replacement owner, not only new props. See threads, adapters and stability for the shared contracts.