Cassiiopeia/projectops / plugins/projectops-extras/skills/pro-remote-link
pro-remote-link
VerifiedGive one link to open a desktop agent app (Orca, Paseo) on this computer from outside: Orca through a cloudflared quick tunnel and its saved pairing link, Paseo through its relay pairing link. Use for 'Orca link', 'Orca URL', 'Orca tunnel', 'Paseo link', 'remote link', 'open from outside'.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.7 KB |
| harness/orca.md | markdown | 3.0 KB |
| harness/paseo.md | markdown | 4.3 KB |
| scripts/remote_apps/__init__.py | script | 961 B |
| scripts/remote_apps/orca.py | script | 1.6 KB |
| scripts/remote_apps/paseo.py | script | 7.5 KB |
| scripts/remote_link_cli.py | script | 11.2 KB |
| scripts/tunnel/__init__.py | script | 105 B |
| scripts/tunnel/links.py | script | 3.2 KB |
| scripts/tunnel/probe.py | script | 2.9 KB |
| scripts/tunnel/proc.py | script | 4.1 KB |
| scripts/tunnel/processes.py | script | 6.5 KB |
| scripts/tunnel/state.py | script | 2.3 KB |
harness/orca.md
View on GitHub# Orca facts (harness)
> Orca is open source and changes often. Everything here can go stale. When a step below fails, find the new fact,
> write it into the local copy `~/.projectops/remote-link/harness/orca.md` (create it from this file), add a line under
> "Change log", and tell the user. The local copy wins over this file.
Last checked: Orca 1.4.253 on macOS, 2026-11-11. Windows and Linux lines marked "not checked yet" are best guesses.
## Where Orca Web listens
- Port **6768** (the desktop app's built-in web server, bound to all interfaces).
- Check: `local --port 6768` returns `title: "Orca Web"`.
- If 6768 does not answer: `ports --process orca` lists the ports the Orca process listens on (works on macOS, Windows
and Linux); run `local --port N` on each and take the one titled `Orca Web`.
- `apps` uses the same port and title (`scripts/remote_apps/orca.py`). If they change, its `ports` fallback still
finds Orca Web, but update both.
- Not Orca Web: the second, loopback-only port (for example `127.0.0.1:61115`) answers 404 at `/`.
## If Orca is not running
- macOS: `open -a Orca`.
- Windows (PowerShell, not checked yet): `Start-Process "$env:LOCALAPPDATA\Programs\Orca\Orca.exe"`;
if that path is missing, find `Orca.exe` under `$env:LOCALAPPDATA\Programs` or the Start menu shortcut.
- Linux (not checked yet): start the `orca` desktop entry or AppImage the user installed.
- Wait up to 30 seconds and check again. Still nothing: tell the user Orca desktop is not running on that computer and stop.
- When you confirm a Windows or Linux path, replace "not checked yet" with the version and date.
## The link the user opens
- Shape: `https://<tunnel>/web-index.html#pairing=<percent-encoded orca://pair?code=...>`
- The `code` is base64 of a JSON object. Its `endpoint` is `wss://<tunnel host>`; the rest
(`deviceToken`, `pairedDeviceId`, `publicKeyB64`, `hostDescriptor`) binds the browser to this Mac.
- Only the tunnel host changes between tunnels. `link get` swaps every `*.trycloudflare.com` inside the link,
including inside the base64 JSON, without knowing the field names.
- The page to check through the tunnel: `/web-index.html`.
## Getting a fresh pairing link
- In Orca desktop the user creates a link for a browser or phone (the mobile / web pairing entry in the sidebar).
The user pastes it in chat. Save it with `link save --app orca` (the link goes in `TUNNEL_LINK`, never on the command line).
- A saved link keeps working while that paired device is still listed in Orca. Paired device ids are in
`orca-devices.json` in Orca's app data folder: macOS `~/Library/Application Support/orca/`,
Windows `%APPDATA%\orca\` (not checked yet), Linux `~/.config/orca/` (not checked yet).
If the user removed the device in Orca, the old link is refused and a fresh one is needed.
## Change log
- 2026-11-11: first version.
- 2026-11-15: skill renamed to pro-remote-link (CLI `remote_link_cli.py`); the local copy lives at `~/.projectops/remote-link/harness/orca.md`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |