mirror of https://github.com/usestrix/strix.git synced 2026-08-16 17:27:26 +02:00

Files

T

0xallam 867a0c81fc 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

795 B

Raw Blame History

shell — `exec_command` + `write_stdin`

SDK-provided shell tools wired per-run from the sandbox session. Every CLI invocation the agent makes (nmap, ffuf, agent-browser, python3, …) goes through exec_command. write_stdin streams input to a still-running process started by an earlier exec_command (for interactive prompts).

Implementation: agents.sandbox.capabilities.tools.shell_tool.ShellTool (in the upstream agents SDK)
Wired in: strix/agents/factory.py — added per-run via the SDK Shell capability; write_stdin is wrapped to drop the SDK's pid arg from the function schema.
Sandbox env: http_proxy / https_proxy route every shell child through Caido; AGENT_BROWSER_*, REQUESTS_CA_BUNDLE etc. come from containers/Dockerfile.

795 B Raw Blame History

shell — exec_command + write_stdin

795 B

Raw Blame History

shell — `exec_command` + `write_stdin`