* wip(cloud): PARITY-FOLLOW design fixtures (top-bar followers, sidebar Team and Following)
* feat(cloud): PARITY-FOLLOW phase 1: sidebar Team list and the top bar's people (creator and who is here now)
* test(cloud): PARITY-FOLLOW fixtures name the workspace a teammate is in
* fix(cloud): PARITY-FOLLOW fixture typecheck
* feat(cloud): PARITY-FOLLOW follow endpoint: workspace_follows (0055), PUT/DELETE /v1/team/workspaces/:id/follow, followers in workspace views
* fix(cloud): PARITY-FOLLOW lint: the hover action's wrapper owns its visibility; no Button restyles; no side effect in a state updater
* feat(cloud): PARITY-FOLLOW phase 2: Follow in the top bar, followers in the stack, Following section in the sidebar
* test(cloud): PARITY-FOLLOW no real-time wait in the live-read test
* feat(cloud): ENTERPRISE-SSO Settings › Enterprise single sign-on and directory sync, driven by server state
* feat(cloud): key icon on the single sign-on group title (TEAM-DIALOG-2)
* fix(cloud): Contact us in the SSO block is a plain button; Copy link is for sign-in surfaces
* test(cloud): the copied SSO setup link is minted like the opened one and never logged
* fix(cloud): design-squad review of the SSO blocks (sentence-case chips, directory sync icon, grace and last-change wording)
* fix(cloud): sentence-case success badge variant for the SSO chips; catalog matches the new copy
* fix(cloud): register the Enterprise IPC handlers with the team handlers (file line limit)
* feat(cloud): every setup notice line has plain words and a real action, or doesn't show (ENV-NOTICE-ACTIONS)
- Doctor checks that reached the bare 'check' line now classify: low disk ('disk')
and a missing repo tool ('tool') get their own plain words; disk.free without a
code and any check this desktop doesn't know are hidden, never a bare label.
- The push notice reads repo access plus the person's own gh rights on the repo
(new gitHubInstallRights IPC): Install on {owner} only where installing can
work, 'Copy request for an owner' once an owner was asked, Check again where
the App already reaches the repo, plain words for someone else's public repo
(octocat/Hello-World). Install no longer carries a Copy link.
* copy(cloud): a push nobody here can install offers Copy request for an owner (design-squad, ENV-NOTICE-ACTIONS)
* fix(cloud): ENV-NOTICE-ACTIONS rebase onto AUTH-ONLY-COPY-LINK: the owner request takes the install page from the repo-access answer
* feat(cloud): COPY-LINK-FIRST-CLICK Copy link on the first Sign in and setup's first Continue in browser starts the same flow without opening the browser
* feat(cloud): COPY-LINK-FIRST-CLICK loopback sign-in links say they open in any browser on this computer (menu line and copied toast)
* fix(cloud): COPY-LINK-FIRST-CLICK Copy link stays on sign-in only; the choose-plan Continue in browser has no copy link
Copy link (the split button's chevron) is for auth and sign-in pages, where
people paste the URL into an incognito window. Billing, contact sales, help,
support and the GitHub App install go back to plain buttons; the billing and
App-install link-only IPCs are removed.
Every button that opens a URL in the external browser gets a chevron with
"Copy link" that copies the exact URL (minted the same way for lazy links),
for incognito windows or another browser profile.
* fix(cloud): PAIRED-WAKE (1/2) a sleeping paired cloud workspace wakes when opened (sidebar, Home), on focus and on hover, like an owned one
cloudWorkspaces:wake wakes a paired workspace's sandbox through the control plane (this desktop has
no VM record to resume) and reconnects its bound server at once. Opening its sidebar row wakes it
when asleep (waking overlay, failure card), and Home > Open wakes it before connecting to the saved
pairing. Predictive wake treats a sleeping paired workspace as a candidate with the same preflight
(fresh status + billing caps) and wakes it quietly (coordinator decision). Wake progress never adds
a paired row to the owned ids.
* fix(cloud): PAIRED-WAKE localize the not-paired message; test uses fixed timestamps
* fix(cloud): PAIRED-WAKE design-squad copy for the not-linked wake failure
Danger-zone card after 'Leave <team>' (owners only, Settings › Team): pre-checks
auth's GET /v1/desktop/orgs/:orgId/delete-check and shows each blocker with its
way out ([Manage billing] / [Show cloud workspaces], Home with Archived on when any
are archived), [Delete team] disabled while blocked. The dialog asks for the exact
team name (case-sensitive, paste allowed) and POSTs /delete with confirmName.
Failures stay in the dialog: confirm_mismatch under the field; 503 'nothing was
deleted'; 429 disables Delete for a minute; 409 not_deletable repeats the blockers.
After a delete the session refreshes (the team falls back to personal).
Copy is design-squad's final TEAM-DELETE copy.
The host panel's recipe warning summarized all of process.env, but a recipe that
sets passEnv only gets buildRecipeInheritedEnv(process.env, passEnv). The IPC
now takes the host's environmentId; main finds its runtime and resolves passEnv
through getRuntimeRecipeContext (never from the renderer), falling back to the
whole env when the recipe can't be resolved. The summary reports narrowed, and
the panel says so with a new string. One classifier (isRecipeCredentialEnvName)
now backs both this warning and listCredentialLikeEnvNames.
Co-Authored-By: Claude <noreply@anthropic.com>
* Avoid refetching every linked Linear badge on window focus
* Preserve sourced badge updates without focus polling
* Use a fixed clock in linked issue refresh contracts
* Resolve linked issue refresh scope from its source
Adds the person's own GitHub identity (user OAuth) for Orca Cloud commit and push attribution: control-plane client methods (githubUser, connectGitHubUser, disconnectGitHubUser) with zod schemas, IPC channels that open the authorize URL only when its origin is exactly https://github.com, preload bridge methods, and a GitHub row under the signed-in identity (not connected, pending with focus re-check and a 3 s poll for up to 5 min, connected, error, disconnect confirm).
- main: lenient GET /v1/plans parse (a bad plan/price/feature is dropped alone), ETag revalidation,
last-good copy in userData (offline <7 days only), 404 = unsupported; IPC orcaProfiles:billingPlans
- plans dialog: Stripe prices, the catalog's Team and Enterprise features (known ids localized,
unknown ids show billing's text), only priced intervals, seat bounds, currency from the price;
older billing (404) reads its entitlement offers; nothing usable -> error + Try again, never a price
- checkout sends the catalog plan id, not 'team'; 409 plan_unavailable is a typed result with
'This plan isn't available right now', Try again (re-reads the catalog) and Contact us
- hardcoded Enterprise bullets removed; PR C checked against today's dev billing (no alert levels)
* fix(workspace-cleanup): warn before deleting a workspace's ignored local files
git worktree remove deletes ignored files such as .env and local config,
and git status never reports them, so cleanup showed "Clean git" and the
delete dialog said nothing. Read them with a bounded ls-files listing,
skip regenerable output, symlinks and byte-identical copies of the main
checkout, and surface the rest as an approval-only cleanup blocker and a
warning in the delete confirmation.
* fix(workspace-cleanup): show an unchecked warning when the ignored-files check fails
* style(workspace-cleanup): format merged fact status list
* feat(plugins): Featured and Newly added rows in the plugin catalog
Featured shows the most installed plugin per category; Newly added lists plugins
by the catalog's new entry-level addedAt (hidden when no catalog dates entries),
with a New badge for 24h and an Added this week filter. Snapshots move to a v3
cache key so older builds never read addedAt.
* feat(plugins): derive Newly added dates from release dates, as the website does
Drops the catalog-level addedAt field (schema, docs, v3 snapshot key). Main now
estimates a listing date for each non-official plugin from its oldest dated
release, and the Newly added row, New badge and This week filter read it through
shared helpers that mirror orca-site's pluginNew.ts: 30-day window, newest first,
dates more than an hour in the future ignored, "just now / N hours ago / N days ago".
* feat(plugins): show nine Newly added plugins, drop the counts release dates inflate
Listing dates come from each community plugin's oldest kept release, and
catalogs keep only recent releases, so almost every plugin looks new: 181
of 182 fall in the 30-day window and 142 count as this week. Remove what
that inflates rather than flag it: the "N this week" count and its See all,
the This week filter, and the 24h New badge.
The Newly added row now offers the website's nine in the catalog's normal
wrapping grid, the same columns and card widths as the catalog groups.
* fix(plugins): pick Featured winners by every kind a plugin belongs to
Featured used only a plugin's first filter kind, while the category filters
count every kind, so category order could change winners or drop a kind's only
candidate. Each plugin, walked by installs with a key tie-break, now fills one
unfilled kind it belongs to (the one with the fewest candidates left, then by
name). Also note why Featured is a capped one-row teaser and pin the cap.
* fix(plugins): hide Featured when Newly added is empty
Without Newly added, Featured sat directly on the Official catalog, whose
leading cards are the same popular plugins in the same columns, so back-to-back
rows repeated and read as a render bug. Featured now shows only alongside
Newly added. Leaving featured plugins out of their catalog instead would move a
card into the catalog the moment it's installed and skew the catalog's N of M.
Adds a PluginManager test that no plugin card shows twice in the empty state,
and page-level fixtures (390, 600, 1440, empty 1440) for screenshots.
* fix(plugins): cap Newly added at two full rows of the current columns
At phone width nine stacked cards pushed the catalogs about 3.5 screens
down. The grid now shows two full rows of its container-query column
count (8 at four columns, 4 at two, 2 at one), hides a partial last row,
and the pick renders at most eight. Hidden plugins stay listed in their
catalog group, so there's no See all.
* Correct plugin catalog fixture evidence
* Make plugin highlight tests match observable behavior
* feat(wsl): turn WSL hosts on by default; ORCA_INTERNAL_WSL_HOSTS=0, false, off or no turns them off
Co-Authored-By: Claude <noreply@anthropic.com>
* fix(wsl): review follow-ups for WSL hosts on by default
- Off words also match when quoted (cmd.exe's set NAME="0" keeps the quotes).
- The refusal now says WSL hosts are turned off for this launch, not missing from the build.
- New preload test pins when the renderer gets the WSL hosts API.
- Unit tests no longer inherit the gate state an Orca terminal publishes.
---------
Co-authored-by: Claude <noreply@anthropic.com>
claude setup-token prints only its manual-redirect link (redirect_uri platform.claude.com/oauth/code/callback), which Orca opens from "Open again" and which ends on Anthropic's "Authentication code - Paste this into Claude Code" page. The CLI waits at a masked "Paste code here if prompted >" in Orca's hidden PTY, and nothing could type into it, so setup spun until its 10-minute timeout.
- Runner: the setup-token process can be written to; once the sign-in link shows, a submitter types the code then Enter. A refused code ("That code wasn't accepted") starts over in the same run (Enter, new link, new submitter).
- claude-setup-run.ts (extracted from the service): one run's link, code prompt and outcome. A run that ends without a token after its link showed is expired (failed/timed_out); "Open again" then starts a fresh run.
- IPC orcaCloudAgents:submitClaudeCode: a bare code or the whole callback URL, trimmed (setup-tokens and other sites refused), never logged or stored; progress on the 'browser' phase (acceptsCode, code: checking | rejected).
- UI (design-squad copy): [Paste code] [Finish setup] [Open again] on the pane strip (terminal and chat UI, which mounts the same strip) and Settings > Agent accounts (also the sign-in sheet the new-workspace row and host panel open). Masked, cleared once sent, auto-submitted when a whole code is pasted; one rejection message; expired shows "Open again". The build sheet row is display only and points to Settings.
* Move local usage services into a supervised backend process
* Own usage recovery and worker retirement lifetimes
* Preserve answered usage data during background refresh
* Run independent usage scans concurrently in the backend
* Limit backend startup paths to the delegated usage service
* Show usage failures through backend recovery
* Include usage failure strings in the English catalog
* Keep usage update details beside refresh failures
* Resolve usage freshness failure from the final producer snapshot
* Retain the forced refresh completion requirement
* Keep managed backend failures out of application crash reports
* Preserve usage recovery boundaries across backend reconnects
* Match the backend RPC cancellation signal in the usage seam proof
* Avoid serializing backend requests before port delivery
* Keep receiving request validation in the boundary schemas
* test: align usage transport coverage with renderer project
* fix: preserve unknown usage state and renderer retirement
* fix(usage): revalidate tracking before scan admission
* fix(usage): retry failed backend startup on demand
* test(usage): isolate stale backend ownership checks
* fix(native-chat): refuse a stale startup-dialog card choice and add a card for the multi-server MCP dialog
* fix(native-chat): drop casts from the startup-dialog guard
* fix(native-chat): refuse a startup card choice until the screen model has applied all received output
* fix(native-chat): refuse a clipped MCP server list and guard restored startup cards
* fix(native-chat): allow one startup card choice per screen so a second client's keys can't hit the next dialog
Each Orca Cloud create logs `[orca-cloud] create <creationId> <phase> +<ms>`
(ms since its provision started) to the main app log, so a slow create shows
which phase took the time. The provision's own `[orca-cloud] <stage>` progress
lines are unchanged.
Also folds the two identical post-start cleanup-and-fail blocks in the
provision handler into one helper (ephemeral-vm.ts was at the 300-line cap).
* Keep browser chrome metadata current without synchronous guest reads
* Provide the guest Escape subscription in browser pane fixtures
* Provide native navigation state in browser guest fixtures
* Preserve browser navigation and loading across asynchronous metadata reads
* Retire browser metadata when its actual guest is removed
* Explain native identity casts in browser disposal fixtures
* Preserve URL titles for untitled client browser pages
* Preserve current browser navigation and untitled page labels
* Keep merged browser failure type within lint limit
* Keep merged browser failure type within lint limit
* Bound published browser titles to the existing wire limit
* Use template literals in browser title regression
OpenCode, OpenCode 2 and Z Code keep every conversation in one shared
database, so Session History could only hand off the row's preview
messages. The session's own host now copies that one conversation into
the per-chat hand-off snapshot the chat Hand Off already uses, and the
dialog points the new agent at it. Older hosts, SSH rows and failed
reads keep the preview.
The workspace watch never follows a symlinked folder, so a tab opened
through one (target outside the root) got no change events. Watch each
such tab's folder directly; main checks for the link with an lstat walk
and already rewrites the folder watch's events to the link spelling.