Refactor the agent service around native messages, skills, MCP tools, a UI message stream and a shared session

Aperta
#9,453 1 commento 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@bobbai00 ci sta già lavorando.

Dal 15/11/2026.

  • #9494 di @bobbai00 — aperta
  • #9495 di @bobbai00 — aperta
  • #9496 di @bobbai00 — aperta

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

Task Summary
Target design of the agent

This refactor reshapes the agent service around four ideas.

  1. Standard tool-call state. The agent keeps tool calls and their results in the AI SDK's own message history, instead of rebuilding a summary by hand at every step (#9455).
  2. A few tools, with edits as patches. The agent reads a workflow, looks up operators, executes, and edits with one tool whose input is a patch: one call can add, modify and delete several operators and their links, and is applied whole or not at all (#9481). Later the same tools are served from a Texera MCP server, one of many the agent can connect to (#9457).
  3. Skills. The system prompt shrinks to the essentials, and Texera's know-how moves into skills loaded only when needed (#9456).
  4. One protocol to the browser, and one shared session. The agent streams its turns to the browser in the AI SDK's own UI message stream, which the SDK's chat clients read in Angular today and in React later (#9482). Instead of editing its own copy, the agent joins the workflow's shared editing and execution session, so the agent and the user see the same workflow and the same executions (#9464).

The order: #9454 first, so every later step can report its score. Then the loop, the tools and the protocol: #9455, then #9481 and #9482, then #9456. Then the shared session (#9464), and last the MCP server (#9457), whose tools edit the shared workflow.

Saving conversations with an owner (#5267, #5268) moves to the resource unification in #9395, where a conversation becomes a resource kind. In the picture, the session store comes with that work, and add_operator and edit_operator are one edit_workflow tool.

For background, see #9377 and #9395. A few open fixes should land first: #9149, #9259, #8753 and #9043.

Task Type
  • Refactor / Cleanup
  • DevOps / Deployment / CI
  • Testing / QA
  • Documentation
  • Performance
  • Other
Lingua principale
Scala
Stelle
333
Fork
202
Merge medio
3g 11h
PR unite (30g)
185

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di apache/texera

Tutte le issue di apache/texera

Issue simili

Altre issue su Scala

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.