Reproduce chat errors, retries, parallel tool calls, and app creation in a running desktop application. Check how messages and cards appear, including interrupted replies, grouped steps, and error details.
Reproduce a known chat state in the running desktop on demand (model provider errors and retries, Code Mode and Den script failures, parallel tool steps, app creation, sequential commands) and check how it renders. Use when fixing or designing chat error, retry, tool-step or app-card UI.
Review the instructions the agent will receive before you install.
Each state below fires in a new session of the running desktop window through drive-desktop-cdp. Provider states also need fake-model-faults set up.
export CDP_URL=http://127.0.0.1:<cdp port>
R=.opencode/skills/reproduce-chat-states/scripts/repro.mjs
C=.opencode/skills/drive-desktop-cdp/scripts/cdp.mjs
node $R provider-refused && node $C wait-idle && node $C shot /tmp/refused.png
Run node $R with no argument for the list. Pass a second argument (or set GATEWAY_MODEL) to change the real model used for the non-fault states.
| State | Fires | Check |
|---|---|---|
provider-refused, provider-dns, provider-reset | engine transport error, retried, then final | one error per turn, plain title, raw text only behind the details icon |
provider-retrying | same as reset; watch the first 30s | "Reconnecting to the model" with attempt progress, no raw text |
provider-midstream, provider-stall | cut or stalled reply | interrupted reply keeps partial text |
http-429, http-5xx, http-401, http-402 | HTTP error bodies | the matching plain-language title and next action |
codemode-wrong-tool | tools.search(...) in Code Mode | a recovered step must not read as a hard failure |
den-script-rejected | Den script with .then | Den's real reason in details, not a generic placeholder |
den-script-service-failure | provider op fails inside a Den script | "Script on OpenWork Cloud failed", reason behind the icon |
den-script-parallel | 20 Slack calls in one script | one readable group, collapsed until opened |
parallel-searches | 10 Exa searches plus Slack | clean service names and logos, no routing ids |
app-create | MCP app build with retries | one card per app that advances through its steps |
sequential-commands | 5 separate bash calls | the chat does not jump (see measure-chat-flicker) |
Stored v2 history shows exactly what the engine recorded (useful when a step looks wrong):
sqlite3 ~/.config/openwork/opencode-v2/state/opencode.db \
"select type, substr(data,1,400) from session_message where session_id='<ses_…>' order by seq"
For a step inside Code Mode, check state.metadata.toolCalls and state.metadata.openworkMcpResults on the execute part.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Manage OpenWork feature releases with feature flags, switches that control access to new behavior. Register features before coding, release them by organization and deployment, prepare a global shutdown option, and remove temporary flags after rollout.
Connect OpenCode browser tools to a locally running OpenWork Electron app to inspect its UI, enter a task, and check the response. This skill supports exploration and debugging through CDP, Chrome's remote control protocol.
Check added lines in a change for information identifying customers, prospects, partners, or outside individuals. Report locations and generic remediation without reproducing identities, and escalate cases where the information is already public.
Connects supported AI clients, including Claude Code and Codex, to OpenWork through MCP, a protocol for accessing external tools. It guides account sign-in and verifies that tools for finding and running organization capabilities are available.
Review an outside contributor’s pull request before running its code. Identify concealed behavior, obfuscated code, risky dependencies, and build hooks, with file locations and specific checks for maintainers to follow up.
Create an OpenCode plugin for OpenWork with custom tools and hooks, which run code at specific events. The skill builds the plugin file and adds its entry to the project configuration.