Skip to content

Troubleshooting & FAQ

Each section below is a symptom, with the cause in one sentence and the steps that fix it. Quick answers to non-problem questions are at the end of the page.

Four different causes can suppress the tooltip, so check them in order:

  1. If Accessibility permission is missing, Remarc cannot read your selection. Grant it in System Settings > Privacy & Security > Accessibility; see permissions.
  2. If the menu bar icon is dimmed, Remarc is paused. Right-click the icon and choose Resume.
  3. If the app you are selecting in is listed under Settings > Excluded Apps, remove it there.
  4. If Detection mode is set to “Hotkey Only”, the tooltip never appears on its own. Workaround: press Ctrl+Option+C after selecting text. Resolution: switch back to “Auto-detect + Hotkey” in Settings > General.

Dictation, Voice Input, Crit Mode, and the Voice settings tab require macOS 26 (Tahoe) or later; on older versions the controls are hidden, not broken. Everything else works on macOS 14 and up.

macOS sometimes drops Remarc’s microphone grant, so recordings produce nothing without any error.

  1. Re-grant access in System Settings > Privacy & Security > Microphone.

  2. If recordings are still silent, reset the permission in Terminal:

    tccutil reset Microphone com.metepolat.Remarc
  3. Relaunch Remarc and grant microphone access when prompted.

The extension connects only in tabs loaded after it was installed, and only when it can reach the app on its port.

  1. Reload your open tabs.
  2. If the tabs are fresh and it still will not connect, open Settings > Chrome Extension, which shows the connection status and port 9274. If another app holds the port, quit that app and click the Retry button.
  3. Check the pause toggle in the extension’s popup.

A harness can list the plugin as installed even when the MCP server fails to start, so an installed plugin is not proof of a working one.

  1. Reinstall from Settings > MCP Integrations (the Codex row offers Repair).
  2. Ask the agent to call remarc_list_sessions. If that call succeeds, the integration is healthy.

Screenshot comments require the Screen Recording permission. Grant it in System Settings > Privacy & Security > Screen & System Audio Recording (called Screen Recording on older macOS), then try again. If macOS offers Quit & Reopen after you change the setting, accept it.

If capture opens but saving fails, check Settings > General > Screenshots > Storage folder. A custom folder must remain available and writable. Reconnect its drive, restore write access, or choose another folder and try again. Remarc does not silently save to the default folder when the selected location fails.

Some agents cannot read ~/Library or cannot access files on your Mac. Choose an accessible folder under Settings > General > Screenshots > Storage folder for new screenshots and pasted image attachments. A local folder choice cannot give a remote agent access to your Mac’s filesystem.

Existing images stay in their original folders and remain editable there; changing the setting does not migrate them. Keep those folders available. The preview panel’s Save As action exports a separate copy without changing the path referenced by the comment.

Where is my data stored? Sessions and comments live in ~/Library/Application Support/Remarc/comments.json. Screenshots and pasted image attachments use its images/ folder by default, or a custom folder selected in Settings. See data, privacy & updates.

Is anything sent to a server? Remarc stores comments, screenshots, and audio on your Mac. Data can leave through agents and webhooks you explicitly use; other network activity is limited to update checks, transcription model downloads, and agent plugin installs.

How many sessions can I have? Up to 8 active sessions, plus the permanent Inbox that catches unfiled comments. See Sessions & the Inbox.

Does Remarc work with my browser? Text selection commenting works in any Mac app, including any browser. The Chrome extension’s element and region capture works in Chromium browsers: Chrome, Arc, Brave, Edge, Vivaldi, and Opera.

Does Remarc work with PopClip? Yes - the Remarc PopClip extension adds a Remarc button to PopClip’s action bar, as an alternative to the tooltip and hotkey.

  1. If the Cursor integration is enabled, turn it off in Settings > MCP Integrations; this removes the files Remarc wrote to ~/.cursor. If you skip this, remove the remarc entry from ~/.cursor/mcp.json and delete ~/.cursor/skills/remarc/ by hand.
  2. If you installed the Claude Code or Codex plugins, uninstall them from those tools (for example /plugin in Claude Code).
  3. Quit Remarc, delete the app, and delete ~/Library/Application Support/Remarc/. If you used custom screenshot folders, remove Remarc’s images and annotation sidecars from those folders too when you want to remove all captured data.

Remarc writes no debug log by default. To capture one for a bug report, enable debug logging, relaunch Remarc, reproduce the problem, and include the tail of ~/Library/Logs/Remarc/remarc_debug.log when you open a GitHub issue. Scrub anything you consider private first, then turn logging back off. Report security problems privately as described in the security policy.