Beta. The Streampixel command line (version 0.1.0-beta.1) and the Streampixel MCP server are in beta. Commands, tools and their output can still change before the stable release.
- a Streampixel section in the project’s
AGENTS.md, read by Codex, Cursor and most coding agents; - a skill for Claude Code in
.claude/skills/streampixel/. Claude Code loads it only when a task is about Streampixel.
AGENTS.md is kept. Running init again updates only the Streampixel section.
streampixel init --dry-run shows what would be written, without writing anything.
What the agent does
The agent runs every command with--json and acts on the result. See Scripts and CI for the output format and codes.
- If you are not signed in, it asks you to run
streampixel loginyourself. It never signs in for you and never asks for a password or token. - When
doctororpackagereports a problem, it fixes it and runs the same step again. - For a password-protected project, you put the viewer password in an environment variable. The agent passes only the variable’s name, with
--password-env.
With the other tools
The command line works alongside two other tools, each with its own job:- Unreal MCP, Epic’s server inside the Unreal Editor (5.8 and later, experimental in Unreal), changes the project: assets, Blueprints, levels, settings. When
doctororpackagereports a problem in the project, the agent fixes it there. - The command line checks, packages, uploads, deploys and tests.
- The Streampixel MCP reads your account. After
test, the agent can pass the session id todiagnose_session, or a build id toget_build_status.