Temporary image generation instructions
Image 1 – icon / symbol: Create a detailed cartoon icon or symbolic illustration for AxiOwl article 65, "How AxiOwl Doctor Inventory Explains What Is Installed". Show an owl-themed AI message dispatcher, named agent badges, and a clear visual metaphor for this topic: `axiowl doctor inventory` should explain the local installation in one place. 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 65, "How AxiOwl Doctor Inventory Explains What Is Installed". Show a developer workstation or clean software interface where named AI agents exchange messages through AxiOwl. Include visual cues specific to this topic: `axiowl doctor inventory` should explain the local installation in one place. Style: polished SaaS website image, widescreen 16:9, believable fictional UI, no real credentials or real private data.
`axiowl doctor inventory` should explain the local installation in one place.
When AxiOwl fails, the operator needs to know what exists on the machine. Which provider apps are installed? Which CLI commands are available? Which extensions are present? Which MCP configs exist? Which AxiOwl command path is active? Which registry files are present?
The doctor inventory command is the natural place to collect that information.
The value is not only convenience. It prevents bad assumptions. A provider may be checked in the installer even though it is not installed. A stale command path may point to an old copy. A VS Code bridge may be missing even though the user expects it. A CLI may exist but not be authenticated.
Inventory should not claim success too strongly. Finding a file does not prove the provider can reply. The command should report evidence, not overstate it.
A useful inventory report can include:
– AxiOwl version and install path;
– PATH resolution;
– provider app detection;
– provider CLI detection;
– MCP config locations;
– bridge extension locations;
– registry path;
– log path;
– license status;
– known errors.
This gives support a short factual baseline before deeper investigation.
Doctor inventory also reduces token use in support workflows. Instead of pasting long unrelated logs, a worker agent can summarize or attach the inventory result first. A supervising agent can ask for focused logs only where the inventory shows a gap.
Inventory is the difference between guessing about local state and inspecting it.