opencode runs in a crystl shard with its own model selection, activity
visibility, and real approval cards for its tool calls, delivered through a
plugin crystl injects into the session. Crystl treats its compatibility as
partial because the card only opens on opencode’s own permission event, and a
missed answer falls back to opencode’s native prompt.
The profile describes what crystl has tested; it never supplies a command,
hook script, or launch setting. Those remain local to the Crystl installation.