run-llama/workflows-py
1
0
Fork 0
mirror of https://github.com/run-llama/workflows-py.git synced 2026-07-21 04:05:25 -04:00
Code Issues 18 Packages Projects Releases 10 Wiki Activity

WorkflowServer debug UI defaults to wrong API endpoint (localhost:8000) #29

New Issue
Closed
opened 2026-02-16 02:16:11 -05:00 by yindo · 2 comments
yindo commented 2026-02-16 02:16:11 -05:00
Owner
Copy Link
Copy Source

Originally created by @b-raines on GitHub (Dec 29, 2025).

Summary

The workflow debugger UI served by WorkflowServer defaults to http://localhost:8000 as the API endpoint, but this doesn't match the actual server port. Since the UI and API are served from the same origin, the UI should default to window.location.origin.

Steps to Reproduce

  1. Start a WorkflowServer using the CLI (which defaults to port 8080):

    python -m workflows.server my_server.py

  2. Open http://localhost:8080/ in a browser

  3. The debug UI shows "Workflow server is unreachable" because it's trying to connect to http://localhost:8000 instead of http://localhost:8080

Expected Behavior

The debug UI should automatically connect to the same origin it's served from (window.location.origin), since the UI and API are served by the same WorkflowServer.

Current Behavior

The UI defaults to a hardcoded http://localhost:8000, which doesn't match:

  • The __main__.py CLI default port (8080)
  • The serve() method default port (80)
  • Any custom port the user configures

Users must manually click the settings gear and change the API URL to match their actual server port.

Suggested Fix

In @llamaindex/workflow-debugger, change the default API URL from the hardcoded http://localhost:8000 to window.location.origin. This way the UI will automatically work regardless of which port the server runs on.

Environment

  • llama-index-workflows: 2.11.5
  • @llamaindex/workflow-debugger: 0.2.2 (loaded from CDN)

Workaround

Users can manually configure the API URL in the settings panel, but this is unintuitive since the UI and API are served from the same server.

Originally created by @b-raines on GitHub (Dec 29, 2025). ## Summary The workflow debugger UI served by `WorkflowServer` defaults to `http://localhost:8000` as the API endpoint, but this doesn't match the actual server port. Since the UI and API are served from the same origin, the UI should default to `window.location.origin`. ## Steps to Reproduce 1. Start a WorkflowServer using the CLI (which defaults to port 8080): ```bash python -m workflows.server my_server.py ``` 2. Open `http://localhost:8080/` in a browser 3. The debug UI shows "Workflow server is unreachable" because it's trying to connect to `http://localhost:8000` instead of `http://localhost:8080` ## Expected Behavior The debug UI should automatically connect to the same origin it's served from (`window.location.origin`), since the UI and API are served by the same `WorkflowServer`. ## Current Behavior The UI defaults to a hardcoded `http://localhost:8000`, which doesn't match: - The `__main__.py` CLI default port (8080) - The `serve()` method default port (80) - Any custom port the user configures Users must manually click the settings gear and change the API URL to match their actual server port. ## Suggested Fix In `@llamaindex/workflow-debugger`, change the default API URL from the hardcoded `http://localhost:8000` to `window.location.origin`. This way the UI will automatically work regardless of which port the server runs on. ## Environment - `llama-index-workflows`: 2.11.5 - `@llamaindex/workflow-debugger`: 0.2.2 (loaded from CDN) ## Workaround Users can manually configure the API URL in the settings panel, but this is unintuitive since the UI and API are served from the same server.
yindo closed this issue 2026-02-16 02:16:11 -05:00
yindo commented 2026-02-16 02:16:12 -05:00
Author
Owner
Copy Link
Copy Source

@adrianlyjak commented on GitHub (Dec 29, 2025):

Fair point. Its meant to be able to easily connect to backends rather than just be embedded, but localhost:8000 is a dumb default. Will fix.

Also, FYI, you can seed the backend url with an api query parameter. Probably not helpful here, but just in case, you can visit https://localhost:8090/?api=/ to auto configure it to your current host

@adrianlyjak commented on GitHub (Dec 29, 2025): Fair point. Its meant to be able to easily connect to backends rather than just be embedded, but localhost:8000 is a dumb default. Will fix. Also, FYI, you can seed the backend url with an `api` query parameter. Probably not helpful here, but just in case, you can visit `https://localhost:8090/?api=/` to auto configure it to your current host
yindo commented 2026-02-16 02:16:12 -05:00
Author
Owner
Copy Link
Copy Source

@adrianlyjak commented on GitHub (Jan 6, 2026):

Fix released just now in v2.11.7

@adrianlyjak commented on GitHub (Jan 6, 2026): Fix released just now in v2.11.7
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
enhancement
good first issue
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/workflows-py#29
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?