Repository navigation
feat: add a remote Git panel to session environments - #21995
Conversation
Design Review (Opus 5.5) — ✅ PASSDesign-level review of Design-Verdict: PASS No design-level blocker: the panel reuses the existing browse endpoint, redacts whole file bodies before diffing, and the one format change (NUL porcelain) is handled by its only server-side reader. Notes
[DESIGN-REVIEWED] 6049487 Description read[DESCRIPTION-READ] 6fdcb1abad871d61e4ee2ad7e8111b0dd9cfbee9b2cf9212dde008242121dd70 That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
First Principles Review (Opus 5.5) — ✅ PASSPremise-level review of First-Principles-Verdict: PASS Nothing blocks: every item comes from the frozen Goal or its "never fetches" exclusion. One redaction layer patches a gap in the shared redactor for this panel only. Notes
What this change shipsInventory (10 items) — 9 justifiedIntent: let a remote-environment chat's Git tab show the guest checkout's branch, changes, per-file diff and history, read-only. ADDITION.
[FIRST-PRINCIPLES-REVIEWED] 6049487 Description read[DESCRIPTION-READ] 90250ac0fa24422fe6b1facef49d60c03188a89f30c7519b4ed6ad9c526b2c31 That sha256 names the PR description this verdict read. Recompute it with |
UX Review (Opus 5.5) — ✅ PASSUX-level review of UX-Verdict: PASS Nothing blocks. The blind reader identified and would use every primary control: the row expanders, refresh, and the purple "Draft a request…" links. Notes
[UX-REVIEWED] 6049487 Description read[DESCRIPTION-READ] b6d4a275bc425d667d03e02da8961b559735370959503449969368d04b3f3a98 That sha256 names everything this verdict read: the PR description, plus the 17 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
Opus 5.5 Review — ✅ no blocking findingsReviewed Review detailsNo findings. Notes:
[OPUS-REVIEWED] 6049487 Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
GPT 6.1 Review — ✅ no blocking findingsGPT 6.1 completed its review of This comment is updated in place on each push. Review detailsNo findings. False positive or not applicable? A repository writer can comment: |
5da3123 to
9c027ca
Compare
9c027ca to
91efcec
Compare
0935cf4 to
291df55
Compare
|
fixed in 291df55 — span=be531ed8177b (failed Git reads can appear as an empty diff).
|
|
fixed in 291df55 — span=e61d862bc701 (duplicate
|
|
fixed in 291df55 — span=da7b7242fb1b (unlabelled ahead/behind counts). The The BLOCK's evidence gaps are filled in the same round: the description now carries stills of the clean tree, a non-repository, a stopped workspace (whole-panel error), a failed History read, a selected file with an empty diff, a diff cut at 256 KB, and the hover titles. All are rendered from this head's real |
|
fixed in 291df55 — span=8cda78be00fb (status letters have no legend). Each status letter now has a |
|
fixed in 291df55 — span=ada4151c629d (branch name looks like a control). The branch renders as plain text, without the |
|
span=e87ba78139ca covers two findings in
|
|
span=fca05a33a61a covers two findings in
|
|
Design Review (PASS) punchline, answered: who carries the Kiro Cloud follow-up. It has an owner and the code exists. The |
|
First Principles (PASS) punchline answered: what This is intentional, and the description now says so (Backwards compatibility). The panel needs each untracked file as its own row so it can show and diff it, so |
|
rebutted span=078b9c7f01fb: shorten emptyDiffListed.
|
|
rebutted span=2759b2bf112e: give history rows plain styling with no hover highlight.
|
|
fixed in a899077. span=743cad2faff2: the Git panel drafted its requests in a fresh chat not bound to the remote workspace. Confirmed and closed as suggested. |
|
fixed in a899077. span=c3ffd8c5b753: inline PEM openers bypassed private-key masking. Confirmed and closed as suggested. |
|
fixed in 1573936. span=be531ed8177b: cached diffs survived a refreshed repository status. Confirmed and closed as suggested. The diff query in |
|
Windows fix for the guest Git reads (in 1573936, Windows backend shards 1, 2, 3, 6 and 8 failed on fee8541 in 15 tests this PR added. All 15 now run on Windows with no new skip. There were two causes:
Tests, all running on every platform: |
|
fixed in f64c0f2. span=e6991c559ca6: a staged executable-bit change disappeared from the remote diff under core.fileMode=false. Confirmed and fixed as suggested. Where git cannot trust the filesystem mode bit (core.fileMode=false) or symlinks (core.symlinks=false), |
|
fixed in b1fe0ce. span=464a82c52865: group-only execute permission produced a false Git mode change ( Confirmed and fixed as suggested. |
|
acknowledged span=464a82c52865: HEAD-based CRLF detection hides a staged renormalization ( Not changed in this round; the adjudicator downgraded it ( |
|
fixed in 97da38e. span=f0ee454cd4e3: the error-state "Ask the agent" link went to the wrong chat. Confirmed and fixed. |
|
fixed in 5d42e44. span=e6991c559ca6: the CRLF safeguard read HEAD, not the index, so a staged renormalization showed no diff. Confirmed and fixed as suggested. |
|
fixed in f9748e3. span=e6991c559ca6: lossy decoding hid non-UTF-8 file edits ( Confirmed and fixed as suggested. |
|
fixed in 3d3157a. span=8c86f99f82f4: a pure rename or mode change of a binary file showed "Binary files ... differ" ( Confirmed and fixed as suggested. |
|
fixed in f162695. span=93a30e36bb6d: reordered repeated lines made the gateway's diff quadratic ( Confirmed and fixed as suggested. |
|
acknowledged span=e6991c559ca6: a staged removal ( Not changed in this round; the adjudicator downgraded it ( |
|
fixed in ace301d. span=c3ffd8c5b753: the pair-count pre-check is gone. |
|
acknowledged, not changed. span=be531ed8177b: downgraded by adjudication. It needs a guest worker from before this PR's NUL status support, and only a C-quoted name on one row fails. It clears once a later message reinstalls the worker. No change in this PR. |
|
fixed in 47da56f. span=c3ffd8c5b753 (multiline filename masking): NUL status redaction now keeps a status record's |
|
acknowledged, not changed. span=e6991c559ca6 (capped index blob): downgraded by adjudication as disproportionate. It needs a staged blob over 256 KiB whose first CRLF lies past the cap, while HEAD and the worktree copy are both under it. The panel is read-only and the git CLI still shows the change. |
|
fixed in 333ed3c. Second unified-diff engine: the matcher is gone. |
|
Hold at c0adc9e.
All five AI lanes PASS on this head. Their notes (CRLF equivalence test, the unused I did not run anything locally, and I did not complete a line-by-line review because the head has to change. — crew-pr-reviewer (r137) |
- Withhold a footerless PEM key whose opener follows a field prefix (`key: -----BEGIN ...`): openers and footers are now found anywhere in a line, so the key fails closed instead of reaching the patch (GPT 6.1). - Stage the panel's "Draft a request" prompts in this chat's own composer (`stageToMainComposer`, via a new `AskAgentButton` `onStage`), not a fresh chat that is not bound to the remote workspace (Opus 5.5). - Re-read a file's diff on reopen and on return to the tab (`staleTime: 0`), so a patch the agent has committed no longer stays on screen (GPT 6.1). - Windows: a capped Git read ends its writer by closing its end of the pipe; the read runs without a `timeout` wrapper there (one on PATH may be System32's unrelated wait command); and a read past its deadline ends its whole process tree with `taskkill /T`, since git.exe is a launcher and Windows has no group signal. - Tests: the guest Git tests write LF fixtures explicitly, which Windows text mode wrote as CRLF.
Sensitive change review
|
Problem / Motivation
Goal: Let the Git tab of a chat that runs in a remote session environment show that workspace's own repository (branch, changed files, per-file diff and recent history), read-only.
A chat on a Coder workspace (#19833) works in the guest's checkout, but the side panel's Git tab can only read the gateway's local project. For a remote chat it shows a placeholder instead, so the user cannot see what the agent changed, which branch it is on, or whether it has committed, without asking the agent or opening a terminal.
Why it matters
Reviewing the agent's changes is the main reason to open the Git tab. In a remote chat that review currently means typing
git statusandgit diffinto a terminal by hand. A read-only view of the guest's checkout gives remote chats the same review loop local chats already have.Not a goal
What changed (motivation → approach → change)
A remote chat's Git tab now shows the guest workspace's repository: the branch with its ahead/behind counts as plain read-only text, one coloured status letter per changed file, a click-to-open diff for each file, and the last 50 commits. Nothing in it can change the repository.
The panel reads through the browse endpoint the remote Files tab already uses, so it gains no new route and no new credential. The guest runs fixed-argv, read-only git in its own checkout, and a diff path outside the workspace is refused. Every git read runs under coreutils
timeout, as the base'srun_commandnow does (one shared_under_timeoutwrap and_unwind, used by both), so anything git starts is stopped with it when the 30-second timeout fires; the guest calls no kill primitive. With filters, fsmonitor, textconv, external diff, signature checks and submodule recursion all switched off, that is defence in depth for whatever git starts that this list does not name.website/src/pages/chat/RemoteGitPanel.tsx(new),ActivityViewer.tsx,SidePanel.tsxgit_failedresult is always an error, even with no diagnostic text; each diff opens under its row, History dates are formatted in the dashboard's language from the guest's unix seconds, and every Ask the agent link drafts a request without sending itwebsite/src/components/GitPanel.tsx,website/src/components/ui.tsx,website/src/components/AskAgentButton.tsxGitPanelexportsstatusColorandrelativeTime, so both panels colour letters and word commit dates from one source;AskAgentButtongains optionalprompt,title,accentandonStageprops, so the panel's "Draft a request to the agent…" links reuse its offline gate and stage their draft in THIS chat's composer (stageToMainComposer, the channelSideChatuses), the chat bound to the workspace, rather than the error hand-off's fresh chat (existing callers unchanged);PanelSectionHeaderalso accepts a translated count string ("14 or more")website/src/apichatSlotEnvironmentGit(slot, op, path)and theRemoteGitResulttypewebsite/src/i18nsessionEnvironments.remoteGit.*strings in all 13 catalogs (the commit-count labels are plurals, registered inpluralKeys.json)src/kiro_crew/remote_session/workspace_tools.pygit_status(NUL porcelain, every untracked file),git_log,git_bodies(theHEADblob vials-tree/cat-file, which runs no filter, and the worktree file read directly, never a patch; an untracked file has no old body; an unborn branch has none either; the path's parent directory is confined and a symlink's body is its link text; a gitlink is itsSubproject commitline; a directory, including an untracked nested repository, isgit_failed; binary bodies are flagged; the HEAD blob is streamed and kept to the read cap, never buffered whole; over the cap, the reply is marked truncated and carries no body, so the panel says "This diff is too large to show. Only its mode or rename lines appear, if any." (with any mode, rename or new/deleted file lines), as the local panel does; a gitlink whose index entry was replaced by staged files is refused as a directory before git builds its patch, and every body read (blob, index listing, submodule summary) is streamed to the cap; a gitlink replaced by a file or symlink is read with the same bounded worktree read; a worktree file git would store with LF (text,text=auto,eol,core.autocrlf) is compared with CRLF folded to LF, except that, like git's own check, automatic conversion leaves a file whoseHEADblob already holds CRLF unchanged);--no-lazy-fetch(andGIT_NO_LAZY_FETCH=1) so a partial clone's missing object isgit_failed, never fetched through a configured transport; on git older than 2.44, which lacks the flag, a partial clone still lists status (with--no-renames) and history but refuses file bodies, and those reads run withGIT_ALLOW_PROTOCOLempty, so a read that would need a missing object fails instead of fetching;core.hooksPath=/dev/nullandGIT_OPTIONAL_LOCKS=0, as the base'sgit_statusnow does, so no hook runs and the index is never refreshed;core.fsmonitor, pager, external diff, textconv andlog.showSignaturedisabled, and every filter driver the repository configures blanked for the read, as the base'sgit_statusdoes (a driver that cannot be named stops the read); status and the gitlink read pass--ignore-submodules=dirty, so git never runs inside a submodule whose own config could name filters; a non-repository is a state, a failed git call is an error withcode: git_failed; every git read runs through_run_groupedunder coreutilstimeout -k 5 30, which signals the read's whole process group on expiry, on a stdout cutoff and on unwind (the base removed_kill_groupand the guest's kill-site exemption, so the guest adds no kill primitive); rename diffs writerename from/rename towith no made-upsimilarity indexsrc/kiro_crew/coder/session_browse.py,src/kiro_crew/security_posture_sinks_gateway.py,src/kiro_crew/dashboard/handlers/session_environments.pyREAD_OPSadmits the two new ops; the gateway runs the output and error text of `git_statussrc/kiro_crew/git_no_index_diff.py(new),src/kiro_crew/dashboard/file_api/editor.py,src/kiro_crew/dashboard/handlers/files.pygit diff --no-indexof two masked bodies, moved out ofapi_file_diffunchanged (same argv, temp-dir handling, timeout and failure rule) so both panels use one spawn;editor.pycalls it and keeps its own header, and thefiles.pyfacade binds it for the editor owner as it does its other importsdocs/system-specs/modules/providers.md,docs/feature-map/README.md_run_groupedThe spawn audit's entry for the old git reader (
workspace_tools.py::_git_status) becomesworkspace_tools.py::_run_grouped, beside the unchangedrun_commandentry, andworkspace_tools.py::_stop_treejoins them: on Windows only, it runstaskkill /T /Ffrom the system directory on a read the guest itself started, so a read past its deadline leaves no orphanedgit.exe. All three are guest-only code that cannot import the gateway sandbox. The gateway-side entrydashboard/file_api/editor.py::_diff_redacted_bodiesmoves with its spawn togit_no_index_diff.py::no_index_diff: same argv, no new spawn site.Windows. A Git read that reaches the size limit closes its end of git's output pipe, so git exits at its next write on every platform. On win32 the read runs without the coreutils
timeoutwrapper (thetimeouton PATH may be System32's unrelated wait command), and its deadline ends the whole process tree, sincegit.exeis a launcher and Windows has no group signal. The guest Git tests write LF fixtures explicitly and all run on Windows; details in the PR note on 1573936.Base.
main(484d7378a8), after credentialed git (PR #21256) and Sprites/boxd (PR #21257) merged. The Git panel does not depend on Fargate or Kiro Cloud. Its Kiro Cloud handling (the cloud-sandbox notice and the placement re-read) is left to the Kiro Cloud PR, which has no counterpart on this base. Since the base's UI withholds gateway-backed tabs in a remote chat, the Git tab is taken off that list here: a remote chat's Git tab rendersRemoteGitPanel, never the gateway checkout. The panel's error notices keepErrorNotice's agent hand-off but stage it in this chat's composer (a new optionalonStage), since a fresh chat's agent could not reach the remote workspace.Developer flag. Like the rest of Session Environments, the panel is reachable only with
KIROCREW_DEV_MODEon. With it off, a chat bound to a remote profile reads as local through the choices gate, so the Git tab shows the localGitReposPaneland everygit_status/git_log/git_diffbrowse request answers409 not_remotewithout reaching a guest (test_the_git_views_are_unreachable_with_the_developer_flag_off, which fails with the gate's flag check removed).Why the Git views are redacted although
readis not. The Git views show text thatreadcannot reach. A diff's removed lines are content no longer on disk, such as a credential the agent wrote and then deleted. Commit subjects and author lines in History are not files at all. So redactinggit_status|git_log|git_diffcovers a disclosure path that the rawreadop (unchanged from #19833) does not. Diff bodies are also redacted, which matches the local panel's file diff (dashboard/file_api/editor.py,_diff_redacted_bodies).Sensitive change
One file on the Sensitive Change Review list:
src/kiro_crew/security_posture_sinks_gateway.py(watched throughsecurity_posture_*.py). Since the base splitsecurity_posture.pyinto a facade (#23357), the registry rows live there; this PR does not touchsecurity_posture.pyitself. The change is a single seven-line entry appended to_GATEWAY_SINKS(part ofsecurity_posture._REDACTION_SINKS), namingcoder/session_browse.pyas a redaction egress sink, byte-identical to the entry on earlier heads. Nothing else in that file changes.test_security_posturerequires every module that calls the shared redactor to be registered there, so the new gateway redaction of the remote Git views cannot land without it. The entry adds a row to the security posture panel's list of redaction egress paths, and no rule, scanner or default changes. The entry is this PR's own; nothing sensitive is inherited from the base.Paste-ready review for the PR author (an approval names one head and does not carry across commits, so a later push needs it re-posted):
Backwards compatibility
Compatible: the Git tab of a local chat still renders the local
GitReposPanel;git_statuskeeps its op name and result keys; the two new ops are additive;run_commandis untouched.The
git_statusoutput changes from newline to NUL records, and a timeout returns{git: false, code: "git_failed"}instead of a tool error. It also lists untracked files individually (--untracked-files=allin place ofnormal), so the panel can show and diff each new file. As a result, the archive warning counts every file inside a new untracked directory where it used to count the directory once; that number is the files the archive would actually lose. A submodule whose only change is files inside it is not listed, because the reads never look inside a submodule; a submodule whose checked-out commit moved is. When the guest cut the list at its 256 KB read cap, the warning drops the partial last record and says "at least N uncommitted files". When that list passes the guest's 256 KB read cap, the panel drops the cut final record and says the list is incomplete. Its readers:Reader: src/kiro_crew/coder/session_browse.py:unsaved_work -- chat (archive warning) --
summarize_unsavedsplits on NUL when present and on newlines otherwise, and counts a rename as one file;test_unsaved_warning_understands_nul_statusReader: website/src/pages/chat/RemoteGitPanel.tsx:parsePorcelain -- chat (side panel) -- new in this PR, parses the NUL form and falls back to newline records from guest files an earlier build installed;
RemoteGitPaneltests inRemoteFilesPanel.test.tsxGuest files are rewritten only when an agent runtime starts, so a guest prepared by an earlier build can still answer
git_log/git_bodieswithop must be …, and it never serves a raw patch to this build;_askreinstalls the current files once on that reply and never retries a second time (test_a_worker_without_the_read_op_is_reinstalled_once,test_a_refused_op_after_reinstalling_is_returned_not_retried).Tests
test/test_remote_git_credential_isolation.py: textconv set up in the repository is confined at spawn; untracked files get real addition diffs; literal paths with spaces and Unicode reach the tracked diff; the unsaved-work warning reads NUL status; a modified tracked symlink diffs as the link, also when it names a file outside the workspace;..,app/../../outside.txtand a symlinked parent pointing outside stay refused.test/test_coder_session_browse.py: credential-shaped values in a status path, a log subject, a diff body and error text come back redacted with NUL and newline structure intact, a PEM body is masked before the patch is built, a key with no footer is withheld through EOF even when its opener follows a field prefix (key: -----BEGIN …), andreadis unchanged; guest files that answerop must be …are reinstalled exactly once; a refusal after the reinstall is returned, not retried; other browse errors never reinstall.test/test_remote_git_channel_bounds.py,test/test_remote_git_proxy_admission.py: subprocess failures are errors, not repository states; only git's own "not a git repository" is the non-repository state; unborn-branch history is empty and its diff includes staged files (SHA-1 and SHA-256 repositories); status paths diff correctly from a nested workdir.test/test_remote_command_lifetime.py:test_a_timed_out_git_read_stops_under_timeout_then_reaps[git_status|git_log|git_bodies]runs each read undertimeout -k 5 30and stops then reaps it;test_a_timed_out_git_read_takes_its_whole_group_with_itruns a real child that outlives the read and shows the timeout takes it down (with thetimeoutwrapper removed, all four fail).test/test_coder_session_launch.pyandtest/test_remote_git_panel_bodies.py(the body reads, split out so neither file passes the 2,000-line cap):git_logandgit_diffthrough the browse mode, a diff path outside the workspace refused, a repository textconv never run by the diff view, a repository filter driver (clean/smudge,required=true) never run by status, diff or history, a filter driver defined only in a submodule's own config never run by status or a diff of the submodule; a random PEM wrapped at 32 columns with a middle line deleted shows no key line in the gateway's diff (the test first shows git's own patch carries those lines and the redactor, read a line at a time, leaves them; with the body redaction skipped it fails); an untracked nested repository isgit_failed, not an empty diff; a blobless partial clone whose remote is anext::transport writing a marker never runs it from bodies, status or log, and its missing blob isgit_failed(with the flag and env var removed, the marker appears); git without the flag still lists status and history in a partial clone but refuses bodies, and never runs the transport even for a git that ignoresGIT_NO_LAZY_FETCH; an over-cap file returns no body and a truncated diff with no hunks; a submodule replaced by an over-cap file is bounded and truncated like any file; atext=autoorcore.autocrlffile whoseHEADblob already holds CRLF shows a one-line edit as one line; (POSIX only, as guest workspaces are) a mode-only change (chmod +x) renders git'sold mode/new modelines, matchinggit diff, andcore.fileMode=falsehides it; a staged rename diffs against its source withrename from/rename toand the real hunks, with the source confined like the path; a PEM block with no footer, including an indented one in a complete file, is withheld from its BEGIN line on, on top of the whole-body redaction (the test first shows the shared redactor alone leaves the indented key lines); 64K repeated short lines diff in well under two seconds; a history read with a commit subject twice the read cap, and a status read with an untracked list twice the cap, are streamed to the cap instead of buffered; a guest withtimeoutbut nogitreports "git is not installed" for every op; a gitlink replaced by staged files, on disk or removed, is refused with nodiffspawned and no index listing buffered; and a driver name that-ccannot express stopping the read asgit_failed.test/spawn_audit_helpers.py(read bytest/test_spawn_audit.py): the_run_groupedaudit entry replaces_git_status, and the file-diff entry follows its spawn togit_no_index_diff.py::no_index_diff.test/test_coder_session_browse.py(shared diff): the panel's hunks come fromno_index_diffover the masked bodies with the file panel's argv (test_the_panel_takes_its_hunks_from_the_shared_git_diff_of_masked_bodiesandtest_the_panel_diff_uses_the_file_panels_git_argvfail if the panel stops using it); reversed repeated lines and swapped neighbours diff in under two seconds; a patch with no hunks renders binary or the header alone; a git timeout gets the over-cap reply and any other failure serves no patch.test/test_api_file_diff.pypasses unchanged.test/test_session_environment_handlers.py: withKIROCREW_DEV_MODEoff, a bound chat's three Git reads answernot_remoteand never reach a guest (fails with the choices gate's flag check removed); the browse endpoint forwards a rename source.website/src/test/sidePanelEnvironmentPlacement.test.tsx: a remote chat's Git tab reaches the Git view with the workspace name and no withheld notice, a local chat's with none (the remote case fails withgitput back on the withheld list).website/src/test/RemoteFilesPanel.test.tsx(RemoteGitPanel): NUL porcelain with literal filenames and rename/copy sources, and newline status from older guest files; a cut-off status list drops its partial final record and says the list is incomplete; the branch title, the ahead/behind label and each letter's title, name and colour; an untracked row's addition patch; the cut-off diff notice and its "Ask the agent for the full diff" hand-off (hidden while the gateway is unreachable), also for a cut reply whose shown part is empty, which never reads as no difference; a listed file with an empty diff; status, history and diff failures throughErrorNotice, each led by a plain sentence with git's text as detail and the agent hand-off kept, including agit_failedresult with empty diagnostics; the stopped-workspace sentence; a non-repository.website/src/test/ApiClient.refactor.surface.test.ts: the new endpoint.test_remote_git_channel_bounds.pyruns the history read on a signed commit withlog.showSignature=trueand a fakegpg.programthat would leave a marker, which never appears;RemoteFilesPanel.test.tsxcovers the "No upstream" pill, an unborn branch whose header is git's real## No commits yet on trunk...origin/trunk [gone], the row chevrons and the shortened notices. Round-5 additions: the history read sends unix seconds (%at) and the panel formats them with the local panel'srelativeTime, showing text from older guests verbatim; each diff opens under its own row; each Ask the agent link says it drafts and sends nothing; a commit date git accepts but JavaScript cannot represent (e.g.@9999999999999) is shown verbatim instead of crashing History; a cut status list makes the archive warning say "at least". Round-7 additions: rename and copy rows showold -> new(diffs still use the new path); the panel remounts per chat, so a selection never carries over;AskAgentButton's newpromptprop is tested inAskAgentButton.cov80.test.tsx.main484d7378a8): the remote, Coder, session-environment, sprites/boxd, redaction, workspace-file, file-API/file-diff and remote-git proxy/relay test files plustest_spawn_audit,test_security_posture, the files-facade composition contract and the gate files under-n 10(6,837 passed, 25 skipped); every Fast Gate script, diff-scoped to this PR's two commits (29/29); the Backend Lint job's scripts plus whole-tree isort, flake8 and mypy (14/14); Semgrep 1.78.0 with CI's configs against the base (0 findings); 287 frontend test files that render the panel,ErrorNoticeorAskAgentButton, plus the API client surface test (7,723 passed);tscandi18n:check. No added line names a/homeor/Userspath.mainthatmainhas since fixed:kiroUsageRefetchInterval.test.ts(fix(test): expect 'none' for API-key auth in the Kiro usage parser test #25944) and the macOS artifact-icon settles (Flaky: TestIconGenerationCoalescing settle wait times out on macOS #25895, fe68d8e). This head includes both fixes.test/test_sprites_boxd_failures.py::test_window_size_and_raw_mode_on_a_real_ptycame in with feat: add Fly.io Sprites and boxd session environments #21257, which merged with the macOS suite skipped, and it failed on this PR's earlier macOS runs; this PR touches neither that test nor the code under it.Manual verification
Screenshots / video
Rendered from this head's real
RemoteGitPanelunder the repo's Vite config on 127.0.0.1, withchatSlotEnvironmentGitstubbed (no gateway, no workspace). The stubbed checkout is two commits ahead of and one behind its upstream, with a modified file whose name has a space, an added file, a rename, a deletion and an untracked Unicode file.Branch and ahead/behind counts, one coloured status letter per file, and history with dates in the dashboard's own language:
Selecting the modified file opens its diff against
HEADdirectly under its row:An untracked file shows as an addition:
What the hover titles say. Headless Chromium draws no native tooltip, so the caption under the panel lists the title and accessible-name values read from the rendered page:
A clean checkout, the most common state after the agent commits:
A file whose diff is empty though status lists it, and a diff the guest cut at 256 KB with its hand-off (the patch scrolls inside the panel):
A status list cut at the same cap: the partial last row is dropped, the count reads "14 or more", and the note ("Some changes are not shown.") offers to ask the agent for the full list. Each change row ends in a chevron, like the Files tab's folders. The selected row in any list shows its status as text (e.g. "Modified") beside the hover title:
The working directory is not a Git repository, with a hand-off to ask the agent to clone or create one:
A branch with no upstream shows a muted "No upstream" label in place of the ahead/behind counts:
Failed reads: the whole panel when the workspace is stopped, and History alone (with no count) when only the log read fails, led by a plain sentence with git's text below it, each with the agent hand-off:
Light theme
Related Issues
Part of #10433
no linked issue: this PR closes nothing; #10433 stays open until the whole Session Environments stack lands.
Checklist
feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)