Measure chat layout jumps while a response runs by tracking the Working line through CDP, a browser debugging connection. Count upward movements and compare the same prompt before and after changes to status lines, step rows, or folding behavior.
Measure whether the chat jumps while a turn runs by sampling the Working line's position over CDP and counting upward moves. Use when changing step rows, live status lines, folding, or anything that can shrink content during a run.
Review the instructions the agent will receive before you install.
Content growing below is normal. Content shrinking during a run (a live line removed, a group closing) moves everything up, and that reads as flicker. This counts those upward moves.
export CDP_URL=http://127.0.0.1:<cdp port>
M=.opencode/skills/measure-chat-flicker/scripts/flicker.mjs
node .opencode/skills/drive-desktop-cdp/scripts/cdp.mjs new-session
node $M arm
node .opencode/skills/reproduce-chat-states/scripts/repro.mjs sequential-commands
node .opencode/skills/drive-desktop-cdp/scripts/cdp.mjs wait-idle
node $M report # { upwardJumps, downwardMoves, samples }
Note: repro.mjs opens its own new session, so arm after it if you need the arm to survive the navigation, or run send directly.
upwardJumps during the run should be 0. One at the very start (the first step replacing "Starting…") is acceptable.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.