Glintype

Fix the common
setup and typing issues.

Glintype sits between macOS permissions, the focused app, and a local model. Most issues are permission, app compatibility, or model readiness problems rather than account problems.

No suggestions appear

  • Confirm Glintype is enabled globally from the menu bar.
  • Grant Accessibility and Input Monitoring in macOS System Settings.
  • Check that the current app is not disabled in App Profiles.
  • Type at least a few characters; Glintype avoids generating from empty fields.
  • If using a local model, confirm the runtime status says ready.

Tab does not accept

  • Tab is only captured when a ready suggestion is active.
  • If text is selected, Glintype passes Tab back to the app.
  • Secure fields and terminal apps are intentionally blocked.
  • Try toggling Glintype off and on after changing Input Monitoring permission.

Ghost text appears in the wrong place

  • Move the caret and type one more character so macOS publishes fresh Accessibility geometry.
  • Disable screen-aware suggestions and retest the same field.
  • Rich web editors can expose stale caret rectangles; add an app profile with shorter suggestions.
  • Generate a debug report and include the app name, macOS version, and whether the field is browser-based.

Suggestions feel too slow

  • Use the chip-recommended model in AI Models.
  • Choose a shorter suggestion length.
  • Turn off screen-aware suggestions if OCR is not needed.
  • If Automatic Low Power Mode is active, disable it only when plugged in and testing performance.

Clipboard or screen context affects wording

  • Clipboard context is optional and can be disabled instantly.
  • Screen-aware suggestions require Screen Recording and should be used only where visual context helps.
  • Clear app-specific instructions if one app starts steering suggestions too strongly.
  • Use local dictionary entries for deterministic replacements instead of relying on context.

What to send support

  • Use Generate Debug Report in Settings.
  • Include the target app and whether it is a native editor, browser editor, or Electron app.
  • Mention the selected engine and local model.
  • Do not send screenshots or private text unless support specifically asks and you are comfortable sharing them.