Skip to content

Report runtime working_dir and username from runner via JobRuntimeData#3617

Merged
peterschmidt85 merged 3 commits intomasterfrom
feat/runtime-working-dir-username
Feb 27, 2026
Merged

Report runtime working_dir and username from runner via JobRuntimeData#3617
peterschmidt85 merged 3 commits intomasterfrom
feat/runtime-working-dir-username

Conversation

@peterschmidt85
Copy link
Contributor

@peterschmidt85 peterschmidt85 commented Feb 26, 2026

The runner resolves the actual working directory and OS username at startup but never sent them back to the server. The UI needs these to construct correct IDE deep-link URLs.

Changes

Add working_dir and username to PullResponse (runner) and JobRuntimeData (server). The server saves them from the runner response on the first poll (write-once).

Backward compatible with old runners, old servers, and existing database rows.

The runner now reports the resolved working directory and OS username
back to the server through the PullResponse. The server persists these
in JobRuntimeData (write-once), and the frontend uses
job_runtime_data.working_dir to construct correct IDE deep-link URLs
instead of the hardcoded legacy /workflow path.

Made-with: Cursor
@peterschmidt85 peterschmidt85 changed the title Report runtime working_dir and username from runner via JobRuntimeData Report runtime working_dir and username from runner via JobRuntimeData Feb 26, 2026
un-def and others added 2 commits February 27, 2026 15:25
/api/pull is too late, we need these fields as soon as the job state is
switched to RUNNING
…Submission?.job_runtime_data?.working_dir` after `run.status === 'running'`; otherwise, fallback to `/`.
@peterschmidt85 peterschmidt85 merged commit 84e2c70 into master Feb 27, 2026
8 checks passed
@peterschmidt85 peterschmidt85 deleted the feat/runtime-working-dir-username branch February 27, 2026 23:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants