Skip to content

Add LiteLLM Communication and Show Generated Workflow #4428

Closed

Description

@mengw15

Feature Summary

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.

Image

Demo Video

Ignore the Jupyter iframe, it will be added in the next PR.

2.show.response.mp4

Impact / Priority

(P2)Medium – useful enhancement

Affected Area

No response

Activity

  1. added theissue type on Apr 20, 2026
  2. Yicong-Huang commented on Apr 21, 2026

    @Yicong-Huang
    Contributor

    @mengw15 you should be able to triage issues now. Please help to do so, thanks. You can start with assigning your own issues ;)

  3. mengw15 commented on Apr 21, 2026

    @mengw15
    ContributorAuthor

    @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.

  4. Yicong-Huang commented on Apr 23, 2026

    @Yicong-Huang
    Contributor

    I think the rule (?) is the ppl has to reply to this issue to be assignable.

  5. chenlica commented on Apr 23, 2026

    @chenlica
    Contributor

    Let's test this rule. @zyratlo Can you reply to this issue and #4427?

  6. zyratlo commented on Apr 23, 2026

    @zyratlo
    Contributor

    Let's test this rule. @zyratlo Can you reply to this issue and #4427?

    Sounds good

  7. mengw15 commented on Apr 23, 2026

    @mengw15
    ContributorAuthor

    Close this issue, since we decide to not separating frontend and backend

  8. Yicong-Huang commented on Apr 23, 2026

    @Yicong-Huang
    Contributor

    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.

  9. changed the title [-]Add the Python-Notebook-Migration Tool Frontend[/-] [+][Notebook Migration] 2. Add LiteLLM Communication and Show Generated Workflow[/+] on May 13, 2026
  10. 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
  11. zyratlo commented on May 13, 2026

    @zyratlo
    Contributor

    /take

  12. changed the title [-][Notebook Migration] 3. Add LiteLLM Communication and Show Generated Workflow[/-] [+]Add LiteLLM Communication and Show Generated Workflow[/+] on May 13, 2026
  13. zyratlo commented on Aug 6, 2026

    @zyratlo
    Contributor

    This issue was split into sub-issues #5259 and #5261

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

frontendChanges related to the frontend GUI

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions