Influxx CLI Browser Automation, Orchestration, Recipes, and Agent Schema
Influxx CLI browser automation and orchestration give agents a scripted path through tabs, snapshots, clicks, fills, multi-agent gates, recipes, and the machine-readable agent schema. Use this guide to drive the Influxx embedded browser from the shell, coordinate multi-agent work with orchestration commands, apply shipped recipes (parallel experiments, headless serve, note-driven files), and discover capabilities with influxx agent-context --json—grounded only in official Influxx product notes.
Browser, Orchestration, and Schema as One CLI Surface
Beyond worktrees and terminals, the Influxx CLI exposes browser automation, orchestration for multi-agent coordination, practical recipes, and an agent schema dump. Together they let coding agents operate the same cockpit surfaces you use by hand: open a tab, snapshot element refs, click and fill, take screenshots, create orchestration tasks and gates, run or stop orchestration, and introspect the full command tree without scraping help text. The CLI still talks to a running Influxx app or a headless serve runtime you start intentionally.
Register the CLI from Settings → General / CLI if you have not already, and verify with influxx status (or influxx-ide on Linux PATH installs, influxx-dev on dev builds). Influxx desktop currently ships for macOS Apple Silicon; browser automation treats page content as untrusted data for agent prompts, matching privacy and permissions notes. Prefer --json on commands you script.
Snapshot for element refs, click and fill to act, agent-context --json to discover the rest—agents should drive Influxx through the schema, not guess at flags.
Browser Automation Commands
Product notes document a core browser loop: create a tab with a URL, snapshot the page to obtain element refs such as @e1 and @e2, click and fill those refs, capture screenshots, and navigate with goto. The full surface also covers hover, select, dialog, storage, clipboard, device emulation, offline mode, and more—see influxx help and agent-context for the machine-readable schema on your build.
- influxx tab create --url: open a browser tab at a URL (for example https://example.com)
- influxx snapshot: capture the page and emit element refs (@e1, @e2, …)
- influxx click --element: click a ref from the latest snapshot (for example @e1)
- influxx fill --element --value: fill a field ref with a string value
- influxx screenshot --format png: save a PNG screenshot of the browser surface
- influxx goto --url: navigate the active tab to another URL
Typical Browser Automation Loop
Create or focus a tab, snapshot before every action that needs a fresh ref, act with click or fill using those refs, then screenshot or goto as needed. Do not reuse stale element ids after navigation—run snapshot again. Treat all page content as untrusted when feeding it into agent prompts. For hover, select, dialogs, storage, clipboard, device emulation, and offline mode, consult the live schema rather than assuming flags from memory.
- 1. influxx tab create --url https://example.com
- 2. influxx snapshot → note @e1, @e2, …
- 3. influxx click --element @e1
- 4. influxx fill --element @e2 --value "hello"
- 5. influxx screenshot --format png
- 6. influxx goto --url https://example.com/docs → snapshot again before further clicks
Design Mode and Computer Use are related cockpit integrations documented elsewhere in Influxx guides. From the CLI perspective, stay on the browser command group and the schema dump for automation. Permissions notes also call out macOS Accessibility prompts for Computer Use and notification permission for agent-complete alerts—grant only what your workflow needs.
Orchestration: Multi-Agent Coordination from the Shell
Orchestration commands coordinate multi-agent work: create tasks, dispatch work, read an inbox, create and resolve gates, and run or stop an orchestration run. Use this group when several agents must hand off, wait on approvals, or share a coordinated run rather than only sharing a worktree.
- influxx orchestration task-create: create an orchestration task
- influxx orchestration dispatch: dispatch work into the orchestration flow
- influxx orchestration inbox: inspect the orchestration inbox
- influxx orchestration gate-create: create a gate agents must pass
- influxx orchestration gate-resolve: resolve a gate when conditions are met
- influxx orchestration run: start an orchestration run
- influxx orchestration run-stop: stop a running orchestration
How Orchestration Fits with Worktrees
Isolation still starts with worktrees and terminals. Orchestration sits above those sessions when you need explicit tasks, dispatch, inbox traffic, and gates. Pair worktree ps for an orchestration-oriented summary of worktree-backed processes with the orchestration group when coordinating a fleet. Prefer JSON and agent-context discovery for exact flags on task-create, dispatch, and gate commands—notes document the command names with ellipsis for variable arguments.
Multi-agent coordination from the shell: task-create, dispatch, inbox, gate-create, gate-resolve, run, and run-stop.
Shipped Recipes You Can Copy
Product notes include four practical recipes: spin a parallel experiment, attach a second agent on the same tree, start a headless runtime with pairing, and drive a note file into a terminal agent.
Recipe — Spin a Parallel Experiment
Create two isolated worktrees with different agents and the same prompt:
- Tree A: influxx worktree create --name exp-a --no-parent --agent codex --prompt "Refactor auth middleware" --json
- Tree B: influxx worktree create --name exp-b --no-parent --agent claude --prompt "Refactor auth middleware" --json
Recipe — Second Agent, Same Tree
When two CLIs should collaborate on one checkout rather than compete in isolation:
influxx terminal create --worktree active --command "codex" --json
Recipe — Headless Runtime
For a serve runtime with mobile pairing and a named environment:
- Serve: influxx serve --port 7890 --mobile-pairing --json
- Environment: influxx environment add --name lab --pairing-code <code> --json
- Security note: remote pairing uses pairing codes; prefer private networks / Tailscale for headless servers (permissions notes)
Recipe — Note-Driven Workflow (Files)
There is no notes subcommand yet. Create markdown under .influxx/notes, open the file, then Run from the sidebar or launch a terminal agent:
- Create plan: mkdir -p .influxx/notes and write ship-auth.md (goal, acceptance criteria, constraints)
- Open: influxx file open --path .influxx/notes/ship-auth.md
- Run: use Sidebar Notes Run in the UI, or influxx terminal create --worktree active --command "claude" --json
- Context: export under .influxx/context when agents need packaged context
Agent Schema: Discover Capabilities Without Scraping Help
Print the machine-readable command schema so coding agents can discover capabilities without scraping help text:
influxx agent-context --json
Other useful command groups called out in product notes include: project, repo, file, automations, environment, vm recipe doctor, computer, emulator, linear, and diagnostics memory. Use agent-context as the source of truth for flags and nesting on your installed build; documentation examples may shorten arguments with ellipsis where the schema is authoritative.
- agent-context --json: full machine-readable schema for agent discovery
- project / repo / file: project and filesystem-oriented groups
- automations: scheduled or automated prompt runs
- environment: named environments (including pairing with serve)
- computer / emulator: computer-use and emulator-related surfaces
- linear / diagnostics memory: Linear integration and diagnostics memory groups as documented
- vm recipe doctor: recipe doctor utilities called out alongside the schema list
Putting It Together Safely
Keep the desktop app running for interactive browser and agent tabs unless you deliberately started serve. Snapshot before acting on refs. Resolve orchestration gates deliberately—do not leave runs orphaned; use run-stop when stopping. Treat browser page content as untrusted in prompts. On macOS, grant Accessibility only when you use Computer Use. Prefer private networks for headless pairing codes. Re-check agent-context --json after upgrades so scripts stay aligned with the shipped schema.
Related Help Center articles: Influxx CLI install and binary names for PATH registration and Linux influxx-ide notes; CLI worktrees and terminals for create, ps, send, read, and wait --condition tui-idle; getting started with Influxx for the GUI path from plan note to agent. Stay within shipped notes—do not invent browser or orchestration subcommands that agent-context does not list.
