mirror of
https://github.com/stablyai/orca.git
synced 2026-11-16 02:47:34 +00:00
* docs: load Orca browser guidance for ordinary web tasks Extend the Orca CLI skill description to include local and external page opening, reading, testing, and captures while working in Orca. Preserve explicitly chosen browser tools and the Computer Use boundary. Regenerate discovery/install bytes and append the new digest. Fixes #39880 * fix: route existing Edge windows to desktop browser control * docs: preserve configured desktop-control tool precedence * docs(skills): scope orca-cli browser trigger to page work and keep the Computer Use rule Drop "reading" so doc lookups stay on fetch tools, say plain HTTP/API calls don't need the skill, and restore the original Computer Use sentence and guide body, which the issue didn't ask to change. * docs(skills): list Edge among existing browser windows in the orca-cli guide The wider page trigger makes "screenshot my open Edge tab" load orca-cli, and the guide named only Chrome and Safari as windows that go to desktop control. --------- Co-authored-by: Kelvin Amoaba <97001695+AmoabaKelvin@users.noreply.github.com>
50 lines
2.5 KiB
Markdown
50 lines
2.5 KiB
Markdown
---
|
|
name: orca-cli
|
|
description: >-
|
|
Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, worktree
|
|
comments, and Orca's embedded browser through the `orca` CLI. Use when the user says
|
|
"$orca-cli", "Orca worktree", "child worktree", "spawn codex/claude in a worktree",
|
|
"read/wait/send Orca terminal", "handoff" / "handover" / "give this to another agent", or
|
|
"Orca browser". Also use for opening, testing, screenshotting, or checking how a local or
|
|
external web page renders while working in Orca, unless the user or project names another
|
|
browser tool; plain HTTP or API calls (curl, fetch) do not need it. Prefer it over raw git
|
|
worktree, ad hoc PTYs, or Computer Use when Orca state is involved. Use Computer Use only
|
|
when a visible window needs GUI control that a CLI, filesystem, or API cannot do.
|
|
---
|
|
|
|
# Orca CLI
|
|
|
|
This discovery stub loads the version-matched guide from the Orca executable used for this session.
|
|
|
|
## Resolve the CLI for this session
|
|
|
|
Choose the executable once and reuse it for every later command:
|
|
|
|
- If the `ORCA_CLI_COMMAND` environment variable is set, use its value. Orca exports this
|
|
for managed WSL sessions.
|
|
- Otherwise, in a dev checkout whose session exposes `ORCA_DEV_REPO_ROOT`, use `orca-dev`.
|
|
- Otherwise, on Linux outside an Orca-managed terminal, use `orca-ide`. Never run bare
|
|
`orca` there — outside Orca's terminals it normally resolves to the
|
|
GNOME Orca screen reader (`/usr/bin/orca`) and starts speech on the user's machine.
|
|
- Otherwise, use `orca`.
|
|
|
|
Below, `ORCA` is a placeholder for the executable you resolved. Substitute it before
|
|
running anything; do not create a shell variable or run `ORCA` literally. This works the
|
|
same way in POSIX shells, PowerShell, and cmd.exe.
|
|
|
|
If the selected executable cannot run, report its exact error and stop. Do not fall through
|
|
to another executable, which could silently target a different Orca build.
|
|
|
|
## Load the version-matched guide before running Orca commands
|
|
|
|
```text
|
|
ORCA skills get orca-cli
|
|
```
|
|
|
|
Prefer `--json`. Use the selected executable's `--help` for commands or flags the guide does
|
|
not cover. If a command reports that Orca is not running, start it with `ORCA open --json`
|
|
and retry. If it fails with `runtime_access_denied`, your sandbox blocked the connection:
|
|
re-run it with escalated permissions, and do not run `ORCA open` or restart Orca. If
|
|
`skills get` is unknown, explain that updating Orca restores the guide; use `--help` for
|
|
read-only discovery and do not guess unsupported commands.
|