| name | openwork-debug |
| description | Debug OpenWork sidecars, config, and audit trail |
Set these before running the HTTP checks:
OPENWORK_SERVER_URLOPENWORK_SERVER_TOKENOPENWORK_WORKSPACE_ID (optional; use /workspaces to discover)curl -s "$OPENWORK_SERVER_URL/health"
curl -s "$OPENWORK_SERVER_URL/capabilities" \
-H "Authorization: Bearer $OPENWORK_SERVER_TOKEN"
curl -s "$OPENWORK_SERVER_URL/workspaces" \
-H "Authorization: Bearer $OPENWORK_SERVER_TOKEN"
curl -s "$OPENWORK_SERVER_URL/workspace/$OPENWORK_WORKSPACE_ID/config" \
-H "Authorization: Bearer $OPENWORK_SERVER_TOKEN"
curl -s "$OPENWORK_SERVER_URL/workspace/$OPENWORK_WORKSPACE_ID/audit?limit=25" \
-H "Authorization: Bearer $OPENWORK_SERVER_TOKEN"
opencode -p "ping" -f json -q
opencode mcp list
opencode mcp debug <name>
When the engine API is unavailable, you can inspect the SQLite db:
sqlite3 ~/.opencode/opencode.db "select id, title, status from sessions order by updated_at desc limit 5;"
sqlite3 ~/.opencode/opencode.db "select role, content from messages order by created_at desc limit 10;"
.opencode/openwork/audit.jsonl in the workspace root.
Test the real Electron app on Daytona: create sandbox, start services, connect via CDP, create workspaces, drive sessions, and verify settings. Use when the user says 'test on Daytona', 'run the app on Daytona', 'Daytona dry run', 'test Electron remotely', or 'reproduce on Daytona'.
Guide users through the get started setup and OpenWork Browser demo.
Run OpenWork UI evals on a Daytona sandbox or local Electron instance. Handles sandbox creation, service startup, and eval execution via CDP browser tools.
Workspace guide to introduce OpenWork and onboard new users.
Publish the openwork-orchestrator npm package with clean git hygiene. Triggers when user mentions: - "openwork-orchestrator npm publish" - "publish openwork-orchestrator" - "bump openwork-orchestrator"
Step through versioning, tagging, and verification