Atomic capability · interfaces

Custom instructionsProduct capability

Persist project or user instruction files.

Custom instructions: 1 supported, 0 partial, 0 unsupported, 30 unreviewed across 31 cataloged products.

Markdown · JSON

Current evidence by product

Can my agent use Custom instructions?

Read across for the answer. 1 of 31 current product columns have reviewed evidence; unreviewed does not mean unsupported.

  • Supported1
  • Partial0
  • Unsupported0
  • Unknown30
  • Not applicable0

Web

9 products

Desktop

13 products

CLI

9 products

Unknown means no public evidence has been reviewed for that product and capability. It does not mean unsupported.

How statuses are assigned

Definition and scope

What this capability means

Persist project or user instruction files. OpenWork’s sourced cell covers its server-owned OpenCode workspace configuration; it does not claim that every instruction format or precedence rule is unique to OpenWork.

The matrix below lists published web, desktop, and CLI surfaces. Unreviewed cells remain unknown until a dated note and public source support a more specific status.

Use the Markdown and JSON twins if you are an agent reading this site.

Traceable compatibility

Assertion ledger

Documentation evidence only. No runtime conformance test is implied.

OpenWork Desktopdesktop · current
Supported
Target
current OpenWork architecture documentation · dated-documentation
Environment
local-default
Observed
2026-08-28
  • runtimeprecedence and file discovery are supplied by the embedded OpenCode runtime
Evidence
  1. 1. Evidence checked 2026-08-28: OpenWork's server owns workspace .opencode configuration, including skills, agents, commands, and other persistent OpenCode instruction primitives.