CLI
CLI Non-Interactive Usage
Best practices for CI runners, agents, and scripted CLI execution.
Non-Interactive Guidelines
- Pass an explicit
--nameon every command in the sequence. - If commands may run from different working directories, also pass
--root-dir. - Do not rely on the implicit
defaultsession in CI or agents. - Prefer
extractwith stable descriptions for replayable data collection. - Re-run
snapshot actionorsnapshot extractionafter page changes before using counters.
Quick Start: CLI
## Open a browser session and bind a selector namespace
opensteer open https://example.com --session demo --name quickstart
## Action snapshot + interaction
opensteer snapshot action --session demo
opensteer click --description "main call to action" --session demo
## Cursor controls
opensteer cursor status --session demo
opensteer cursor off --session demo
## Extraction snapshot + structured extract
opensteer snapshot extraction --session demo
opensteer extract '{"title":"string","href":"string"}' --description "hero section" --session demo
## Close session
opensteer close --session demo
For non-interactive runs, set OPENSTEER_SESSION or OPENSTEER_CLIENT_ID.
Runtime daemon routing for OPENSTEER_SESSION is scoped by canonical cwd
(realpath(cwd)) + logical session id.
Cursor defaults:
- CLI sessions: enabled by default (toggle with
--cursororopensteer cursor on|off) - SDK instances: disabled by default (set
cursor.enabled: trueto opt in)
Covered Features
cli:extractcli:snapshot
