feat(transfers): progress and cancel for SSH uploads and all remote downloads by Chihen-Tai · Pull Request #23849 · stablyai/orca

Chihen-Tai · 2026-09-29T09:52:39Z

Stacked on #16107 (runtime upload progress). This branch is current main + a merge of #16107 (ae66b3fbd3, resolved against main's owner-routed target and the shared streamExternalFileSlices streamer) + one commit with this PR's change (43c77436bb). Review git show 43c77436bb; the PR diff shrinks once #16107 lands.

Reworked after the relay removal (#27214, #27215). SSH workspaces now run on the host's managed runtime, so the earlier SSH-specific half (desktop-side SFTP/system-SSH upload progress, the rollback ledger, main-process download progress/cancel IPC) is gone. Everything now rides #16107's runtime transfer path.

ELI5

When you copy files to or from a remote workspace (an SSH host or a remote Orca server), Orca shows one progress panel: a row per item with bytes, a bar and a Cancel button. Before, only files dropped onto a remote terminal got a panel; explorer and editor drops and all downloads showed nothing until they finished.

What Changed

Before (main + #16107):

Dropping files onto a remote terminal shows feat(runtime): per-file progress and cancel for files dropped onto a remote workspace #16107's panel with cancel.
Dropping into the file explorer or editor of a remote workspace shows no progress and cannot be cancelled.
Downloads (explorer → Download, terminal "download & open") show nothing until the final toast and cannot be cancelled.
On an SSH workspace, the explorer Download and terminal "download & open" for a file went to the desktop-side SSH filesystem provider, which nothing registers since the relay was removed.

After:

Explorer, editor and terminal drops into a remote workspace all use the same panel, with per-row cancel.
File downloads from a remote workspace show the panel (bytes of total, bar, percentage, Cancel). Cancel stops the download, discards the temp file, and never overwrites the chosen destination. A download that finished before the cancel landed still ends with the usual "Downloaded … / Open" toast.
SSH workspace files download through the host's runtime, like every other remote workspace.

Mechanism:

UI: feat(runtime): per-file progress and cancel for files dropped onto a remote workspace #16107's terminal panel, its session store, heading and byte formatting move to components/transfer-progress/ and take a direction (upload/download). createUploadProgressPanel wraps feat(runtime): per-file progress and cancel for files dropped onto a remote workspace #16107's RuntimeImportProgressHandlers; runRemoteDownloadWithProgress wraps a download. Rows end from the transfer's result, not the click: "Cancelling…" until the result arrives, "remote state unconfirmed" after 15 s.
Uploads: no new transport code. Explorer and editor drops pass progress to importExternalPathsToRuntime, which already reports bytes over feat(runtime): per-file progress and cancel for files dropped onto a remote workspace #16107's fs:uploadProgress and cancels through fs:cancelRuntimeUpload. Local workspaces are untouched (their copy has no progress handlers).
Downloads: downloadRuntimeFile already pulls the file chunk by chunk in the renderer (files.readChunk). It now takes an optional transfer: it reads the size with files.stat (failure only means "bytes, no percentage"), counts each appended chunk (throttled to one update per 100 ms), and checks an AbortSignal before every chunk and before the final commit. Older servers that answer in one preview reply still show the panel and can be cancelled before the save. No main-process or wire change.
SSH download routing: the explorer prefers the runtime context for files (pickRemoteDownloadTarget); terminal "download & open" always calls downloadRuntimeFile, which still falls back to the SSH connection when the context has no runtime owner. Folder downloads keep main's existing SSH-only path.
Runtime cancel fixes (touch only feat(runtime): per-file progress and cancel for files dropped onto a remote workspace #16107's import loop): directories check the cancel before and after each create, so nothing new appears after a cancel and an empty folder cancelled mid-create is cleaned up; a source is marked cancelled only when the cancel is what stopped it, so a failure after the click is still reported.

Why

The maintainer's note on this PR: SSH uploads/downloads now share the runtime path with feat(runtime): per-file progress and cancel for files dropped onto a remote workspace #16107, so a second, SSH-specific pipeline would duplicate it. Reusing feat(runtime): per-file progress and cancel for files dropped onto a remote workspace #16107's channel, cancel registry and panel keeps one implementation.
Download progress and cancel stay in the renderer because the renderer already owns the chunk loop. Aborting the in-flight chunk would need the subscription-based abortable RPC per chunk; a chunk boundary is a cheap, safe cancel point for a read-only request.
Nothing new crosses the client/server wire, so older remote servers keep working.

Linked Issue

Fixes #16077 (together with #16107)

Visual Proof

Captured from the dev app (this branch) against an Ubuntu 24.04 SSH host served by its managed runtime (orcad), driven through CDP. Crops show only the panel.

	Upload (explorer drop)	Download (explorer → Download)
In progress
Cancel
Finished	(panel holds its outcome, then closes)

Two items	Terminal drop	Terminal after the drop

Testing

Automated (ran locally on this branch):

pnpm tc: pass.
check:code-quality:changed, oxlint on changed files, check:max-lines-ratchet, check:dead-classes, check:owner-routing-ratchet, verify:localization-catalogs|extraction|coverage: pass.
Changed/related suites (transfer-progress/, runtime/runtime-file-client-*, right-sidebar/FileExplorerRow.actions, terminal-pane/terminal-drop-*, terminal-runtime-drop-upload, terminal-pane-element-file-drop, main/ipc/runtime-upload-*, filesystem-mutations-runtime-upload): pass.
New/updated tests: download progress against the remote size, unknown size, cancel between chunks (temp discarded), cancel during the final append (nothing committed), older-server one-reply download, an SSH workspace file downloading through its runtime instead of the SSH connection, explorer download target choice, the download panel (dismissed dialog, success, cancel, failure, finish-before-cancel), the tracker throttle, and the runtime cancel fixes above.
A wider run (src/main/ipc, src/renderer/src/{runtime,lib,components/terminal-pane,components/editor,...}) has 29 failures in files this PR does not touch; the same files fail on clean main on my machine (node:sqlite unavailable, a BrowserWindow mock, timing tests).

Manual, macOS → Ubuntu 24.04 SSH host on the managed runtime (dev app, driven through CDP):

Scenario	Result
Explorer drop, 286 MB file	Bar climbs, panel closes after its outcome; remote sha256 matches
Drop a file + a folder, cancel the file mid-upload	File row reads "Cancelled", its `.orca-upload-*` temp is removed on the host; the folder finishes and both files' sha256 match
Terminal drop	Panel, then the remote `.orca/drops/` path is pasted; sha256 matches
Explorer → Download, 286 MB	Panel, then "Downloaded … / Open"; local sha256 matches
Cancel mid-download	"Download cancelled"; the temp file is removed and nothing is written at the destination

Not run by hand: editor drop and terminal "download & open" (same upload/download functions as above, covered by unit tests). The dev app needed out/orcad-template from a release build to connect at all; without it every host reports "isn't supported" (main's dev setup, unrelated to this PR).

I manually tested these changes locally
Automated tests added/updated, or explained why not below

AI Disclosure

Implemented and tested with Claude Code (Claude Opus 5.5).

Agent skill upstream boundary

Not applicable, or this change follows docs/reference/agent-skill-sharing-upstream-boundary.md and copies or mechanically translates no upstream skill-installer source, tests, fixtures, registry entries, path tables, comments, or documentation.

Notes

Cross-platform / SSH / folder workspaces: no platform-specific code; uploads and downloads route by the workspace owner's runtime target as before.
Known limits:
- Download cancel takes effect at the next chunk boundary (an in-flight chunk read finishes first).
- Folder downloads still use main's SSH-provider path, which has no provider on managed-runtime SSH hosts; the runtime has no recursive download. Out of scope here.
- Explorer and editor drop panels show in every workspace; terminal drop panels stay scoped to their workspace as in feat(runtime): per-file progress and cancel for files dropped onto a remote workspace #16107.
- When a runtime import is cancelled, feat(runtime): per-file progress and cancel for files dropped onto a remote workspace #16107's root cleanup still deletes the import root recursively (behavior from feat(runtime): per-file progress and cancel for files dropped onto a remote workspace #16107/main, unchanged).

Checklist

This PR is small and focused
I explained what changed and why (ELI5, the user-facing before/after, the mechanism, and why over the alternatives)
Before/after screenshots or videos attached for UI changes, or N/A with reason
Self-reviewed for correctness, security, and performance
Cross-platform, SSH/remote, and path/shortcut impact considered (or N/A)
pnpm lint, pnpm typecheck, pnpm test, and pnpm build pass (or CI will cover; local preferred)

🤖 Generated with Claude Code

Runtime-environment imports read the entire file into memory and base64-encoded it before sending, so peak main-process memory was ~2.3x the file size. A 25 MB per-file / 100 MB per-drop ceiling existed only to keep that from exhausting the heap, and it was checked right after lstat — so dropping a 40 MB recording failed instantly with no bytes moved. The socket already lives in main, but the chunking loop lived in the renderer, so the whole base64 payload crossed IPC only to be sliced and passed back through main. Move the byte pump into main, next to the file handle and the socket: one open handle per file, 384 KiB slices (512 KiB on the wire, matching the previous chunk size), sent through the existing files.writeBase64Chunk method. Staging now records byteLength instead of file contents. The renderer keeps deconflict, commit, rollback and cleanup, and never sees file bytes. Peak memory per upload drops to one slice. The ceilings become user safety limits rather than memory guards, raised to 2 GB / 8 GB until the drop UI can show progress and cancel a running upload. No protocol change: files.writeBase64Chunk already existed and was already used by this path for payloads over 512 KB. Small files now use it with append: false, which is exactly what files.writeBase64 does internally, so mixed client/host versions are unaffected. Symlink rejection, O_NOFOLLOW, realpath containment and the stat identity check all move to upload time and now share one handle for the whole file, so every slice comes from the same inode. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Dropping a large file onto a remote terminal gave no feedback until the transfer finished or failed, so a slow upload looked like a hung one. That became easy to hit once streaming removed the 25 MB per-file import cap. The chunk loop now reports bytes acknowledged by the runtime, coalesced to at most one update per megabyte or 100ms so a multi-gigabyte file does not flood IPC. The renderer sums staged byte counts up front and tracks committed files plus the file in flight, so the drop toast shows one figure for the whole drop rather than per file. Client-local only: main to renderer, no RPC params or stream frames change, so there is no wire-compatibility surface. Cancellation is deliberately excluded; it needs an abort path threaded into the streamer plus temp-file cleanup, and belongs with UI that can trigger it. Fixes stablyai#16077 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Replaces the single-line progress toast with a panel: a header carrying the aggregate percent and a collapse toggle, then one row per dropped source showing name, transferred-of-total, a bar, percent, and a cancel control. Cancel is real rather than decorative. Each dropped source streams under one id that is both its progress key and its abort handle, so cancelling a row stops that source and leaves the rest of the drop running. The streamer checks between slices, which leaves a well-formed partial temp file for the existing cleanup to remove; nothing lands at the final path. A cancel that arrives between two files of a source is remembered so the next file aborts instead of the click doing nothing, and cancelled sources are excluded from the failure summary because a cancel is not a failure. Both figures in a row scale to the total's unit: formatting them independently rendered "900 / 32.5" when a file crossed a unit boundary. Per STYLEGUIDE, cancel is a back-out rather than a destructive action, so it stays a quiet ghost control with no colour, and the bar uses the existing Progress primitive's `primary` fill rather than a new hue. Splits the drop flow into terminal-runtime-drop-upload and terminal-drop-paste; the host file had grown past the max-lines limit. Fixes stablyai#16077 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Cancelling every file removed the session immediately, so the panel vanished mid-gesture with its header still reading "Uploading 2 files" — the one moment the user most needs to see what happened. Finishing now settles the session instead of deleting it. The header switches to the outcome (cancelled, failed, uploaded X of N), the percent and collapse toggle drop away since nothing is moving, and the panel holds for 1.2s before fading out and dismissing itself. Reduced-motion skips the fade but keeps the hold, so the outcome is still readable. Dismissal moves from the drop flow to the panel, which owns the timing; only the error path still tears it down at once. Fixes stablyai#16077 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Collapsing the file list left the header hanging where the expanded panel's top edge was, with dead space below it, instead of dropping to where a single-line toast sits. Sonner caches each toast's height and recomputes it only when the toast's element identity changes — `toast.jsx` is in that effect's dependency list. Our panel re-renders internally from its own store, so the cached height stayed at the expanded size and the shrunken content was top-aligned inside it. Collapse state moves into the session store and toggling re-issues toast.custom under the same id, which changes the element identity and makes sonner re-measure. Keeping the flag in the store is what makes the remount safe: local component state would reset on every toggle. Fixes stablyai#16077 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Collapsing the file list added a second panel rendering the same session instead of updating the first, so two identical cards ticked along together. sonner's toast.custom mints an id, then spreads the caller's options over it: const id = data?.id || toastsCounter++ this.create({ jsx: jsx(id), id, ...data }) return id Passing `id: undefined` therefore reaches create() as an explicit undefined, which mints a second id internally while custom() returns the first. The stored id never matched the registered toast, so re-issuing under it found no existing toast and added another. The id key is now omitted entirely on the first publish and only supplied on re-issue. A test pins that the first call carries no id key at all, since passing undefined reads as harmless and is not. Fixes stablyai#16077 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

…t jump An unstyled sonner toast is content-sized, so the expanded panel was as wide as its longest file name and the collapsed header shrank to fit "Uploading 2 files". Collapsing therefore moved the left edge as well as the bottom, which read as a jitter rather than a fold. The panel now takes the Toaster's own --width, so both states occupy the same box and only the height changes. File names are clipped inside that box instead of widening it. Fixes stablyai#16077 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Collapsing swapped ChevronUp for ChevronDown, which replaces the DOM node, so there was nothing to tween and the arrow flipped in a single frame. One ChevronDown now rotates 180deg over 200ms. The rotation survives the toast re-issue because sonner keys the list item by toast id and only swaps its jsx, so React reconciles the same element rather than remounting it. motion-reduce drops the transition. Fixes stablyai#16077 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

"Uploading 2 files" reads as a local copy. This panel only ever appears for a drop onto a remote workspace, so it now says "to runtime", matching the wording the old single-line toast used. The cancelled and failed lines stay short: once nothing landed there, the destination is no longer the point. Fixes stablyai#16077 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Review follow-ups on the import ceilings. Staging and upload are separate IPC calls, so a source could be replaced or grown in between and the streamer would take the new size as authoritative — transferring a file the ceilings had already rejected, and invalidating the per-drop aggregate. The staged byteLength now rides the upload request and a mismatch is refused before any chunk is sent. formatByteCeiling rounded, so 2 GiB + 1 B rendered "2.0 GB" against a "2 GB" limit and the error read like a broken check. It now rounds up, so anything over the ceiling renders strictly greater than it. Symlink tests are skipped on Windows, where symlink() needs elevation or Developer Mode. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

…ty drop Review follow-ups on the drop panel. Electron does not order webContents.send against an invoke reply, so a final progress event can arrive after completeFile and be counted a second time, jumping the bar ahead. The tracker now only accepts progress inside an explicit per-file window that completeFile closes. onStart still fires when every source was skipped, so a drop that staged nothing flashed an empty panel; it now returns before creating one. releaseRuntimeUpload was a bare `void` on a promise, which surfaces as an unhandled rejection if the IPC fails during cleanup — it now carries the same `.catch(() => {})` the sibling cleanup calls use. Comments trimmed to the one-line rule in AGENTS.md. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

…-progress Picks up the review follow-ups on the base branch: staged-size enforcement, the rounding fix for over-limit errors, and the Windows symlink test guards.

The ceiling lived only in staging, and the upload IPC takes the staged size as optional — so the limit held only for callers that had actually staged. The streamer now checks it itself, independent of whether a staged size was supplied. Both ceilings and their formatter move to runtime-import-limits so staging and the streamer share one definition rather than drifting. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

…-progress Picks up the per-file ceiling check at the streaming boundary and the shared runtime-import-limits module.

…ings truncate() sets a logical length but does not guarantee a sparse file, so on NTFS the over-limit fixtures could allocate two to three gigabytes on Windows CI to prove a comparison. The ceiling tests now mock runtime-import-limits down to kilobytes and use small real files, and the formatter's one-byte-over case moves to a pure unit test on formatByteCeiling where no file is needed at all. Largest fixture in these suites drops from 3 GiB to 3 MiB. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

…op-upload-progress

…rows Headings now pass count so i18next picks the plural form, with named placeholders. Drop-handler success mocks settle their row before finishing, and the runtime file client harness stubs cancel/release so progress-enabled imports resolve.

Copilot

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

greptile-apps · 2026-09-29T09:57:10Z

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge; no new actionable finding or outstanding previous finding remains.

Findings

Cancel still publishes the file ▶
Closed-window coverage was removed ▶
Cancel hides download errors ▶
Cancel buttons leave the screen ▶

Summary

The PR extends the runtime upload progress panel to explorer, editor, and terminal drops, with per-item cancellation. It adds renderer-side download progress and cancellation and routes SSH file downloads through the owning runtime.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  A[Explorer, editor, or terminal drop] --> B[Runtime import]
  B --> C[Transfer progress panel]
  C --> D[Cancel selected upload]
  E[Remote file download] --> F[Renderer chunk loop]
  F --> C
  C --> G[Cancel before download commit]

_{Reviews (23) · Last reviewed commit: "fix(i18n): give the upload heading its s..." · Reviewed by Greptile}

coderabbitai · 2026-09-29T10:00:20Z

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Last reviewed commit: 7f589613a92bbfe2c90928b7debeb07e6b12a618
Latest commit, not reviewed: 985b216

Use the following commands to manage reviews:

@coderabbitai resume to resume automatic reviews.
@coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

▶️ Resume reviews
🔍 Trigger review

Walkthrough

The change adds progress reporting and cancellation for remote downloads and uploads. Main-process handlers and SSH/runtime transfer paths report byte counts through IPC. SSH imports track created entries and roll back canceled uploads. Renderer code tracks transfer sessions and displays progress panels in file explorer, terminal, and file-drop workflows. Tests cover progress updates, cancellation, cleanup, rollback, and transfer-session behavior.

Pre-merge checks | 3 | 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Out of Scope Changes check		The PR adds SSH upload progress and cancellation, remote file and folder download progress and cancellation, shared transfer UI, and cancellation infrastructure. Issue [`#16077`] requires runtime droppe…	Split SSH upload, remote download, and cancellation work into separate pull requests, or link active issues that require these features. Keep this pull request limited to runtime dropped-file upload progress and supporting code and tests.
Docstring Coverage		Docstring coverage is 32.50% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 120 functions across 74 files. (2 skipped…	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Linked Issues check		The PR implements the coding requirements in [`#16077`]. Runtime upload streaming reports acknowledged byte progress with throttled IPC updates. Preload and web APIs expose the subscription. Staged file…
Title check		The title clearly summarizes the primary changes: transfer progress and cancellation for SSH uploads and remote downloads.
Description check		The description is complete and relevant. It includes the required explanation, change summary, rationale, linked issue, visual proof, testing details, AI disclosure, scope notes, and checklist. The s…

Full details: Out of Scope Changes check

Explanation

The PR adds SSH upload progress and cancellation, remote file and folder download progress and cancellation, shared transfer UI, and cancellation infrastructure. Issue [#16077] requires runtime dropped-file upload progress only. It explicitly excludes cancellation and does not require SSH uploads or downloads.

Full details: Docstring Coverage

Explanation

Docstring coverage is 32.50% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 120 functions across 74 files. (2 skipped: 2 unsupported.)

Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

coderabbitai

Actionable comments posted: 2

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Advanced

Run ID: 8309eb7b-1277-4fc2-9052-9643195067ec

📥 Commits

Reviewing files that changed from the base of the PR and between 31012ae and 60803e540a40f3c2359e5eaf4252812d4053acd0.

📒 Files selected for processing (70)

src/main/ipc/filesystem-download-folder.ts
src/main/ipc/filesystem-download-progress.test.ts
src/main/ipc/filesystem-download-transfers.test.ts
src/main/ipc/filesystem-import-ssh-progress.test.ts
src/main/ipc/filesystem-import-ssh-progress.ts
src/main/ipc/filesystem-import-ssh.ts
src/main/ipc/filesystem-mutations.ts
src/main/ipc/filesystem/filesystem-download-handlers.ts
src/main/ipc/filesystem/remote-download-sessions.test.ts
src/main/ipc/filesystem/remote-download-sessions.ts
src/main/ipc/runtime-upload-cancellation.test.ts
src/main/ipc/runtime-upload-cancellation.ts
src/main/ipc/runtime-upload-file-stream.test.ts
src/main/ipc/runtime-upload-file-stream.ts
src/main/ipc/runtime-upload-progress.test.ts
src/main/ipc/runtime-upload-progress.ts
src/main/providers/filesystem-provider-contract.ts
src/main/providers/ssh-filesystem-download-progress.test.ts
src/main/providers/ssh-filesystem-download.ts
src/main/providers/ssh-filesystem-file-upload.ts
src/main/providers/ssh-filesystem-provider-download-folder.test.ts
src/main/providers/ssh-filesystem-provider-sftp.ts
src/main/providers/ssh-filesystem-provider.test.ts
src/main/providers/ssh-filesystem-provider.ts
src/main/ssh/sftp-upload.ts
src/main/ssh/ssh-connection.ts
src/main/ssh/ssh-relay-session.ts
src/main/ssh/ssh-system-fallback.test.ts
src/main/ssh/system-ssh-file-binary-transfer.ts
src/preload/api/filesystem-api.ts
src/preload/api/fs-bridge.ts
src/renderer/src/components/right-sidebar/FileExplorerRow.actions.test.tsx
src/renderer/src/components/right-sidebar/file-explorer-row-file-transfer.ts
src/renderer/src/components/right-sidebar/useFileExplorerImport.ts
src/renderer/src/components/terminal-pane/terminal-drop-handler.test.ts
src/renderer/src/components/terminal-pane/terminal-drop-paste.ts
src/renderer/src/components/terminal-pane/terminal-native-file-drop.ts
src/renderer/src/components/terminal-pane/terminal-remote-file-download-open.ts
src/renderer/src/components/terminal-pane/terminal-runtime-drop-upload.ts
src/renderer/src/components/transfer-progress/TransferProgressPanel.tsx
src/renderer/src/components/transfer-progress/download-progress-panel.test.ts
src/renderer/src/components/transfer-progress/download-progress-panel.ts
src/renderer/src/components/transfer-progress/open-transfer-progress-panel.ts
src/renderer/src/components/transfer-progress/transfer-progress-format.test.ts
src/renderer/src/components/transfer-progress/transfer-progress-format.ts
src/renderer/src/components/transfer-progress/transfer-progress-heading.test.ts
src/renderer/src/components/transfer-progress/transfer-progress-heading.ts
src/renderer/src/components/transfer-progress/transfer-session-state.test.ts
src/renderer/src/components/transfer-progress/transfer-session-state.ts
src/renderer/src/components/transfer-progress/upload-progress-panel.test.ts
src/renderer/src/components/transfer-progress/upload-progress-panel.ts
src/renderer/src/hooks/useGlobalFileDrop.ts
src/renderer/src/i18n/en-runtime-required.json
src/renderer/src/i18n/locales/en.json
src/renderer/src/runtime/runtime-file-client-download-progress.test.ts
src/renderer/src/runtime/runtime-file-client-external-import.test.ts
src/renderer/src/runtime/runtime-file-client-test-harness.ts
src/renderer/src/runtime/runtime-file-client-types.ts
src/renderer/src/runtime/runtime-file-client.ts
src/renderer/src/runtime/runtime-file-import-client.ts
src/renderer/src/runtime/runtime-file-read-client.ts
src/renderer/src/runtime/runtime-file-upload-client.ts
src/renderer/src/runtime/runtime-upload-progress-tracker.test.ts
src/renderer/src/runtime/runtime-upload-progress-tracker.ts
src/renderer/src/runtime/ssh-upload-progress-client.test.ts
src/renderer/src/runtime/ssh-upload-progress-client.ts
src/renderer/src/web/preload-api/web-filesystem-api.ts
src/shared/remote-download-progress.test.ts
src/shared/remote-download-progress.ts
src/shared/runtime-upload-staging-contract.ts

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.

coderabbitai

Caution

Some comments are outside the diff and can’t be posted inline due to GitHub limitations.

⚠️ Outside diff range comments (1)

🟡 Minor · Check cancellation after the final chunk is acknowledged. · runtime-upload-file-stream.ts:114-127

src/main/ipc/runtime-upload-file-stream.ts:114-127
🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win

Check cancellation after the final chunk is acknowledged.

cancelSignal is checked before each slice, but the final sendChunk uses only the lifetime signal and is followed by no cancellation check. A user cancellation during that send can therefore let the upload resolve. The renderer then calls files.commitUpload and reports the file as imported.
Suggested fix
     if (afterReadStat.mtimeMs !== openedStat.mtimeMs || !isSameFile(afterReadStat, openedStat)) {
       throw new Error(`File changed during upload: '${displayPath}'`)
     }
+    throwIfCancelled(args.cancelSignal)
     return { byteLength: totalBytes }

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Advanced

Run ID: a26a9a1b-d1af-4283-aa68-02632077ee40

📥 Commits

Reviewing files that changed from the base of the PR and between 60803e540a40f3c2359e5eaf4252812d4053acd0 and a5bac704974829c1212c9bd8bed44512c9151eb5.

📒 Files selected for processing (15)

src/main/ipc/filesystem-download-progress.test.ts
src/main/ipc/filesystem-import-ssh-progress.test.ts
src/main/ipc/filesystem-import-ssh-progress.ts
src/main/ipc/filesystem-mutations.ts
src/main/ipc/filesystem/filesystem-download-handlers.ts
src/main/ipc/runtime-upload-cancel-ipc.test.ts
src/main/ipc/runtime-upload-cancel-ipc.ts
src/main/ipc/runtime-upload-cancellation.test.ts
src/main/ipc/runtime-upload-cancellation.ts
src/main/providers/filesystem-provider-contract.ts
src/main/ssh/sftp-upload.ts
src/renderer/src/i18n/en-runtime-required.json
src/renderer/src/i18n/locales/en.json
src/renderer/src/runtime/runtime-file-client-download-progress.test.ts
src/renderer/src/runtime/runtime-file-read-client.ts

🚧 Files skipped from review as they are similar to previous changes (1)

src/renderer/src/i18n/locales/en.json

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 8 remain after this review.

pullfrog

ℹ️ No critical issues — one minor suggestion inline.

Reviewed changes — the top commit 60803e5, which extends #16107's runtime upload panel to every remote transfer.

SSH upload progress and cancel — fs:importExternalPaths / fs:resolveDroppedPathsForAgent take per-source uploadIds; main measures each source locally, counts bytes off the SFTP/system-SSH upload streams, reports on fs:uploadProgress, and a cancel deletes a cancelled exclusive partial remote file.
Remote download progress and cancel — fs:downloadFile / fs:downloadFolder take a downloadId; main tracks bytes from fastGet, the system-SSH cat stream and a folder size pre-walk, reports on fs:downloadProgress, and fs:cancelDownload aborts.
One shared panel — the upload panel, session store, heading and byte formatting move to components/transfer-progress/ and take a direction; openTransferProgressPanel, createUploadProgressPanel and runRemoteDownloadWithProgress wrap each entry point.

ℹ️ Visual proof is still a TODO

The PR body's "Visual proof" section still reads "TODO: attach the upload, cancelled-upload, download and cancelled-download captures." The checklist requires before/after captures for UI changes; attaching them (or marking the row N/A) would let a reviewer see the cancel/outcome states without driving the dev app.

^{｜ Fix all ➔ ｜ Fix 👍s ➔ ｜ View workflow run ｜ Using DeepSeek Flash (free via Pullfrog for OSS) ｜ 𝕏}

pullfrog

ℹ️ Follow-up commits reviewed — no new issues found.

Reviewed changes — the two commits pushed since the initial review (60803e5), both closing cancel-edge gaps:

Window-scoped upload ids — scopeRuntimeUploadId(senderId, uploadId) keys cancellation, and a new runtime-upload-cancel-ipc.ts validates the request and scopes by event.sender.id, so one window cannot cancel another window's upload. The remembered-cancel set is capped at 1024 with oldest-first eviction.
Only delete a partial this upload created — FileUploadSession.uploadFile gains onRemoteCreated, fired from ssh2 WriteStream's open event (verified the pinned v1.17 emits open on a successful exclusive open) and from a set -C; : > … marker command on the system-SSH path. Delete-on-cancel now requires it, so an EEXIST loser no longer removes a file another client just wrote.
Cancel after the last byte — an SSH import rolls back an imported result when the source was cancelled (covers empty folders and a late click); fs:downloadFile and the chunked runtime download both re-check the signal before promotion; the runtime download loop now throws on a zero-byte non-EOF chunk instead of spinning.

No new defects found in these changes. The earlier note about runtime-upload-progress-tracker.ts's cross-file progress guard is unchanged and still open.

^{｜ Fix it ➔ ｜ View workflow run ｜ Using DeepSeek Flash (free via Pullfrog for OSS) ｜ 𝕏}

pullfrog

ℹ️ No critical issues — one stale contract comment to update.

Reviewed changes — the single commit pushed since the prior pullfrog review at 5d12792d62 (60d329f9cd), which gives a folder download a moving bar.

Folder size walk now runs alongside the download — downloadFolderViaSftp starts measureRemoteTree without awaiting it and reports the total when the walk finishes, dropping a total that arrives after the download settled; the 2 s budget and its null return are gone, and a failed walk or a throwing observer is swallowed so it never fails the download.
Indeterminate row bar while the total is unknown — TransferProgressPanel renders an animated, aria-valuenow-less role="progressbar" for an active row with no total, keeping the determinate <Progress> once the total is known and for ended rows.
Tests — the SFTP progress suite replaces the budget case with four cases (total lands mid-transfer, observer throws, slow walk does not block and its late total is dropped, walk failure still downloads), and a new TransferProgressPanel.test.tsx covers the animated/determinate/ended bar states.

^{｜ Fix all ➔ ｜ Fix 👍s ➔ ｜ View workflow run ｜ Using deepseek-v4.1-flash (free via Pullfrog for OSS) ｜ 𝕏}

pullfrog

✅ No new issues found.

Reviewed changes — the two commits pushed since the prior pullfrog review at 60d329f9cd (3689d8d21f, c20a5f85dc), which keep a failed SSH upload's real error and correct a stale contract comment.

Kept a failed SSH upload's real error — importOneSourceSsh now reports the failure to importSshSourceWithProgress through an onFailure callback that runs before any cleanup, and the cancel branch only relabels the result as cancelled when the failure did not precede the click; otherwise the real reason is returned (with any rollback leftovers appended).
Corrected the onTotalBytes contract — the shared observer JSDoc now says a folder's total may arrive mid-transfer and is never reported after the transfer ends, matching the alongside-the-download walk.

The new tests are non-vacuous: the progress suite cancels from a beforeRemove hook so the click lands inside cleanup, and the rollback suite pins both directions (failure-then-cancel keeps the real reason; cancel-caused failure still reports as cancelled). The prior review's inline nit is addressed by c20a5f85dc, and its thread is resolved.

^{｜ View workflow run ｜ Using deepseek-v4.1-flash (free via Pullfrog for OSS) ｜ 𝕏}

pullfrog

✅ No new issues found.

Reviewed changes — the single merge pushed since the prior pullfrog review at c20a5f85dc (2595868489), which merges main after #24559 reverted #24401.

Restored the branch's transfers inline — main's revert deleted ssh-connection-file-transfers.ts and ssh-upload-session-lifetime.ts, and git auto-merged downloadFile / openFileUploadSession to main's plain bodies, silently dropping this branch's download progress/cancel, upload cancel signal and callbacks, and removeCreatedEntry. The merge restores both methods in ssh-connection.ts to this branch's pre-#24401 form, keeping main's unrelated changes.
Verified faithful — the restored methods (uploadDirectory, downloadFile, openFileUploadSession, writeFile, writeBuffer) match the previously approved 03a44db0b7 state; pnpm tc:node is clean, no references to the deleted modules or work ledger remain, and the SSH transfer suites pass (8 tests).

^{｜ View workflow run ｜ Using deepseek-v4.1-flash (free via Pullfrog for OSS) ｜ 𝕏}

pullfrog

✅ No new issues found.

Reviewed changes — the main merge 88f930fe74 (main at e2da3a1eb1), the only commit since the prior pullfrog review at 2595868489.

Merged main's LocalFileAccess file-access feature — main's #24489 replaced filesystem-auth with local-file-access-resolution and added access?: LocalFileAccess to fs:readFile / rename / stat / pathExists / importExternalPaths. All five conflicts (filesystem-mutations.ts args, filesystem-api.ts / fs-bridge.ts field + import, runtime-upload-file-stream.ts's removed authorizeExternalPath, runtime-file-import-client.ts options) were resolved by keeping both sides.
Kept the branch's import path intact — runtime-file-import-client retains its progress option and runSshUploadWithProgress, adding main's access and ...localAccess(...) to the local import call only, so remote destinations stay root-relative.
Extracted the runtime upload tracking — trackRuntimeUploadForSender moved from the fs:uploadExternalFileToRuntime handler into runtime-upload-cancel-ipc.ts, behavior-identical to the prior inline wiring (null when no uploadId, same throttle/emit, same release).

Verified: pnpm tc:node and pnpm tc:web are clean; filesystem-mutations-runtime-upload, runtime-upload-cancel-ipc, runtime-upload-cancellation, and runtime-file-client-external-import pass (34 tests); pnpm run check:code-quality:changed reports 0 findings. git show --remerge-diff 88f930fe74 confirms every conflict kept both sides and dropped no branch behavior.

^{｜ View workflow run ｜ Using deepseek-v4.1-flash (free via Pullfrog for OSS) ｜ 𝕏}

OrcaWin · 2026-10-11T06:49:22Z

Thanks for this, @Chihen-Tai. Quick update: the legacy SSH relay has been removed (#27214, #27215), and SSH workspaces now run on Orca's managed server on the host, so their uploads and downloads go through the same remote-runtime transfer path as #16107 rather than the old desktop-side SFTP import. The idea here (one progress panel with cancel for remote transfers) still applies, but the SSH-specific half would need to be reworked onto that runtime path when this is rebased.

Resolved against main's owner-routed runtime target (settings -> target), the shared streamExternalFileSlices streamer, and the terminal drop split. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

…d downloads SSH workspaces now run on the host's managed runtime, so their transfers use the same runtime path as remote Orca servers. This builds on stablyai#16107's runtime upload progress instead of the removed desktop-side SFTP import: - stablyai#16107's terminal-drop panel moves to components/transfer-progress and takes a direction; file explorer and editor drops use it too. - Runtime downloads (explorer Download, terminal "download & open") count the chunks the renderer already pulls, show the panel, and cancel between chunks through an AbortSignal; the temp file is discarded and nothing is committed. - SSH workspace files download through the host runtime instead of the SSH filesystem provider, which nothing registers anymore. Folder downloads keep their existing SSH-only path. - Runtime import cancel fixes: directories check the cancel before and after each create, and a source is marked cancelled only when the cancel is what stopped it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

…progress # Conflicts: # src/main/ipc/filesystem/filesystem-mutations.ts # src/renderer/src/components/editor/editor-dropped-file-open.ts # src/renderer/src/components/right-sidebar/file-explorer-row-file-transfer.ts # src/renderer/src/components/terminal-pane/terminal-drop-handler.test.ts # src/renderer/src/components/terminal-pane/terminal-drop-runtime-catalog-owner.test.ts # src/renderer/src/components/terminal-pane/terminal-drop-upload-report.test.ts # src/renderer/src/components/terminal-pane/terminal-drop-upload-report.ts # src/renderer/src/components/terminal-pane/terminal-native-file-drop.ts # src/renderer/src/components/terminal-pane/terminal-pane-element-file-drop.test.tsx # src/renderer/src/i18n/en-runtime-required.json # src/renderer/src/i18n/locales/en.json # src/renderer/src/runtime/runtime-file-client-external-import.test.ts # src/renderer/src/runtime/runtime-file-import-client.ts # src/renderer/src/runtime/runtime-file-read-client.ts

…ecord selector after main merge Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

…progress # Conflicts: # src/renderer/src/runtime/runtime-file-client-test-harness.ts # src/renderer/src/runtime/runtime-file-read-client.ts

greptile-apps · 2026-10-28T20:36:35Z

        await args.writeSlice(buffer.subarray(0, bytesRead).toString('base64'), offset)
        offset += bytesRead
+        // Why: reported after the chunk is acknowledged, so the bar tracks bytes the
+        // runtime actually has rather than bytes handed to the socket.
+        args.onProgress?.({ sentBytes: offset, totalBytes })


Cancel still publishes the file

If the user clicks Cancel during the final writeSlice, the upload still publishes the file. Cancellation is checked before each slice, but not after the last write returns. The renderer then calls files.commitUpload without another cancel check. This also affects the single write for an empty file.

Check cancellation after the final write, while the file is still temporary, so the upload can discard it instead of publishing it.

greptile-apps · 2026-10-28T20:36:35Z

+    if (controller.signal.aborted) {
+      view.panel?.updateRow(rowId, { status: 'cancelled' })
+      view.panel?.settle()
+      return { canceled: true }


Cancel hides download errors

A Cancel click turns every download error into a cancelled result, even when cancellation did not cause the error. For example, if the pending chunk read fails because the connection drops after the click, this catch hides that failure and shows “Cancelled.” Users lose the actual reason the download failed.

Only treat the error thrown by the cancel checkpoint as cancellation. Pass unrelated errors back to the caller.

greptile-apps · 2026-10-28T20:36:35Z

+        <ul className="border-t border-border">
+          {session.rows.map((row) => (


Cancel buttons leave the screen

The expanded upload list has no height limit or scrollbar. Dropping enough separate files makes the bottom-right toast taller than the window, pushing the header and earlier rows above the screen. Those rows’ Cancel buttons—and the collapse button—then cannot be reached with the mouse.

Limit the list height to the available window space and let it scroll.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

…progress Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Also cover closed-window cleanup of remembered cancels. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

…lure Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

…stopped it Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

…lue tests Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

…ancel after the final stat Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Keeps the shared transfer panel and upload progress/cancel here; download progress and cancel follow in a separate PR. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

…progress Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

…ral extraction expects Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

…progress # Conflicts: # src/renderer/src/i18n/en-runtime-required.json

mmarabel and others added 18 commits August 23, 2026 00:32

Merge feat/stream-runtime-upload-staging into feat/remote-drop-upload…

5b02c76

…-progress Picks up the review follow-ups on the base branch: staged-size enforcement, the rounding fix for over-limit errors, and the Windows symlink test guards.

Merge feat/stream-runtime-upload-staging into feat/remote-drop-upload…

f7c1deb

…-progress Picks up the per-file ceiling check at the streaming boundary and the shared runtime-import-limits module.

Merge branch 'feat/stream-runtime-upload-staging' into feat/remote-dr…

e357019

…op-upload-progress

Merge upstream/main into feat/remote-drop-upload-progress

3bb3397

Chihen-Tai requested a review from brennanb2025 as a code owner September 29, 2026 09:52

Copilot AI balanced review requested due to automatic review settings September 29, 2026 09:52

Copilot AI reviewed Sep 29, 2026

greptile-apps Bot reviewed Sep 29, 2026

View reviewed changes

coderabbitai Bot reviewed Sep 29, 2026

View reviewed changes

Comment thread src/main/ipc/filesystem-import-ssh-progress.ts Resolved

Comment thread src/main/ipc/filesystem-mutations.ts Resolved

greptile-apps Bot reviewed Sep 29, 2026

View reviewed changes

Comment thread src/main/ipc/filesystem-import-ssh-progress.ts Resolved

coderabbitai Bot reviewed Sep 29, 2026

View reviewed changes

pullfrog Bot reviewed Sep 29, 2026

View reviewed changes

Comment thread src/renderer/src/runtime/runtime-upload-progress-tracker.ts Resolved

pullfrog Bot reviewed Sep 29, 2026

View reviewed changes

greptile-apps Bot reviewed Sep 29, 2026

View reviewed changes

Comment thread src/main/ssh/system-ssh-file-binary-transfer.ts Resolved

greptile-apps Bot reviewed Oct 1, 2026

View reviewed changes

Comment thread src/main/providers/ssh-filesystem-download.ts Resolved

pullfrog Bot reviewed Oct 1, 2026

View reviewed changes

Comment thread src/main/providers/ssh-filesystem-download.ts Resolved

pullfrog Bot reviewed Oct 1, 2026

View reviewed changes

rorar mentioned this pull request Oct 2, 2026

[Feature]: A transfer queue behind the upload panel — retry, pause/resume, and a conflict policy #24735

Open

pullfrog Bot reviewed Oct 2, 2026

View reviewed changes

pullfrog Bot reviewed Oct 5, 2026

View reviewed changes

Microdaery and others added 2 commits October 11, 2026 16:42

Merge stablyai#16107 (runtime drop upload progress) into current main

ae66b3f

Resolved against main's owner-routed runtime target (settings -> target), the shared streamExternalFileSlices streamer, and the terminal drop split. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Chihen-Tai force-pushed the feat/remote-transfer-progress branch from 88106e8 to 43c7743 Compare October 11, 2026 09:15

Chihen-Tai pushed a commit to Chihen-Tai/orca that referenced this pull request Oct 11, 2026

Runtime-path screenshots for stablyai#23849

f450821

Merge origin/main into feat/remote-transfer-progress

5e438ea

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

liujiayi771 mentioned this pull request Oct 27, 2026

[Feature]: Show progress when downloading files from a Remote Orca Server #34369

Open

Chihen-Tai and others added 3 commits October 28, 2026 12:05

fix: drop unreferenced upload-toast keys and read worktrees through r…

0d1735c

…ecord selector after main merge Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Merge remote-tracking branch 'origin/main' into feat/remote-transfer-…

2cd7654

…progress # Conflicts: # src/renderer/src/runtime/runtime-file-client-test-harness.ts # src/renderer/src/runtime/runtime-file-read-client.ts

greptile-apps Bot reviewed Oct 28, 2026

View reviewed changes

Chihen-Tai and others added 13 commits October 29, 2026 11:58

Merge remote-tracking branch 'origin/main' into feat/remote-transfer-…

9453219

…progress Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

fix(upload): reject a cancel that lands during the final upload write

d073622

Also cover closed-window cleanup of remembered cancels. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

fix(transfers): keep a download failure after a Cancel click as a fai…

c9eb270

…lure Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

fix(transfers): show an upload row as cancelled only when the cancel …

c67aee5

…stopped it Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

fix(transfers): scroll the expanded transfer list within half the window

811122a

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

refactor(transfers): use shared button and shadow tokens; drop low-va…

8a5b54f

…lue tests Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

refactor(transfers): reuse statRuntimePath for download size; check c…

bb27016

…ancel after the final stat Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

chore(transfers): trim comments to one line; drop a passthrough test

bc25dd8

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

fix(transfers): let the ghost Button own its colors

dbcf21b

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

refactor(transfers): move remote download progress to its own PR

e1c0b51

Keeps the shared transfer panel and upload progress/cancel here; download progress and cancel follow in a separate PR. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Merge remote-tracking branch 'origin/main' into feat/remote-transfer-…

46791b6

…progress Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

fix(i18n): give the upload heading its singular inline, as main's plu…

fd855b3

…ral extraction expects Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Merge remote-tracking branch 'origin/main' into feat/remote-transfer-…

985b216

…progress # Conflicts: # src/renderer/src/i18n/en-runtime-required.json

		<ul className="border-t border-border">
		{session.rows.map((row) => (

Conversation

Chihen-Tai commented Sep 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

ELI5

What Changed

Why

Linked Issue

Visual Proof

Testing

AI Disclosure

Agent skill upstream boundary

Notes

Checklist

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

greptile-apps Bot commented Sep 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Confidence Score: 5/5

Findings

Summary

Diagram

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

coderabbitai Bot commented Sep 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviews paused

❌ Failed checks (2 warnings)

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

pullfrog Bot left a comment

Choose a reason for hiding this comment

ℹ️ Visual proof is still a TODO

Uh oh!

Uh oh!

pullfrog Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

pullfrog Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

pullfrog Bot left a comment

Choose a reason for hiding this comment

Uh oh!

pullfrog Bot left a comment

Choose a reason for hiding this comment

Uh oh!

pullfrog Bot left a comment

Choose a reason for hiding this comment

Uh oh!

OrcaWin commented Oct 11, 2026

Uh oh!

greptile-apps Bot Oct 28, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps Bot Oct 28, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps Bot Oct 28, 2026

Choose a reason for hiding this comment

Uh oh!

This branch has not been deployed

Chihen-Tai commented Sep 29, 2026 •

edited

Loading

greptile-apps Bot commented Sep 29, 2026 •

edited

Loading

coderabbitai Bot commented Sep 29, 2026 •

edited

Loading