- COPILOT_GITHUB_TOKEN on api.github.com: GET /user and GET /copilot_internal/* only (normalized
paths; dot or encoded segments refused); the Copilot API hosts are unchanged. It resolves like
an env variable (personal beats team): it is one person's GitHub identity.
- Routine summaries for opencode (JSON events), cursor (JSON result) and copilot (--silent) are the
agent's final message, and every summary has the session's secret values replaced before it can
be posted as a comment or PR body.
- Webhook/GitHub context in a routine prompt is capped at 48 KiB (compact, then cut), so a prompt
passed as one argv entry stays under Linux's 128 KiB limit.
- A test fails if an agent credential is neither swapped nor marked 'Stored on workspace'.
- COPILOT_GITHUB_TOKEN: placeholder in the VM, swapped on api.github.com (Bearer or token form, next to
the workspace token's own route) and on the Copilot API hosts (left open for Copilot's own session
token). GOOGLE_API_KEY: swapped on generativelanguage.googleapis.com and aiplatform.googleapis.com
(Vertex express). A credential may now route to several hosts.
- Routines accept claude, codex, opencode, gemini, cursor and copilot; the in-VM runner has a
headless command for each (checked against a local stand-in model: prompts starting with '-' stay
prompts). The editor picks the agent from a list.
- AWS_* keys (SigV4, signed in the VM) and Bedrock API keys can't be swapped: the secrets UI marks
them 'Stored on workspace' with the reason, in the list, the .env preview, the effective view and
the editor.
- Gemini's auth method is seeded for GOOGLE_API_KEY too (vertex-ai with GOOGLE_GENAI_USE_VERTEXAI);
headless Gemini refuses to start without one.
Copilot prefers GH_TOKEN/GITHUB_TOKEN over a stored /login. In Orca Cloud those hold the workspace
GitHub App placeholder, so every Copilot start said 'Resource not accessible by integration' and a
user who signed in could never use it. A wrapper drops the two placeholders for Copilot only, unless
BYOK is configured (no GitHub sign-in needed; gh in Copilot's shell keeps working).
- assertUndoCovers never asks batch-check about a path with a newline (counts as
unsaved), so answers can't shift.
- The workspace-busy probe matches rows by workspace id or worktree realpath and
treats a truncated listing as busy.
- Rewind dialog opens with focus on Cancel; a disabled option reads as disabled.
- Notes: unreadable tracked deletes keep their staged blob; the turn-starting
mark is process-local by design.
- Refuse a restore that would write or delete inside a nested repository, and
verify every on-disk path it touches is in the undo tree first (git add can
skip a path without failing).
- A turn counts as busy from its snapshot until the hand-off; terminal agents
working in the workspace make restores refuse; the preview reports busy and
the dialog disables the files choice.
- W10 copy: statement description, i18n plurals, state-dependent detail line,
option directly under the description, 'The chat was rewound, but…' errors.
- Index restore keeps skip-worktree bits; large-file scan honours the deadline.
- Component fixture for the rewind prompt states.
- A restore that fails partway names its undo point; the error toast offers Undo.
- Refuse when an ignored file sits where the checkpoint needs a folder, or when
a file to overwrite is unreadable (neither could be saved first).
- Busy check runs inside the per-worktree queue and covers every chat in the
worktree; the rewind stays pending until files are back.
- add --ignore-errors exit 1 (unreadable/nested repo) no longer disables
checkpoints; untracked files over 10 MB are left out of snapshots (saved only
if a restore would overwrite them); one deadline per capture.
- Skip-worktree/assume-unchanged entries are left alone; stale temp indexes swept;
retention never prunes the checkpoint just written.
Before each turn a message opens, the host snapshots the chat's worktree as a
stash-like commit under refs/orca/checkpoints/<session>/turn/<item> (working
tree incl. untracked files, staged tree as second parent), via a private temp
index. HEAD, the branch, the user's index and the stash list are untouched.
Rewind to here now offers 'Also restore files (N changed)', on by default when
a snapshot exists. Restore first saves an undo checkpoint (also covering ignored
files it overwrites), refuses on merge conflicts or file/folder clashes before
writing anything, never moves HEAD, and restores staging only while HEAD is
unchanged. The toast offers Undo. Retention: newest 50 turn / 10 undo
checkpoints per chat, nothing older than 30 days.
Measured: capture p50 356 ms on a 40k-file repo, 637 ms on 200k files; restore
0.44 s / 0.78 s.
* feat(cloud): pdx1 default region with iad1 fallback and one golden per region; Standard is 8 vCPU / 16 GB (U17, U18)
- golden_images and environment_builds record their region (0040, backfilled iad1); rotation,
git-source builds, smoke and activation run per region; lifecycle picks the region's golden.
- New creates default to pdx1; a create with no pinned region falls back to iad1 automatically on a
capacity/provider error (VERCEL_FALLBACK_REGIONS). Until pdx1 has an image, creates use iad1.
- Environment builds boot and smoke in their own region; workspaces from a build boot there.
- One size: Standard = 8 vCPU / 16 GB (ORCA_CLOUD_SANDBOX_SPEC). Legacy 'large' requests map to
standard; 0040 rewrites existing large rows.
* merge cloud/integration (ORCA_CLOUD_SANDBOX_SPEC landed in #196)
Found on m4air: with the right sidebar open the titlebar strip isn't rendered, so the button also
sits next to Quick Commands in the (focused) tab strip; workspace.run is dispatched by the global
keybinding handler; the primary action is the last one still running, else the default.
Hosts with credential rules (model APIs, api.github.com) are answered by Vercel's egress proxy with a
certificate from its CA. Vercel's command env trusts it (NODE_USE_SYSTEM_CA, NODE_EXTRA_CA_CERTS,
SSL_CERT_FILE) but orcad starts under env -i, so Node clients in terminals used Node's bundled roots:
Gemini CLI retried forever ('This is taking a bit longer') while the same call from a command
returned at once. Found on the live proof of the new agents; NODE_USE_SYSTEM_CA=1 in the terminal
fixed it there (1 s to the provider's answer).
Staging sign-in now works end to end in dev without a dev operator key on the user's machine.
Same account ids as billing dev (which trusts staging already); never honored when SANDBOX_ENV=prod;
a staging key cannot pass as the prod issuer.