Skip to content
WeType

Compatibility

Will it run on your Mac, and in your apps?

The short version: any Apple Silicon Mac on macOS 14 or later, in any app with a normal text field. The longer version, including what doesn't work, is below.

Requirements

Mac

Apple Silicon: M1, M2, M3 or M4

The on-device model is built for Apple Silicon.

Intel Mac

Not supported

There is no universal build today, and the update feed requires arm64.

macOS

macOS 14 Sonoma (14.0) or later

Tested on Sonoma and Sequoia. Built on modern accessibility APIs.

Disk space

7.9 MB for the app, plus 379 MB to 4.5 GB for a model

The recommended Qwen 2.5 3B (base) is about 1.9 GB.

Internet

Only to download a model and check for updates

Predictions themselves never need a connection.

Permissions

Accessibility and Input Monitoring

Screen Recording is optional and off by default.

Apps

Anywhere macOS exposes a text field.

WeType reads the focused field through the system accessibility layer rather than through per-app integrations, so it appears in apps nobody had to add support for.

Mail & messaging

  • Apple Mail
  • Gmail on the web
  • Outlook
  • Slack
  • Messages
  • Discord

The thread you are replying to shapes the suggestion.

Notes & documents

  • Notes
  • Notion
  • Obsidian
  • Bear
  • Craft
  • Google Docs
  • TextEdit

Long-form writing, where it saves the most.

Browsers

  • Safari
  • Chrome
  • Arc
  • Firefox
  • Edge
  • Brave

Text areas and comment boxes, Chromium quirks handled.

Code & terminal

  • VS Code
  • Xcode
  • Cursor
  • JetBrains IDEs
  • Terminal
  • iTerm2

Commit messages, docstrings and READMEs. Pair it with a code model.

Where it works less well

Stated here rather than discovered later.

  • Canvas-rendered text

    Apps that paint their own text rather than using a real text field, such as some design tools, terminals inside web apps and games, expose nothing for WeType to read. There is an optional screen-reading mode that uses OCR for these, off by default and available only on the larger models.

  • Chromium and Electron apps

    These expose their text fields only when an accessibility flag is set, which WeType sets while it is running and restores when you switch away. Positioning inside them is handled by a dedicated path, and it is the area most actively worked on.

  • Password fields

    Deliberately excluded, along with anything that looks like a credential and any site on the banking, payment and health blocklist. This is a feature, not a gap.

  • Mid-line editing

    Suggestions only appear with the cursor at the end of a line. Inline ghost text draws forward from the cursor, so mid-line it would paint over the rest of your sentence.