simulate: link to the dashboard of the project the run belongs to - #948
Merged
Conversation
The dashboard URL was derived from --server-url, so a staging project run against the default server URL linked to the production dashboard. Derive it from the project URL instead, the same way `lk agent dev` does, falling back to the --server-url derivation for unrecognized hosts.
u9g
force-pushed
the
jason/simulate-dashboard-from-project
branch
from
August 27, 2026 20:53
5bf746f to
b0eb7ed
Compare
theomonnom
approved these changes
Aug 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The simulate TUI derived its dashboard links from
--server-url, so a run under a staging project against the default server URL linked to the production dashboard.Derive the dashboard host from the project URL instead, using the same
cloudProjectmappinglk agent devalready uses (wss://p.staging.livekit.cloud→cloud.staging.livekit.io), and fall back to the--server-urlderivation for unrecognized hosts. All dashboard links (run, job, item, report, transcript refs) go throughdashboardBaseURL, so they all follow the project.