Files
strix/strix/tools/agent_browser/README.md
T
0xallam 4e73e8b0b8 Document the SDK-provided tools as stub dirs under strix/tools/
Every agent-facing tool now has a corresponding directory: the
strix-implemented ones already do, and the SDK-provided ones
(exec_command/write_stdin shell, apply_patch, view_image) plus the
sandbox-CLI agent-browser get README-only stubs. Each README names the
implementation source, where the tool is wired up, the strix-specific
config it inherits, and the skill that teaches its usage. Listing
strix/tools/ now gives a new reader the full agent toolset at a glance.

The stub dirs intentionally have no __init__.py — they are not Python
packages, just documentation. Nothing in the codebase auto-discovers
strix.tools.* as packages (all imports are explicit), so the stubs
cannot accidentally affect runtime behavior.
2026-05-25 22:23:14 -07:00

575 B

agent-browser

Browser automation CLI installed in the sandbox image. Driven by the agent through exec_command (not a function tool).

  • Implementation: sandbox CLI at /home/pentester/.npm-global/bin/agent-browser — npm package agent-browser@0.26.0 (Vercel), driving Chromium directly.
  • Strix config: containers/Dockerfile sets AGENT_BROWSER_* env (executable path, UA, launch args, screenshot dir).
  • Skill: strix/skills/tooling/agent_browser.mdalways-loaded into every agent prompt by strix/agents/prompt.py:_resolve_skills.