Skip to content

feat(web): preview run workspace files without the IDE - #1125

Open
wcy12378 wants to merge 1 commit into
Tencent:mainfrom
wcy12378:codex/run-workspace-file-preview
Open

wcy12378 wants to merge 1 commit into
Tencent:mainfrom
wcy12378:codex/run-workspace-file-preview

Conversation

@wcy12378

Copy link
Copy Markdown

Run outputs can refer to intermediate workspace reports that are inconvenient to inspect through the IDE. Add a read-only file browser to the run-detail header, using the existing workspace tree and file APIs.

The browser supports directory navigation and path/name search, renders Markdown by default with a source toggle, and displays other supported text files as escaped source. It identifies the content as the current workspace, separate from immutable artifact snapshots. Unavailable/cleaned workspaces explain the existing restore entry; file-size and binary-file restrictions continue to come from the server. Rendering is bounded to 200 entries at once, with explicit notices for larger/truncated results.

Late file or artifact responses cannot replace a newer selection/modal. Existing artifact preview remains available.

Refs #1078. This provides the file-tree alternative for run workspaces; it does not turn arbitrary report paths into clickable links or add new file-write APIs.

Validation:

  • 18 tests passed: new file-preview regression tests plus existing run-detail/action tests. New entry/preview tests and the old-artifact response regression were observed failing before implementation/fix.
  • node --check web/app/run-file-preview.js, node --check web/app/runs.js, and git diff --check passed.
  • Real Edge at 1440px/390px, light/dark, verified opening from run details, directory navigation, keyboard file opening, Markdown rendering, exact source text, keyboard scrolling, no injected script execution, and no horizontal overflow. Browser plugin unavailable: Playwright used the actual scripts/styles with mocked APIs; the unrelated boot loader was explicitly settled in this fixture. This is not a live deployment acceptance test.

No Go/backend behavior changed. Full-repository tests, a fresh chatbot build, paid integrations and live remote-runner acceptance were not run.

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.

1 participant