Turning AI features off

Every AI feature in AddisDB has an off switch, and there is one more switch above them all. While a switch is off, AddisDB sends nothing to a model for that feature — not your schema, not your query, not a single row.

The switches are shared by the desktop app, the terminal app and the VS Code extension, so turning something off in one turns it off in all three.

Turning off all AI

1. Open Settings → AI.
2. Click Use AI features so it reads Off.

That stops every AI feature, in every project. While it is off, no project can turn AI back on.

Turning off one feature

Under the main switch, Settings → AI lists each feature with its own checkbox. Clear the ones you do not want:

• AI chat — the conversation grounded on a project’s databases.
• Generate SQL — turning a plain-English question into a query in the editor.
• Fix with AI — handing a failing query to the assistant. It works through chat, so turning chat off turns this off too.
• AI mock data — planning and generating sample rows.
• Test clone AI fix — auto-fixing statements that fail on a throwaway test clone.
• Schema diff rename check — asking whether a dropped and added column is really a rename.
• ERD views with AI — describing part of a schema and having a diagram built for it.
• AI workflow steps — workflow steps that write SQL, review a result or generate mock data, including scheduled runs.

Keeping AI out of one project

Open the project, click the gear at the top of the sidebar to open Project settings, and scroll to AI features.

• Turn off all AI in this project — stops every AI feature here and leaves your other projects alone.
• Global, On or Off beside each feature — Global follows Settings; On or Off decides for this project only. The line under each feature says what it currently resolves to, and why when it is off.

A project’s On can switch a single feature back on that is unchecked in Settings. It cannot get past Use AI features: while that is off, AI stays off in every project, whatever the project says.

What “off” looks like

• Buttons stay where they were, dimmed. Hover one and it says which switch is off — for example, “AI mock data is turned off in Settings.”
• The Chat tab keeps your earlier conversation readable, and swaps the message box for the reason, with an Open AI settings button.
• If you reach an AI feature by keyboard shortcut, a small notice says why nothing happened, with a shortcut to AI settings.
• A workflow with AI steps says so in the wizard. Pressing Run will not start it.
• A scheduled workflow with AI steps is skipped rather than failing halfway. The skip is recorded under Workflow activity with the reason, once per missed run.

If your organization has turned AI off, the message names your team instead — “Acme has turned off AI for its members.” — and there is no settings button, because it is not a switch you can change. See “Team AI policy”.

What these switches do not cover

Some features sound like AI but never call a model, so they have no switch and keep working: inline completions in the SQL editor, query plans and cost estimates, AI Privacy locks and the sensitive-column scan, and Data Map.