agentleFS
LeostrukaLeostruka/devin-bundle/skills/cu-realtime/SKILL.md

cu-realtime

Skill0 starsChanged 3 months agoMITView on GitHub

Use when computer-use or terminal automation needs the fastest reaction the runtime allows - event waits instead of screenshot polling, text perception instead of image reads, whole perceive-act-verify cycles batched into one exec, or deterministic reflex loops below model latency. Composes with the `computer-use` skill (same extension CLIs).

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Never poll recv --tail in a decide-loop: Use recv <sid> --wait <REGEX> --timeout <deadline> - one call blocks until match (verified: hit …

    line 29
  2. Very specific:

    Batch inside one exec: when each step's precondition is deterministic or self-checked (--verify, --wait).

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

CU Real-time

Latency patterns for extensions/computer-use/, measured on this bundle (.devin/research/cu-realtime-{phase1,phase2,verdict}.md). The runtime floor is one model turn per cycle (~9.5s p50 measured) - nothing injects mid-turn, so "real-time" means one turn whose perceive+act+verify happen inside one tool call.

Domain ladder (try in order)

  1. TTY - terminal.py spawn/exec/recv --wait. Text output, blocking regex match, deterministic. Fastest channel.
  2. DOM - bound browser.py: eval/find/wait --selector|--text| --url|--fn; browser_events.py daemon for push streams.
  3. UIA - screenshot.py --hints under profile fast: visual bypass returns pure element JSON (capture:"skipped", ~250ms, ~1.4KB); mouse.py click --hint <id> / --via uia.
  4. Pixels - last resort: screenshot.py (+PNG + vision tokens + inference). Use --region when only an area matters.

Patterns (each measured)

  • Never poll recv --tail in a decide-loop. Use recv <sid> --wait <REGEX> --timeout <deadline> - one call blocks until match (verified: hit at ~event+0.2s, true timeout otherwise).
  • One cycle = one call: terminal.py exec '<cmd>' --wait <regex> does spawn+send+match+close in a single invocation (1 agent turn).
  • Batch inside one exec when each step's precondition is deterministic or self-checked (--verify, --wait). Blind click && sleep && click chains violate the action contract.
  • Async events: background subagent (is_background=true) that blocks on the event - its completion notification wakes the parent at the next turn boundary. Or a watcher daemon + cheap inbox poll.
  • Reflexes below model latency: terminal.py link <src> <dst> --limit N pipes one spawned PTY's output lines into another's input (measured 0.33s src->dst execution, zero model turns). Deterministic triggers only; the send/exec command gate applies per forwarded line and --limit is the brake. Resident (non-PTY) reflexes were proven in phase 4 but are prototype-only: a held-open ws eval poll reacts in ~16ms, a per-hwnd UIA enum poll + uia_invoke in ~54ms. Any reflex consumer MUST be resident - a subprocess per poll costs ~150-300ms and erases the reflex.
  • CU_SESSION=1: persistent worker daemon amortizes imports (~30-75ms/call on screenshot-class ops, ~0 on light ones). Optional.

Protocol gotchas (verified)

  • send-to payloads submit on \r, not \n - \n echoes the line without executing (cmd/ConPTY). The link pump appends \r itself.
  • A wait/match string must NOT appear literally in the command text (input echo = false positive). Assemble at runtime: set "M=PRE_" & call echo %M%MARK - call re-expands after set ran (cmd expands %VAR% at parse time per line).
  • --if-changed/--diff rarely skips on a live desktop (clock/cursor drift) - do not count it as the reperceive saving.
  • Provider elements (XAML/Notepad) carry hwnd: null in hint JSON: uia_perform and mouse.py --via uia return no_hwnd and silently fall back to a physical click. Use --channel uia --uia-name / cu_scope.uia_invoke(hwnd, name=...) to stay provider-side. UWP apps own multiple same-class hwnds and a stub pid - match windows by class + element presence, never by spawned pid.
  • dispatched never means done - reperceive via --wait/--verify.

Pointers

  • Full CLI contract: extensions/computer-use/USAGE.md
  • Evidence + thresholds: .devin/research/cu-realtime-verdict.md, reflex/UIA/laya ceiling data: .devin/research/cu-realtime-phase4.md
  • Harnesses: .devin/scratch/cu-realtime/ (s1_probe.py, p4_probe.py, p4_laya.py)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.