The browser loop,
at your command.

The commands you’ll use most.

Ref numbers below are placeholders. Use the numbers from your own page. Run gripui <command> --help for exact options.

Look

gripui hud

Read the page’s numbered actions and current state.

gripui read

Read the visible page text.

gripui find "Submit"

Find a known label after orienting with the HUD.

gripui form

Inspect fields, values and validation errors.

Act

gripui do <ref>

Run a current numbered action.

gripui type <ref> "text"

Clear and type into a specific field; verify the result.

gripui say "text"

Paste into the already-focused field. No ref argument.

gripui scroll

Scroll the page, then refresh the HUD.

Manage context

gripui attach <name>

Bind this job to a named browser profile.

gripui tab list

List tabs; use gripui tab switch t2 to select an observed tab.

gripui frame list

List frames; switch to the observed frame containing the controls.

gripui detach

Release your claim while retaining the browser.

Handoff & diagnose

gripui human-drives

Hand the browser to a person for authentication.

gripui agent-drives

Return control, then refresh the HUD.

gripui doctor <ref>

Inspect why a field rejects input.

gripui transcript --path

Find the session transcript.

Captured output / Cloudflare Pages

Same label.
Different action.

Both links say “Get started.” The surrounding context tells the agent which imports a repository and which uploads files.

   [148] click link:"Create a Worker"
      * Get started
        [149] click link:"Get started" context="Import an existing Git repository"
        [150] click link:"Get started" context="Drag and drop your files"
    *

Actual HUD excerpt from a visible Cloudflare session. Ref numbers are session-specific. Names and context are separate; uncertain associations are omitted.

A profile belongs to a job.

gripui attach work binds the job and writes the project choice to .gripui.json. There is no implicit default. Another job cannot attach a profile already owned by a live job.

For automation, set a stable GRIPUI_JOB_ID for the logical job. An explicit --profile is a one-command shared-control override; it does not transfer ownership.

gripui detach releases ownership and keeps the browser. gripui quit ends that profile’s session. MCP uses the same profile model.

When the page surprises you.

• Page changed? Refresh gripui hud and use the new observation.
• Popup open? Use gripui hud --layer active.
• Control missing? Scroll, inspect frames, then look again.
• Input rejected? Use gripui doctor <ref>.
• Login or CAPTCHA? Hand the browser to a person.
• Timed-out write? Check the result before retrying.

Run gripui status for session state. The full skill covers active layers, tabs, profiles, recovery and command options.