Menu
Launch FoxCode in User Profile mode. Guides user to load extension via about:debugging, opens connection page, verifies connectivity.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Launch FoxCode in Project Profile mode from Codex via the foxcode MCP server (`launchBrowser`). One tool call, no Python.
Launch FoxCode in Project Profile mode via the foxcode MCP server (`launchBrowser` tool). One tool call, no Python.
Test FoxCode distribution when asked to verify install/update paths, plugin packaging, marketplace contents, npm pack output, Claude Code plugin delivery, Codex plugin/config delivery, OpenCode package delivery, release readiness, or user-machine installation behavior.
Launch FoxCode in User Profile mode from Codex. Guides extension loading via about:debugging, opens connection page, verifies connectivity.
Quality-test the user-facing FoxCode skills (`foxcode-run-project-profile`, `foxcode-run-user-profile`) by spawning fresh subagents per probe so context cannot leak. Judges triggering accuracy, end-state correctness, robustness on negative prompts, and adherence to the SKILL.md flow. Use when asked to QA, audit, benchmark, regression-check, or smoke-test FoxCode skills, or to validate that a SKILL.md edit did not break the run flow.
Analyze historical Codex and Claude Code sessions for real FoxCode usage. Use when evaluating how effectively agents use FoxCode, evalInBrowser, launch skills, or browser automation across past sessions.
| name | foxcode-run-user-profile |
| description | Launch FoxCode in User Profile mode. Guides user to load extension via about:debugging, opens connection page, verifies connectivity. |
Load extension into user's Firefox, connect, verify. Communicate in user's language. Be concise — minimal output, no explanations unless something fails.
Source of truth: port, password, AND extensionDir come only from the MCP status response. Never read ~/.foxcode/* directly — those files may belong to a different server.
Call status.
connectedClients > 0 -> say "Ready." and stop.{port, password, extensionDir} from the response as PORT0, PASSWORD0, EXT_DIR.extensionDir is absent (older channel) -> tell user "Channel too old; upgrade foxcode-channel", stop.Tell user (single message, substituting values from step 1):
- Load extension:
about:debugging-> This Firefox -> Load Temporary Add-on ->{EXT_DIR}/manifest.json- Open in the same Firefox:
http://localhost:{PORT0}#{PORT0}:{PASSWORD0}Tell me when done.
Wait for user response.
Poll status every 3s, max 10 attempts (30s).
connectedClients > 0 -> "Ready."status one final time and compare with step 1:
port or password differ from PORT0/PASSWORD0 -> "MCP server restarted (port/password rotated). Re-run skill."