Temporary image generation instructions
Image 1 – icon / symbol: Create a detailed cartoon icon or symbolic illustration for AxiOwl article 70, "How AxiOwl Creates New Provider Sessions". Show an owl-themed AI message dispatcher, named agent badges, and a clear visual metaphor for this topic: AxiOwl create support lets the user start a new provider session through a provider-specific path. 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 70, "How AxiOwl Creates New Provider Sessions". Show a developer workstation or clean software interface where named AI agents exchange messages through AxiOwl. Include visual cues specific to this topic: AxiOwl create support lets the user start a new provider session through a provider-specific path. Style: polished SaaS website image, widescreen 16:9, believable fictional UI, no real credentials or real private data.
AxiOwl create support lets the user start a new provider session through a provider-specific path.
Sending to an existing target is only one workflow. Sometimes the user needs a fresh session for a new role: a review agent, an installer test agent, a documentation agent, or a provider probe. The `create` command is the interface for that.
Creation is provider-specific. A Codex session, CLI session, editor-backed chat, and other provider surface can have different creation mechanics. AxiOwl should expose a common command shape while preserving those provider differences internally.
A create request normally includes:
– provider;
– desired display name;
– initial message;
– model when applicable;
– working directory when applicable.
The result should record whether creation was accepted, what method was used, what provider session id was created, and whether a rename is recommended or needed.
Creation must also connect back to the registry. A new provider session is not useful to AxiOwl unless it becomes addressable. The registry row should store the provider surface, provider session id, display name, and evidence source.
Create support is important for repeatable workflows. Instead of telling a human to manually open a new chat and name it, AxiOwl can create a target that matches the role needed for the task.
The quality bar is the same as send support. Creation is not fully proven until the new session can receive and, where supported, reply through AxiOwl.
Creating sessions is how AxiOwl moves from messaging existing agents to constructing workflows.