Skip to content

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

Open
0 of 7 issues completed

Description

@bobbai00

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 (Use the AI SDK's native message history in the agent #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 (Give the agent one workflow edit tool that takes a patch #9481). Later the same tools are served from a Texera MCP server, one of many the agent can connect to (Serve the agent's workflow tools from a Texera MCP server #9457).
  3. Skills. The system prompt shrinks to the essentials, and Texera's know-how moves into skills loaded only when needed (Move the agent's guides into skills and shorten its system prompt #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 (Use the AI SDK's UI message stream between the agent service and the browser #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 (Let the agent join the workflow's shared editing and execution session #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

Activity

  1. added theissue type on Nov 15, 2026
  2. changed the title [-]Refactor the agent service around native messages, skills and MCP tools[/-] [+]Refactor the agent service around native messages, skills, MCP tools and a shared session[/+] on Nov 15, 2026
  3. self-assigned this
    on Nov 15, 2026
  4. changed the title [-]Refactor the agent service around native messages, skills, MCP tools and a shared session[/-] [+]Refactor the agent service around native messages, skills, MCP tools, AG-UI and a shared session[/+] on Nov 16, 2026
  5. bobbai00 commented on Nov 16, 2026

    @bobbai00
    ContributorAuthor

    Updated the plan after a review:

  6. changed the title [-]Refactor the agent service around native messages, skills, MCP tools, AG-UI and a shared session[/-] [+]Refactor the agent service around native messages, skills, MCP tools, a UI message stream and a shared session[/+] on Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions