Temporary image generation instructions
Image 1 – icon / symbol: Create a detailed cartoon icon or symbolic illustration for AxiOwl article 95, "How AxiOwl Supports Antigravity Agent and CLI Surfaces Separately". Show an owl-themed AI message dispatcher, named agent badges, and a clear visual metaphor for this topic: Antigravity agent surfaces and Antigravity CLI surfaces should be treated separately. 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 95, "How AxiOwl Supports Antigravity Agent and CLI Surfaces Separately". Show a developer workstation or clean software interface where named AI agents exchange messages through AxiOwl. Include visual cues specific to this topic: Antigravity agent surfaces and Antigravity CLI surfaces should be treated separately. Style: polished SaaS website image, widescreen 16:9, believable fictional UI, no real credentials or real private data.
Antigravity agent surfaces and Antigravity CLI surfaces should be treated separately.
The brand may be the same, but the integration mechanics can differ. An agent window can require one delivery model. A CLI session can require command-line discovery, MCP config, and metadata behavior. AxiOwl should not let success in one surface automatically mark the other as supported.
For agent-window support, AxiOwl may need provider-specific delivery and reply handling. For CLI support, it may need executable discovery, session discovery, prompt delivery, auth awareness, and MCP metadata.
The registry should preserve the difference. A target should not merely be "Antigravity." It should identify whether it is an agent surface or CLI surface. That keeps installer behavior, testing, and support clear.
This is also useful for users. Someone working in the Antigravity agent surface wants to know whether that surface can receive and reply. Someone using an Antigravity CLI wants to know whether the CLI surface works. Those are different expectations.
Testing should use separate rows in the provider matrix:
– Antigravity agents;
– Antigravity CLI.
Each should have its own send test, reply marker, run id, and known risks.
This separation prevents one of the most common documentation mistakes: declaring a brand supported when only one surface has proof.
AxiOwl's provider-surface model exists precisely to avoid that mistake.