You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add LiteLLM Communication and Show Generated Workflow #4428
This second sub-issue introduces communication with the LLM through the LiteLLM proxy service that already exists in Texera. Now after the user submits a notebook, the notebook will be passed to the LLM with our prompts. After generation time, the generated workflow will be returned from the LLM and displayed in the Texera workspace. At this stage, there is still no Jupyter iframe, mapping, or database storage.
Proposed Solution or Design
This sub-issue describes Steps 4, 5, 6, 7, and 8 in the architecture diagram.
Demo Video
Ignore the Jupyter iframe, it will be added in the next PR.
@mengw15 you should be able to triage issues now. Please help to do so, thanks. You can start with assigning your own issues ;)
Thanks! I’ll help with triaging issues.
For this issue and #4427, I helped Ryan create them as sub-issues because he was not able to create sub-issues himself. I was just trying to assign them back to Ryan, but I could not find his name in the assignee list.
Nit: Another way of thinking is the issue is still a valid "todo", but you can use one PR to solve both issues at the same time. This way we don't need to re position the opened issues. I.e., you don't need to update the other issue to contain both frontend and backend.
changed the title [-]Add the Python-Notebook-Migration Tool Frontend[/-][+][Notebook Migration] 2. Add LiteLLM Communication and Show Generated Workflow[/+]on May 13, 2026
changed the title [-][Notebook Migration] 2. Add LiteLLM Communication and Show Generated Workflow[/-][+][Notebook Migration] 3. Add LiteLLM Communication and Show Generated Workflow[/+]on May 13, 2026
changed the title [-][Notebook Migration] 3. Add LiteLLM Communication and Show Generated Workflow[/-][+]Add LiteLLM Communication and Show Generated Workflow[/+]on May 13, 2026
Activity
Yicong-Huang commentedon Apr 21, 2026
@mengw15 you should be able to triage issues now. Please help to do so, thanks. You can start with assigning your own issues ;)
mengw15 commentedon Apr 21, 2026
Thanks! I’ll help with triaging issues.
For this issue and #4427, I helped Ryan create them as sub-issues because he was not able to create sub-issues himself. I was just trying to assign them back to Ryan, but I could not find his name in the assignee list.
Yicong-Huang commentedon Apr 23, 2026
I think the rule (?) is the ppl has to reply to this issue to be assignable.
chenlica commentedon Apr 23, 2026
Let's test this rule. @zyratlo Can you reply to this issue and #4427?
zyratlo commentedon Apr 23, 2026
Sounds good
mengw15 commentedon Apr 23, 2026
Close this issue, since we decide to not separating frontend and backend
Yicong-Huang commentedon Apr 23, 2026
Nit: Another way of thinking is the issue is still a valid "todo", but you can use one PR to solve both issues at the same time. This way we don't need to re position the opened issues. I.e., you don't need to update the other issue to contain both frontend and backend.
[-]Add the Python-Notebook-Migration Tool Frontend[/-][+][Notebook Migration] 2. Add LiteLLM Communication and Show Generated Workflow[/+][-][Notebook Migration] 2. Add LiteLLM Communication and Show Generated Workflow[/-][+][Notebook Migration] 3. Add LiteLLM Communication and Show Generated Workflow[/+]zyratlo commentedon May 13, 2026
/take
[-][Notebook Migration] 3. Add LiteLLM Communication and Show Generated Workflow[/-][+]Add LiteLLM Communication and Show Generated Workflow[/+]zyratlo commentedon Aug 6, 2026
This issue was split into sub-issues #5259 and #5261