[horizonbymuneeb]

What is this about?

Fix the "Invalid schema for function 'computer_run': Pointer '/$defs/__schema0' does not exist" error that blocks every chat on 0.18.60+.

What problem does it solve?

computer_run's input argument is declared z.json(). Zod 4 serializes that to {"$ref":"#/$defs/__schema0"} with the definition in a top-level $defs. The engine hands the tool schema to the model provider, the $defs does not travel with the $ref, and providers reject the request — every message carries the computer-use tools, so every message fails.

What was the situation before?

Every chat, old or new, fails with Invalid schema for function 'computer_run': Pointer '/$defs/__schema0' does not exist (request_id: ...) after upgrading from 0.18.58.

How is this implemented?

• apps/server/src/opencode-plugins/openwork-computer-use.ts: new jsonValue union (string | number | boolean | null | array | object) that validates the same JSON values as z.json() but serializes to plain nested JSON Schema; both computer_run uses of z.json() now use it.
• apps/server/test/computer-use-tools.vitest.test.ts: regression test asserting no computer tool schema serializes $ref.

What else changed?

none

Release note

Computer use no longer breaks every chat with a provider schema error.

Evidence

• Before → after, on the real plugin file: z.toJSONSchema of computer_run args contains "$ref":"#/$defs/__schema0" → no $ref, input is an anyOf of the six JSON value types.
• apps/server/test/computer-use-tools.vitest.test.ts: 3 existing + 1 new test pass.
• Run with npx vitest run on the two changed files; full repo typecheck/build left to CI (heavy monorepo install).

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

4 Skipped Deployments

Project	Deployment	Actions	Updated
openwork-app	Skipped		Oct 25, 2026 9:48am UTC
openwork-den	Skipped		Oct 25, 2026 9:48am UTC
openwork-diagnostics	Skipped		Oct 25, 2026 9:48am UTC
openwork-landing	Skipped		Oct 25, 2026 9:48am UTC

[github-actions]

Contributor screen: passed

Commit 799d3795a9 · run

No hidden characters, dependency, database or obfuscation concerns.

Nothing else runs yet. A maintainer reviews the changes then comments /test to start the AI screen, the tests and the Warden security review.

[horizonbymuneeb]

Closing this one — #6491 landed the same fix on dev, and it takes a simpler route than this branch did (z.unknown() for the model-facing argument while execute still validates it as JSON), so there is nothing left here worth carrying.

For the record, this branch reached the same diagnosis independently: z.json() serializes to {"$ref":"#/$defs/__schema0"}, and the engine renames the root $defs to definitions without rewriting the pointer, so strict providers reject the dangling $ref. This branch resolved it by spelling out the JSON value as an explicit union; #6491's z.unknown() plus the parse in execute is the cleaner answer and I would not want two competing versions of it in the tree.

Thanks for the review time.