Devotd Github
NewCoding agents

vercel-labs/eve-agent-python-template — Restoring eve RC chat interactions

Vercel Labs' eve-agent-python-template has reworked the frontend message rendering layer in its latest commit, along with the fix "restore eve RC chat interactions (#3)".

Repositoryvercel-labs/eve-agent-python-template ↗

Vercel Labs' eve-agent-python-template has reworked the frontend message rendering layer in its latest commit, along with the fix "restore eve RC chat interactions (#3)".

GitHub description: eve agent template with a Next.js frontend and FastAPI backend.

stars
★ 1
Forks
0
Language
TypeScript
License
MIT
Read original source ↗View on GitHub ↗

vercel-labs/eve-agent-python-template is an Eve agent template consisting of a Next.js frontend and a FastAPI backend. The latest commit c92518c was pushed on October 30, 2026 at 21:50 UTC with the commit message "fix: restore eve RC chat interactions (#3)", and Colton Padden of vercel.com left a Signed-off-by. The stats are 540 lines added, 83 lines deleted, 623 lines in total, and only two files were touched.

The changes remain only in the two files apps/web/app/_components/agent-chat.tsx(+11/-12) and apps/web/app/_components/agent-message.tsx(+529/-71). In agent-chat.tsx, the interactions import from eve/events, the questionsFor helper, and the passing of that prop were removed. At the same time, the interaction part was added to the exclusion list for judging an empty assistant message that is replaced by the thinking indicator, and the indentation and comments of getLatestTurnFailure were also cleaned up. In agent-message.tsx, the questionsFor prop of AgentMessage was dropped, and BashToolContent, Tool, ToolContent, and ToolHeader were newly imported. A constant MAX_SUMMARY_ROWS = 4, which determines the number of input fields listed by an approval card before it summarizes the rest, was added, and JSDoc comments were attached to each prop and function.

The conversation screen of this template handles model responses (text), reasoning, tool calls (tool), and user questions and approvals (interaction) as message parsing units. Questions and approval cards are drawn with the @/components/ui/questionnaire component, and the same file also references the Spec type from @json-render/react and the uiSpecSchema of the local ui-registry. This commit is a fix that realigns the contacts between that rendering layer and the session view (failure, turns, interaction). The Python files on the backend side are not included in this commit.

However, the interaction restoration that the commit message talks about and the surface of the patch do not match. The questionsFor helper and prop have disappeared from both files, and the provided patch does not include the latter part of agent-message.tsx, so it is not possible to confirm how interaction cards are currently drawn. Neither the license nor the release version indication was given, and there are no test or performance figures. It is a change worth referencing for those looking for a starting point for the template, but the actual behavior can only be known by looking at the repository directly.