Temporary image generation instructions
Image 1 – icon / symbol: Create a detailed cartoon icon or symbolic illustration for AxiOwl article 82, "How AxiOwl Leaves Unchecked Provider Integrations Untouched". Show an owl-themed AI message dispatcher, named agent badges, and a clear visual metaphor for this topic: Unchecked provider integrations should be left untouched. 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 82, "How AxiOwl Leaves Unchecked Provider Integrations Untouched". Show a developer workstation or clean software interface where named AI agents exchange messages through AxiOwl. Include visual cues specific to this topic: Unchecked provider integrations should be left untouched. Style: polished SaaS website image, widescreen 16:9, believable fictional UI, no real credentials or real private data.
Unchecked provider integrations should be left untouched.
This rule sounds obvious, but it is one of the most important installer rules in AxiOwl. If a user unchecks Codex, the installer should not install, repair, remove, or restart Codex integration as part of another provider's setup. If a user unchecks Cursor, the installer should not patch Cursor. If VS Code is unchecked, the installer should not close VS Code merely because it was discovered.
Granular installer UI only matters when behavior is granular too.
The rule applies to install, repair, reinstall, and cleanup. Robust uninstall logic should remove what belongs to selected or installed AxiOwl features, but it should not damage provider integrations the user did not select.
This is a hard balance. AxiOwl also needs to be robust and adaptive. It may need to clean stale files, repair PATH, reinstall extensions, and remove old product-name leftovers. But that work still needs provider boundaries.
The provider contract model helps enforce the boundary. Each provider feature has known feature ids, custom actions, payloads, and log scopes. The installer can validate that selected providers map to selected feature work.
Leaving unchecked providers untouched builds user trust. It also prevents regressions where fixing one provider breaks another.
The product standard should be clear: aggressive inside the selected scope, careful outside it.
That is how AxiOwl can be robust without being destructive.