Temporary image generation instructions
Image 1 – icon / symbol: Create a detailed cartoon icon or symbolic illustration for AxiOwl article 94, "How AxiOwl Discovers and Sends to OpenCode CLI Sessions". Show an owl-themed AI message dispatcher, named agent badges, and a clear visual metaphor for this topic: OpenCode CLI support is a command-line provider surface. Style: modern SaaS cartoon, bold shapes, high contrast, polished but friendly, simple or transparent background, no readable text.
Image 2 – article image / screenshot: Create a blog hero image or product-style screenshot for AxiOwl article 94, "How AxiOwl Discovers and Sends to OpenCode CLI Sessions". Show a developer workstation or clean software interface where named AI agents exchange messages through AxiOwl. Include visual cues specific to this topic: OpenCode CLI support is a command-line provider surface. Style: polished SaaS website image, widescreen 16:9, believable fictional UI, no real credentials or real private data.
OpenCode CLI support is a command-line provider surface.
That means AxiOwl should treat it as its own integration path, with its own discovery, MCP configuration, delivery method, and test status. It should not be grouped with editor providers or assumed to behave like a desktop app.
Discovery for OpenCode CLI should find sessions that can be targeted and should store them in the registry with a provider surface that clearly says OpenCode CLI. The row should contain the session identity, display name where available, source, and sendable state.
Delivery should use the OpenCode command-line path appropriate for the session. AxiOwl should pass the final visible body to the CLI provider in a way that preserves content and lets the provider respond through the configured MCP path.
The key requirement is metadata. Historical reachability is useful, but final support should require provider-owned identity. A reply should not merely say "OpenCode replied." It should be tied to the specific CLI session that answered.
Testing should be response-backed. AxiOwl should send a known message to an OpenCode CLI target and require a known reply marker through AxiOwl. The test should record run id, receipt id, provider session id, and any error.
OpenCode CLI is a good example of why provider surfaces matter. It may be easier than patching an editor, but it still has auth, config, session identity, and MCP requirements.
Support is real when AxiOwl can discover the CLI session, send to it, receive a reply, and identify the sender.