* 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): SSO-FOLLOWUPS members managed by the identity provider on the Team page; a clear message when single sign-on ends a sign-in
* fix(cloud): import the roster type where it is used
* feat(cloud): wording for single sign-on and directory sync events in the audit log
* fix(cloud): the missing-DNS-record audit line reads as an action (design-squad)
* 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
A GitHub App user token generally can't read orgs the App isn't installed on, which is
exactly when canInstall is asked. Read the owner type anonymously first (GET /users/{owner}):
another user's account is false; an org is true only for active admin, false for another
role/state, and null for 403/404/errors/timeouts. Owner-type lookup failures are null.
Present while the Orca GitHub App isn't installed for the repo owner ('missing', or
'public' with no installation). true: the caller's connected GitHub login is the owner,
or their membership in the owner org is active admin. false: member, non-member (403/404),
or another user's account. null: no connected GitHub user token, the token can't be read
or refreshed, or GitHub errored / timed out (3 s). Never fails the answer.
The token comes from memberGitIdentity (decrypt + refresh near expiry).
* 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
NO-ROW: a create with no project here yet (GitHub-only Orca Cloud) now has its pending row
atop the list when grouped by project too (it got a blank 'repo:' section before). While it
opens, openCloudWorkspace reports the server it pairs to (onHost); the sidebar hides that
server's rows until the hand-off removes the pending row, both in one store update, so the
workspace never shows twice.
CANCEL: createSandboxWithProgress (owned and GitHub-only creates) deletes what a cancel
leaves: cancelled in flight, it replays the create by its Idempotency-Key and deletes the
sandbox the control plane hands back (reclaimCancelledCreate, retrying while the first is
still in progress); cancelled just as it answered, it deletes it. A cancelled clone already
deleted itself. The GitHub runner deletes the sandbox when Cancel lands before or during
Open workspace (which also drops this computer's pairing), and cancel's 'Deleting the
sandbox…' waits for it. Copy link moves to cloud-workspace-share-link.ts (re-exported) to
keep open-cloud-workspace.ts within max-lines.
Landing is back to upstream's layout; its Add project opens the sidebar's
Add project menu. Everything only the Home list did moves to one picker
reached from the Add project menus, the palette, and every former Home
pointer (paired-wake not-paired card, primary-delete toast, running limit,
teammate profile, team delete).
Co-Authored-By: Claude <noreply@anthropic.com>
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.
Environment builds get only the team secrets an admin named, never a swapped model key, hand them to the install script alone, and fail with no snapshot (secret_in_image) when a value is still in a file the build changed.
* fix(cloud): PAIRED-ACCOUNT-FILTER paired workspaces are scoped by the account their pairing was made under
* perf(cloud): PAIRED-ACCOUNT-FILTER read the active account once per profile-index write, not per paired lookup
Restart reaches a paired workspace's sandbox: main's restart resolves a bound pairing
(restartPairedOrNotCloud) and restarts it through the control plane, dropping the bound server's
dead connection so it reconnects, with the same waking > connecting > ready / failed progress as an
owned restart. The panel offers Wake (the sidebar open path, which wakes paired rows since #571/#583)
and Restart on paired rows again; Archive and Move stay hidden until PAIRED-ARCHIVE.
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.
The waking card showed the control plane's code on a billing refusal (paired: "entitlement_denied";
owned: "Orca Cloud refused the request (entitlement_denied).") and offered Restart, which fails the
same way. Failed wake/restart/unarchive events now carry the plan's refusal (billingDenial), from
main's recipe resume, restart and unarchive and from the paired wake. The card uses the create
sheet's billing words, offers the one fix to an owner or admin (See plans, Raise spend cap, Update
payment method) and tells a member who to ask; running limits keep the shared workspace copy.
Starting a cloud workspace from a GitHub repository with no clone here showed only a
'Starting <repo> in Orca Cloud…' toast. It now opens the same build sheet as a cloud
create from a local clone: Start sandbox, Clone repository with git's progress, Open
workspace; the same failure cards and JA-21b billing blocker (plan, hours, spend cap,
payment; members get no See plans); Retry; and Back to draft (composer back on Orca
Cloud with the GitHub repository picked and the prompt kept).
Main: createFromGitHub runs the hosted driver's create path (createSandboxWithProgress,
shared with the owned create): boot plan, create, waitForClone, with the same
[orca-cloud] progress lines streamed on ephemeralVm:provisionEvent under the window's
creation id, the same failure reason lines and codes (hostedCreateFailure), Cancel via
ephemeralVm:cancelProvision, and an Idempotency-Key. The workspace id is fixed per
creation so a Retry sends the same body.
Renderer: the GitHub start is a pending creation with the Orca Cloud recipe and a
githubSource; retryBackgroundWorktreeCreation routes it to its own runner. A Retry
after a lost answer resends the same key (same sandbox back); after an answered failure
it is a new attempt; after a failed open it only opens the sandbox it already has.
The paired workspace has no environment-checks step.
* fix(cloud): PAIRED-STATUS one status path for paired cloud workspaces (main resolves a bound pairing; store registers paired rows)
getStatus/getArchive take { workspaceId, environmentId? }: main resolves this desktop's own runtime
first, else a paired server bound to a sandbox (findCloudSandbox), never an arbitrary sandbox.
The window registers each paired cloud workspace's own row (main checkout on a server the catalog
marks orcaCloudPaired) in the cloud workspace store's `paired` map, apart from the owned ids, so its
status lands in status[worktreeId] and every status surface reads it unchanged.
* fix(cloud): PAIRED-STATUS read worktrees through selectWorktreesByRepo (workspace-record ratchet)
* fix(cloud): PAIRED-AWARE paired Orca Cloud servers count as Orca Cloud everywhere (catalog marks bound servers; shared check and sandbox map include them)
* fix(cloud): PAIRED-AWARE paired-server mark held in memory from bindings reads and writes (no sync fs on main); catalog republishes on change