Verify OpenWork changes by running the real product and following user or client actions. Choose suitable tests, capture screenshots and reports, and demonstrate that the check fails on dev but passes on the changed branch.
Prove an OpenWork change works on the real product before calling it done. Start the product, drive the change the way a user or client would, capture screenshots, and show the proof fails on dev and passes on your branch. Use before opening a PR, when a reviewer asks "show me", or when a core journey is red.
Review the instructions the agent will receive before you install.
A change is done when you have watched it work on the real product, not when it
compiles. The committed e2e suite is only the nine core journeys in
evals/journeys.ts; everything else is proved per PR and thrown away.
| The change is… | Prove it with |
|---|---|
| a server rule (permissions, isolation, validation, secrets) | an API test next to the code, e.g. ee/apps/den-api/test/api/*.api.test.ts (pnpm --filter @openwork-ee/den-api test:api) |
| a pure function or component logic | a colocated unit test |
| something a person or client does end to end | a proof: evals/proofs/<name>.proof.test.ts (write-a-spec) |
| one of the nine core journeys broke or changed | a step in that journey, evals/core/<journey>.e2e.test.ts |
pnpm world up dev-app-web --detach -- --browser # this checkout in headless Chrome; prints webUrl and cdp
pnpm world down dev-app-web # when done
Use a desktop window only for desktop-shell changes (see drive-desktop-cdp).
Den needs MySQL and Redis on localhost (pnpm dev:den:mysql, or a local MySQL
via OPENWORK_EVAL_MYSQL_URL=mysql://root@127.0.0.1:3306).
drive-desktop-cdp (new session, send, wait, screenshot).pnpm evals:e2e <name> --local; screenshots and the report land in
evals/results/test-runs/<latest>/.Drive the real user path. No internal setters, no test-only endpoints, no
reading app state; pnpm --dir evals lint:specs rejects those in proofs.
A proof that passes on dev proves nothing about your change. Run it on both:
git worktree add /tmp/ow-base origin/dev
cp evals/proofs/<name>.proof.test.ts /tmp/ow-base/evals/proofs/
(cd /tmp/ow-base && pnpm install --frozen-lockfile && pnpm evals:e2e <name> --local) # must fail
pnpm evals:e2e <name> --local # must pass
git worktree remove /tmp/ow-base
If it passes on dev, the assertion is looser than the change: tighten it.
Open the PR with open-a-pr. CI runs your proof and the nine core journeys on
the PR head and posts the evidence. Name the proof and its before → after in
the PR's Evidence section.
| Journey | What it proves | Run |
|---|---|---|
org-invite-join | an owner invites someone and they join with the right role | pnpm evals:e2e org-invite-join --local |
core-chat | a signed-in person sends a message and reads the reply | pnpm evals:e2e core-chat --local |
thread-continues-after-restart | a conversation, queued follow-up and draft survive a restart | desktop; pnpm evals:e2e thread-continues-after-restart --local |
agent-connection-journey | a connector call in chat shows what was called and what came back | pnpm evals:e2e agent-connection-journey --local |
agent-permissions | blocked commands stay blocked; allowed ones run | pnpm evals:e2e agent-permissions --local |
app-smoke | the packaged desktop app opens to a working screen | packaged smoke (apps/desktop/scripts/packaged-smoke.mjs) |
packaged-update-install | an installed app downloads and installs a newer build | macOS packaged smoke |
agent-signup-via-mcp | an MCP client connects, searches capabilities and runs one | pnpm evals:e2e agent-signup-via-mcp --local |
secure-keys-in-chat | keys stay out of the transcript, model, logs and other members' calls | pnpm evals:e2e secure-keys-in-chat --local |
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.