Support

Narrow down errors without skipping safeguards.

These are safe, local checks. They never recommend bypassing Gatekeeper or macOS privacy protections wholesale.

The panel does not appear

Check that AYVI runs in the menu bar and that Gatekeeper did not block it. A menu bar app does not necessarily show a Dock window. Without Accessibility access it may show the permission explanation instead of the normal help.

The global shortcut does nothing

The default is ⌥ Space; check the shortcut in the AYVI settings and look for conflicts with other software. Test with harmless selected text after a change.

Accessibility access is supposedly off

Open System Settings → Privacy & Security → Accessibility and check that the current /Applications/AYVI.app is enabled. If the app keeps asking after a build, remove only the outdated AYVI entry and add the current bundle again, then restart AYVI. See install step 4.

Selection is not detected, or Chrome/Electron reports nothing

Accessibility support depends on the app, the focused element and the kind of text. Try a simple text app first. Some Chromium/Electron views expose the selection or range incompletely. In such apps the Services menu or the explicitly confirmed clipboard path can help; see compatibility.

Replacing does not work

AYVI aborts when the app, the focused element, the text/fingerprint or the range no longer match. That is a safeguard: the result stays copyable; capture the selection again. Do not test on important documents first.

“Explain with AYVI” is missing from the Services menu

The entry appears only for selected text and only after macOS has registered the installed app. Start /Applications/AYVI.app once, then run /System/Library/CoreServices/pbs -update or log out and back in. Check that the entry is enabled under System Settings → Keyboard → Keyboard Shortcuts → Services. Text from the Services menu is read-only.

Lens markers are missing or not next to the code

AYVI shows them only with a validated selection and current line bounds. Otherwise use the “Line explanations” list in the panel, which works without markers and with the keyboard and VoiceOver.

Where is “Check compilation” for code?

Enable it under Settings → General (default: off). The button appears only below finished answers with a Java, Swift or Python code block. If AYVI reports “compiler not found”: install the Command Line Tools with xcode-select --install for Swift and Python, a JDK for Java. AYVI installs nothing automatically and still cannot run code.

Voice input does not start

Enable it under Settings → General first. On first use an explanation appears before macOS asks for microphone and speech recognition access. Hold the shortcut for at least 0.4 seconds; on-device speech must be available for the chosen language, there is no server fallback.

Ollama is not reachable

Check that Ollama runs, base URL and port are right and the model is installed. The connection test under Settings → AI can help.

A cloud provider reports 401 or a rate limit

401 usually means a wrong or missing key, the wrong account or a model that is not enabled. Rate limits are the provider’s; wait or check your quota. Never put API keys into support text or a selection.

The app does not open after the build, or Gatekeeper warns

Check that the build finished and /Applications/AYVI.app exists. This development bundle is locally or ad-hoc signed and not notarized. We do not recommend disabling Gatekeeper or removing quarantine attributes blindly.

Delete history or remove an API key

Use the history view and its delete functions; storage can be switched off under Privacy. Provider keys are managed under Settings → AI.