VCW / AGENT CONTROL

Give your agent eyes,
actions, and guardrails.

VCW is local-first. An agent connects to the API running on your own machine; it does not receive a public remote-control endpoint by default.

1. Start the local control plane

cd website/v1/ai/vibecodeworker\n$env:VIBE_API_TOKEN = "choose-a-long-random-secret"\nnpm run start:cloud

The API listens on http://127.0.0.1:42069. Keep its token private; it is required for state-changing requests from non-loopback clients.

2. Connect through MCP

VCW includes a stdio MCP bridge. Add this to your MCP client configuration, adjusting the absolute path to your clone:

{\n  "mcpServers": {\n    "vcw": {\n      "command": "node",\n      "args": ["C:/path/to/4weird/website/v1/ai/vibecodeworker/server/vcw_mcp_server.js"],\n      "env": { "VCW_API_URL": "http://127.0.0.1:42069", "VIBE_API_TOKEN": "…" }\n    }\n  }\n}

Tools: vcw_status, vcw_list_games, vcw_launch_game, vcw_get_state, vcw_get_logs, vcw_send_action, vcw_create_bug, and vcw_generate_handoff.

REST API

curl http://127.0.0.1:42069/api/status\ncurl -X POST http://127.0.0.1:42069/api/game/launch -H "Content-Type: application/json" -H "X-Vibe-Auth: $VIBE_API_TOKEN" -d '{"gameId":"friendslop"}'

Read-only endpoints include status, games, state, logs, dashboard, and vision state. Use the API token for actions, launches, bugs, or repair flows.

Control policy

Start read-only: inspect status, games, logs, and state first.
Ask before launching unknown targets, sending input, editing files, or starting cloud work.
Never expose port 42069 publicly without authentication and a network policy.
Use vcw_generate_handoff to persist a concise, reviewable context brief.

Agent runbook