claire687 opened a new pull request, #5087:
URL: https://github.com/apache/texera/pull/5087
… and file management
Expands the Texera AI agent into a global chatbot available on every page,
enabling end-to-end natural language interaction without manual navigation.
Agent service changes:
- Global agent with navigate, listWorkflows, listDatasets, listDatasets tools
- Auto-discover and provision computing units for workflow execution
- Lazy workflow creation on first operator add (no upfront workflow required)
- navigateToWorkflow with auto-naming from uploaded filename
- Loop detection for addOperator/modifyOperator repetition (max 3/5 per turn)
- File context persistence across conversation turns (lastSeenFileContext)
- Auto-inject fileName for file-scan operators from file context
- Structured response formatting with markdown, clean next-step suggestions
- Fix inputPorts/outputPorts stripping in execution requests (was causing
400)
- Auto-discover running computing unit; provision new local unit if none
exists
- Dataset-specific navigation with dvid query param for version
auto-selection
- navigateToWorkflow abort on first call to prevent looping
Frontend changes:
- Global agent panel (AppComponent) visible on every page, Cursor-style
sidebar
- Agent panel pushes page content (paddingRight) instead of overlapping
- Sidebar collapses dashboard nav when agent panel opens
- File upload via chat with duplicate detection (Use Existing / Upload New)
- Dataset version auto-selection on navigation via ?dvid= query param
- Onboarding welcome screen for first-time users (agents.length === 0)
- Agent auto-opens on login if no agents exist
- Workflow auto-naming based on uploaded filename
- Navigate to specific dataset page after file upload
- Agent registration no longer forces workflow creation upfront
<!--
Thanks for sending a pull request (PR)! Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
[Contributing to
Texera](https://github.com/apache/texera/blob/main/CONTRIBUTING.md)
2. Ensure you have added or run the appropriate tests for your PR
3. If the PR is work in progress, mark it a draft on GitHub.
4. Please write your PR title to summarize what this PR proposes, we
are following Conventional Commits style for PR titles as well.
5. Be sure to keep the PR description updated to reflect all changes.
-->
### What changes were proposed in this PR?
<!--
Please clarify what changes you are proposing. The purpose of this section
is to outline the changes. Here are some tips for you:
1. If you propose a new API, clarify the use case for a new API.
2. If you fix a bug, you can clarify why it is a bug.
3. If it is a refactoring, clarify what has been changed.
3. It would be helpful to include a before-and-after comparison using
screenshots or GIFs.
4. Please consider writing useful notes for better and faster reviews.
-->
### Any related issues, documentation, discussions?
<!--
Please use this section to link other resources if not mentioned already.
1. If this PR fixes an issue, please include `Fixes #1234`, `Resolves
#1234`
or `Closes #1234`. If it is only related, simply mention the issue
number.
2. If there is design documentation, please add the link.
3. If there is a discussion in the mailing list, please add the link.
-->
### How was this PR tested?
<!--
If tests were added, say they were added here. Or simply mention that if the
PR
is tested with existing test cases. Make sure to include/update test cases
that
check the changes thoroughly including negative and positive cases if
possible.
If it was tested in a way different from regular unit tests, please clarify
how
you tested step by step, ideally copy and paste-able, so that other
reviewers can
test and check, and descendants can verify in the future. If tests were not
added,
please describe why they were not added and/or why it was difficult to add.
-->
### Was this PR authored or co-authored using generative AI tooling?
<!--
If generative AI tooling has been used in the process of authoring this PR,
please include the phrase: 'Generated-by: ' followed by the name of the tool
and its version. If no, write 'No'.
Please refer to the [ASF Generative Tooling
Guidance](https://www.apache.org/legal/generative-tooling.html) for details.
-->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
