* fix(mobile): sync non-markdown editor files to mobile session tabs
A regression stopped non-markdown files opened on desktop from reaching the
mobile session-tab list: the group projection order surfaced markdown tabs but
dropped plain file tabs. Append any open editor file for the worktree that the
projection didn't emit, keyed by relativePath, so plain files show up on mobile
again (markdown still syncs via the projection).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* fix(mobile): preserve recovered editor session tab identity
Co-authored-by: Orca <help@stably.ai>
* fix(mobile): tolerate legacy active tab metadata
Co-authored-by: Orca <help@stably.ai>
---------
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-authored-by: Jinwoo-H <jinwoo0825@gmail.com>
Co-authored-by: Orca <help@stably.ai>
* fix(mobile): downscale oversized clipboard images so paste no longer fails
Pasting a large clipboard image (high-res screenshot or photo) failed with
'Image too large to paste' because the re-encoded PNG exceeded the 24 MiB
base64 upload cap, with nothing shrinking it first.
Now an oversized image is downscaled to fit the budget before upload:
- computeMobileClipboardImageDownscale() picks target dimensions by area
(~sqrt(budget/actual)), with a bounded retry loop since PNG size is nonlinear.
- prepareMobileClipboardImageBase64() drives the loop with an injected resizer,
so the byte/dimension logic is unit-tested without native modules.
- The resizer stages the image to a temp file and hands ImageManipulator a
file:// URI; the iOS native loader (Data(contentsOf:)) cannot decode large
base64 data URIs, so a data URI made renderAsync throw.
Adds expo-image-manipulator and expo-file-system.
* fix(mobile): fail fast when resized clipboard image has no base64
Empty base64 from saveAsync would pass the downstream base64 check and
upload a corrupt image; throw instead so the paste surfaces an error.
Addresses CodeRabbit review on #5601.
* Fix mobile clipboard image resize cleanup
Co-authored-by: Orca <help@stably.ai>
---------
Co-authored-by: Jinwoo-H <jinwoo0825@gmail.com>
Co-authored-by: Orca <help@stably.ai>
* refactor(sidebar): give repo and group names priority over header chrome
Repo and group headers no longer show the workspace-count badge or the
collapse chevron, and the trailing action buttons (project menu, add
workspace) now collapse to zero width until the row is hovered, focused,
or its menu is open. The name takes the full row width by default and
only truncates once the actions reveal.
The count was secondary and the chevron was redundant -- the whole
header is already clickable to expand/collapse -- so both were spending
horizontal space better given to the name. The now-unused count field
and its subtree-counting logic are removed from the header row model.
* refactor(sidebar): drop the rename-pending badge from workspace rows
With auto-rename on, every freshly created workspace carried a "rename
pending" badge beside its name until the first agent message landed.
It was persistent clutter on the element we most want legible -- the
workspace name -- so remove it and the no-longer-needed handler.
* Remove unrelated formatting from PR 4761 merge
---------
Co-authored-by: Jinjing <6427696+AmethystLiang@users.noreply.github.com>
* Prevent stale branch compare results on Git HEAD updates
Track the status HEAD for each worktree to prevent race conditions
where a background branch compare request finishes after Git HEAD has
moved. Stale compare results are now rejected, and the compare state
is invalidated on status HEAD changes to avoid rendering incorrect
diffs. Also allows preserving the prior summary during refresh
requests to reduce UI flicker.
* Match '(initial)' status head with null branch compare head OID
Map the '(initial)' HEAD reported by git status for unborn branches
to a null head OID in branch compare results. This prevents false
mismatch positives during validation and state transitions, ensuring
unborn branch comparisons are accepted and stale ones are correctly
rejected.
* memoize hostedReview in SourceControl and extract support search
- Wrap the hostedReview calculation in useMemo in SourceControl to avoid redundant object recreation and re-renders.
- Move the general support search entries to their own dedicated file for improved code organization.
* fix: improve mobile terminal glyph rendering
Align the mobile companion WebView terminal with the desktop xterm setup so Claude output renders correctly on iOS.
- Upgrade the embedded xterm CDN stack to the desktop beta line
- Load Unicode 11 before replaying terminal bytes
- Enable WebGL rendering with context-loss fallback
- Preserve Claude status dots as text presentation
- Add regression coverage for the mobile terminal setup
* Fix mobile status dot normalization edge cases
Co-authored-by: Orca <help@stably.ai>
---------
Co-authored-by: Jinwoo-H <jinwoo0825@gmail.com>
Co-authored-by: Orca <help@stably.ai>
* Highlight the open file in the Source Control sidebar
Pending (uncommitted) rows had no persistent indicator for the file
currently open in the editor: a plain single click cleared the bulk
selection and only opened the diff, leaving no visual cue for which row
was active.
Derive the active editor file for the worktree from the store and mark
its Source Control row as the current row (full bg-accent + data-current),
outranking the lighter bulk-selection tint. Matching is area-aware so a
partially staged file lights up only the row that is actually open, and
the highlight clears when the visible tab is not an editor.
Extract the row-key mapping into source-control-active-open-file-keys.ts
and cover it with unit tests plus render tests for the highlight wiring.
* Update src/renderer/src/components/right-sidebar/SourceControl.open-file-highlight.test.tsx
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
* Refine source control open-file highlighting
---------
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: brennanb2025 <brennankbenson@gmail.com>
The empty-workspace landing screen showed an alarming "Missing
dependencies — GitHub CLI is not installed" banner even for users
whose registered projects are all GitLab-backed, where `gh` is never
used. `gh` only powers GitHub PRs/issues/checks, so this is a false
alarm for GitLab-only users (#5670).
Treat the GitHub CLI prompt as a soft, provider-scoped setup nudge
rather than a global missing-dependency error:
- Quiet the banner styling (muted surface, no amber frame) and cap its
width so it reads as a soft nudge, not an error state.
- Add a persistent dismiss to the gh / gh-auth nudges. Git stays pinned
as a hard global dependency.
- Dismissal snapshots the set of GitHub-backed project identity keys;
the nudge re-surfaces only when a genuinely new GitHub-backed project
is added (set-based, so remove+re-add of the same project doesn't
retrigger, and GitLab/folder repos never do).
Adds isGitHubBackedRepo() to the host-setup projection (reusing the
existing GitHub-identity detection) plus unit tests for both the
predicate and the dismissal logic.
Co-authored-by: Orca <help@stably.ai>
* Revert "fix(terminal): add proportional scroll fallback for sidebar resize" (#937)
* fix(sidebar): smoothly animate off-screen worktree reveal on click (#1302)
Clicking a worktree card whose row lies outside the sidebar viewport
caused an instant jump when scrolling it into view. Switching
`scrollToIndex` to `behavior: 'smooth'` turns that minimum-distance
scroll into an animated slide while keeping `align: 'auto'` so visible
cards still no-op (no re-centering).
Co-authored-by: Orca <help@stably.ai>
* Avoid local scrollback serialization on shutdown (#1821)
* Fix PR refresh coordinator test arguments (#2545)
* release: v1.4.31
* release: v1.4.31
* release: v1.4.31
* release: v1.4.31
* release: v1.4.31
* release: v1.4.31
* release: v1.4.31
* release: v1.4.36-rc.6
* release: v1.4.36-rc.6
* release: v1.4.36-rc.6
* ci: gate release-cut to the canonical repo so it skips forks (#4815)
The cut job checks out main, bumps package.json's version, and
fast-forwards main. On a fork with Actions enabled, the scheduled RC
cut runs against the fork's main and diverges it on the version line
every slot, so that contributor's PRs back to upstream conflict on
package.json even when their change never touches it.
Gate the job to github.repository == 'stablyai/orca' so it (and the
jobs that depend on it) no-op on forks. Canonical scheduled and manual
cuts are unaffected.
* feat(hooks): install Devin managed status hooks
* feat(devin): address hook review, resume, and UI polish
- Parse Devin config.json as JSONC; warn on read_config_from overlap
- Windows hook command uses forward slashes; APPDATA fallback
- Add devin to sleeping-agent resume and UI registries (plan 003/004)
- Add hook-service and hook-config-json tests
Closes follow-up for plans 002–004 on feat/add-devin-agent.
* feat(devin): scan ATIF transcripts for AI Vault
Register devin in AI_VAULT_AGENTS, discover ~/.local/share/devin/cli/transcripts
(or DEVIN_HOME), parse ATIF JSON sessions, and build devin --resume commands.
* docs(devin): clarify stdin-after-start vs bracketed paste
* fix(devin): use JSONC for remote install, add partial+APPDATA tests
- installRemote: replace readHooksJsonRemote (JSON.parse) with
readTextFileRemote + parseJsonc for JSONC compatibility on SSH
- Add partial status test (some hooks missing → state:'partial')
- Add Windows APPDATA config path test with fallback
* fix(devin): address CodeRabbit review — sessionId fallback, parseJsonc errors, comment, i18n
* Fix Devin integration edge cases
Co-authored-by: Orca <help@stably.ai>
* Package Devin JSONC parser dependency
Co-authored-by: Orca <help@stably.ai>
---------
Co-authored-by: Neil <4138956+nwparker@users.noreply.github.com>
Co-authored-by: Brennan Benson <79079362+brennanb2025@users.noreply.github.com>
Co-authored-by: Orca <help@stably.ai>
Co-authored-by: Jinjing <6427696+AmethystLiang@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Trevin Chow <trevin@trevinchow.com>
Co-authored-by: Jinwoo-H <jinwoo0825@gmail.com>
The line-note popover anchored its top edge just below the selected line
and only ever grew downward. When the anchor line sat near the bottom of
the editor viewport, the popover extended past the visible area and was
clipped by the editor pane's overflow container, hiding the textarea and
the action buttons.
Resolve the popover's vertical placement against real geometry: flip it
above the anchor line when it would not fit below, and clamp it inside the
viewport when it fits neither way. Placement now lives in a pure
resolveDiffCommentPopoverTop helper, while the popover measures its own
height and its container via a ResizeObserver so it re-resolves as the
textarea auto-grows or the pane resizes.
Thread the anchor line height from both diff viewers (DiffViewer and
DiffSectionItem) through to the popover; markdown annotation callers keep
working via a zero default and still benefit from the viewport clamp.