macOS
Corvid on macOS is in beta. It runs on Apple Silicon and Intel Macs.
Tested status#
- Automated tests pass on macOS.
- One tester ran
npm run setupon a real Mac. Build, install and first launch worked. - Nobody has tried anything after the first launch on a real Mac yet. That includes updates and rollback.
To help test, follow the tester checklist in TESTING-PLATFORMS.md and report what you see.
What is different on macOS#
| Feature | On macOS |
|---|---|
| Shortcuts | Cmd in place of Ctrl. Tooltips show ⌘. The terminal keys stay Ctrl. |
| Show or hide Corvid from any app | Cmd+Shift+Space |
| Tray | The menu bar. Closing the window keeps Corvid running. Click the Dock icon to show it again. |
| Start at login | Open at login in Settings → Window and layout. It adds Corvid to Login Items. |
| Resume a session in a terminal window | Terminal |
| Open in Visual Studio Code (VS Code) | code on your PATH, or else VS Code by its app id |
| Side terminal shells | Your login shell first, then the other installed shells |
| Saved passwords and tokens | The Keychain. It can ask you once. |
Voice dictation does not work on macOS yet. The microphone button is greyed out.
Where things are#
| What | Where |
|---|---|
| The app | ~/Applications/Corvid.app |
| Previous builds, for rollback | ~/Library/Application Support/Corvid/previous-builds |
| Your data | ~/Library/Application Support/Corvid |
Claude Code on macOS#
Corvid looks for claude in these places and uses the newest version it finds:
~/.local/bin(the native installer)~/.claude/local- The VS Code extension
- Homebrew's folders:
/opt/homebrew/binand/usr/local/bin - Your
PATH
If the installed app does not start#
- Run
npm run setup -- --no-launchin your Corvid folder. It builds Corvid but does not install it. - Run
npm start. Corvid runs from the folder. - Report what
npm run deployprinted. See the tester checklist above.