App Compatibility

Cotypist works with most Mac apps out of the box. Here's what to expect in your favorite apps.

Table of Contents

Compatibility Overview

Most apps work without any configuration. Some need a small setup step, and a few are not yet supported.

Your favorite app is not listed here?
It likely works anyway — Cotypist supports most Mac apps out of the box.

If you find an app that doesn't work, please let us know!

Browsers

Application Status
SafariWorks
ChromeWorks
BraveWorks
EdgeWorks
ArcSetup needed
DiaSetup needed
FirefoxMirror window only
Zen BrowserMirror window only

Email

Application Status
Apple MailWorks
Gmail (in browser)Works
OutlookWorks
MimestreamWorks
ThunderbirdNot supported

Writing & Documents

Application Status
Microsoft WordWorks
Google DocsSetup needed
TextEditWorks
PagesNot supported
ScrivenerNot supported

Notes & Knowledge

Application Status
Apple NotesWorks
NotionWorks
ObsidianWorks
OneNoteNot supported

Messaging

Application Status
MessagesWorks
TeamsWorks
SlackPartial
WhatsAppWorks

Code Editors

Application Status
VS CodeSidebar chats only
CursorSidebar chats only
WindsurfSidebar chats only
BBEditNot supported

Terminals

Application Status
Terminal.appWorks
iTermWorks
GhosttyNot supported
cmuxNot supported
WarpNot supported

Why Doesn't Cotypist Work in Some Apps?

Cotypist needs apps to make their text fields accessible to other software on your Mac. Most apps do this automatically, but some use custom text rendering that prevents Cotypist from reading or inserting text.

Apps marked as "Not supported" don't provide the access Cotypist needs. We cannot work around this on our end — the app developer would need to make changes on their side.

Google Docs

Cotypist relies on Google Docs' Accessibility mode to read your document and show suggestions. Without it, Google Docs does not expose enough information for Cotypist to work.

When you start editing a Google Doc, Cotypist should automatically show a floating button offering to enable Accessibility for you. If that button does not appear, you can enable it manually:

  1. In Google Docs, go to the Tools menu and select Accessibility.
  2. Check "Turn on screen reader support".
  3. Also check "Turn on braille support".
  4. Click OK.

After enabling this, Cotypist should start showing suggestions as you type. If it still doesn't work, try restarting your browser or your Mac.

We recommend disabling Smart Compose (Google Docs' built-in autocomplete) to avoid it interfering with Cotypist's suggestions. You can find this option under Tools > Preferences.
Note: Cotypist currently works in Google Docs only. Google Sheets and Google Slides are not supported.

Arc & Dia Browsers

In some browsers (including Arc, Dia, Firefox, and Zen Browser), Cotypist can only show its suggestions in a "mirror" window above the text field rather than inline with the text itself.

However, it is possible to enable inline text suggestions in Arc and Dia (but not Firefox or Zen Browser). There are two ways to do this:

Option 1: Enable Text Metrics in the accessibility tab

  1. Open chrome://accessibility in Arc or Dia.
  2. Check the "Text Metrics" option.
  3. Keep that tab open in the background while using Cotypist. Pinning the tab is recommended — it should prevent Arc/Dia from unloading it automatically.
Important: With this option, inline suggestions only work while the chrome://accessibility tab remains open. You can leave it open in the background.

The Text Metrics setting may not persist after restarting the browser or switching between Spaces — you may need to re-enable it by revisiting that tab. This is a limitation of Arc/Dia, not Cotypist. If this becomes annoying, see Option 2 below for a more persistent (but more technical) workaround.

If you use Arc or Dia, consider asking The Browser Company to provide a built-in way for Accessibility apps to force-enable Text Metrics, which would remove the need for this workaround entirely.

Option 2: Launch the browser with an accessibility flag

If you're comfortable using the Terminal, you can avoid the persistence issues above by launching the browser with the --force-renderer-accessibility=complete flag instead. Quit the browser first, then run:

open -a 'Arc' --args --force-renderer-accessibility=complete

Replace Arc with Dia if you use Dia. Once launched this way, Cotypist's inline suggestions work for the entire session, including when switching between Spaces — no extra tab required. To make this convenient, save the command as a small shell script or shortcut and use it instead of the regular Dock icon.

Code Editors

Cotypist works in the sidebar chat panels of popular code editors — the text fields where you interact with AI coding assistants like Claude Code, Codex, Cursor Agent, or GitHub Copilot.

Cotypist does not provide completions in the main code editor area, as code editors have their own specialized completion systems (IntelliSense, Copilot, etc.) that are better suited for code.

Code editors are disabled in Cotypist by default. To enable sidebar chat completions, add the editor in Cotypist's settings or via the Cotypist icon in your menu bar.

Terminals

Cotypist works in Terminal.app and iTerm, making it particularly useful when interacting with AI coding agents like Claude Code, Codex, or similar tools where you type natural language in a terminal.

Cotypist automatically activates in these terminal apps when it detects you are typing in an AI agent's prompt. For regular command-line usage, completions are not shown by default (to avoid interfering with shell autocompletion). If you want completions while typing regular commands, you can use the force-activate completions shortcut (see Shortcuts) to temporarily enable them.

Ghostty & cmux

Ghostty does not yet provide the support that Cotypist needs to show suggestions. Since cmux is based on Ghostty, it has the same limitation.

We've submitted improvements to Ghostty — you can follow the progress in ghostty-org/ghostty#9932. Once these changes are merged and released, Cotypist will be able to support Ghostty and cmux.

In the meantime, Terminal.app and iTerm are the recommended terminals for use with Cotypist.

Warp

Warp doesn't provide the access Cotypist needs to read or insert text. Warp support is unlikely in the near future.