Setup

The primary way agents drive SootSim is the sootsim CLI. Use the same sootsim path a human uses after the global install; there is no separate agent install.

From inside any agent (Claude Code, Cursor, Codex, or anything that can run shell commands), sootsim describe, sootsim do tap-text "Sign in", and the rest of the CLI work against whatever sim is running.

Start the app’s existing Metro, Expo, React Native, or One server yourself. SootSim does not own that process. Run sootsim open <port> from the app project root so font, splash-screen, and project-configuration discovery has the same context as the development server.

#Verifying

With a sim open:

sootsim compat         # scan this app's React Native dependencies
sootsim list           # should show at least one connected tab
sootsim describe       # dumps the current screen

If list is empty, start a sim first (sootsim open <port> or your usual dev flow), then retry.

If the scan or live app exposes a missing SootSim compatibility seam, the agent should explain the finding and offer to send it with sootsim report-issue. Nothing is submitted until you explicitly agree. The command previews its bounded attachment set before sending; see Reporting Issues.

#Skills

We ship a handful of skill files that teach agents how to use SootSim well: setup, debugging, accessibility, perf, visual regression, and test flow authoring. The global CLI installs them into the standard agent skill homes:

sootsim skill install
sootsim skill install codex
sootsim skill install --target .claude/skills sootsim-debug

Available: sootsim-setup, sootsim-debug, sootsim-perf, sootsim-visual, sootsim-test, and contrast. Pick what matches your task, then restart the agent session so it reloads the skill list.

#What’s next

• CLI Use: the day-to-day commands an agent runs.
• Agent Devtool (Inspect): the in-sim panel where you talk to an agent and watch it work.