axstream

axstream — replay UI tasks instead of re-deriving them

First decision: delegate multi-step UI work to the computer-use subagent

If your harness has a Task/Agent tool and an agent named computer-use (plugin form: axstream:computer-use) is available, DELEGATE any multi-step UI task to it instead of driving the UI from the main conversation. It runs on a fast model with exactly the tools below, replays a matching macro when one exists, drives novel tasks as batched verified actions, saves a macro on success, and returns a compact outcome report — so screenshots and OCR dumps never enter your context, and your own turns stay fast for the rest of the session. It can run in the background while you continue other work.

• Delegate: "open X and do Y then Z", click-through flows, reproduce-a-bug in a running app, verify-something-on-screen, anything worth a macro.
• Do it yourself (tools below): a single action, or when you must reason about visual state mid-flow.
• Authorize explicitly: if the task includes an irreversible step (send, pay, delete), name that exact step in the delegation prompt — the agent refuses risk:"risky" ops it wasn't explicitly given.

Fast primitives (axstream MCP tools, if connected)

When the axstream MCP server is available, prefer its primitives over screenshot-driven computer use for mechanical steps — they run on-device in milliseconds and return text, not images:

• screen_text (~200ms) — the window as text lines with coordinates. Use INSTEAD of a screenshot to learn what's on screen.
• find (~30-600ms) — locate one control/text; returns a click-ready target.
• act — a whole batch of actions in ONE call (open/click/type/key + assert guards). Plan the sequence once; don't take a model turn per step.
• check (~250ms) — verify an outcome ("results page shows my query") without a verification screenshot.
• begin_capture + compile_capture — wrap Codex's initialized native sky computer-use object, record successful actions plus their preceding AX state, then compile that real trace into a parameterized macro. This is the native fallback bridge; cua-driver's recorder cannot observe sky calls.