Native macOS·Local only·8 agents
Your coding agents, one glance away.
Nimcue is a small panel at the top of your Mac screen. It opens when Claude Code, Codex, Cursor or another agent finishes or needs you, and lets you answer right there, without hunting for the right window.
Free preview · ad-hoc signed preview, not notarized
The panel at the top of this page is the real interface, running as a live demo. Click an agent in the Dock, or use the buttons to send events.
Send a demo event
Every card is a clearly marked sample. Nothing here contacts an agent, and nothing leaves your browser.
What it does
Everything an agent needs from you, in one small panel.
Nimcue listens to the hooks your agents already emit and turns them into cards you can act on. The agent keeps running in its editor or terminal; you keep working in yours.
Anchored at the top of your screen
A compact strip that fits the content. Short lists use less space; long ones scroll inside a capped height. It never steals focus from your editor.
Answer questions right there
Choices, multiple selections or free text. The answer returns through the exact originating hook or MCP call, into the same conversation.
Approve or decline tool calls
Permission cards show the entire tool input and the workspace before you choose Approve once or Decline. Nothing is approved automatically.
Send the next task from the panel
Completion cards for Claude Code, Codex and Cursor carry a composer. Your follow-up continues the same conversation, within a 110 second window.
Native glass, native motion
macOS backdrop blur, translucent cards, a soft notification halo that breathes for six seconds. Reduce Motion and Reduce Transparency are respected.
Local only. No accounts, no cloud.
Built with SwiftUI and AppKit, with no third-party dependencies or service. Event history stays in your Library folder for seven days.
Install
Three steps. No account, no API key.
Requires macOS 13 Ventura or later on Apple silicon (arm64).
- 1
Download and move to Applications
Unzip the archive and drag Nimcue.app into Applications before connecting any agent. The first launch may need a Gatekeeper confirmation because this preview is ad-hoc signed.
- 2
Connect your agents
Press Control–Option–N, open Settings and choose Connect next to each tool you use. Existing hooks are preserved and backed up. Codex asks you to review and trust the new hooks with /hooks.
- 3
Run a small task
Restart your agent sessions and give one a short job. “Last event” in Settings confirms a received event; “Installed” alone means the configuration was written.
- File
- Nimcue-0.8.1-macOS-arm64.zip
- Size
- 2.5 MB
- Requires
- macOS 13 Ventura or later
- Signing
- Ad-hoc signed preview, not notarized
Blocked by Gatekeeper? Follow Apple’s instructions only if you trust the sender. The archive includes START-HERE.txt and a capability reference.
Already running Nimcue or AgentNotch in ~/Applications? Upgrade in place, keeping settings and editor connections:
python3 upgrade.py
Supported agents
Eight agents. Three of them can be answered from the panel.
Claude Code, Codex and Cursor Agent support replies and follow-ups. The others deliver notifications, so you still know the moment they finish or need you.
| Agent | Events | Replies in the panel | Activation |
|---|---|---|---|
Claude Code | Working, response ready, questions, permissions, errors | Questions, permissions, timed follow-ups | Restart sessions |
Codex | Working, response ready, permissions; questions where emitted | Permissions, MCP question answers, same-thread queued follow-ups | Trust /hooks; connect question replies; reload editor |
Cursor Agent | Working, final response, errors, pending questions with choices | MCP ask_user questions: choices and free text; timed follow-ups | Enable the Nimcue MCP server; hooks reload automatically |
GitHub Copilot | Working, response ready, errors, permission/elicitation notifications | Notifications only | Restart CLI / VS Code; local harness needs hooks enabled |
Gemini CLI | Working, response ready, permission notifications | Notifications only | Restart CLI; hooks must be enabled |
Windsurf / Cascade | Working and full response ready | Notifications only | Restart editor; Cascade only |
OpenCode | Working/retrying, response ready, errors, permission requests | Notifications only | Restart to load the plugin |
Cline | Task lifecycle and ask_followup_question events | Notifications only | Enable Hooks in Cline settings |
These are local integrations. The newer adapters are validated against documented payloads and isolated process tests rather than live end-to-end sessions in every product and version. Native editor questionnaires and permissions stay in the editor; the panel shows them read-only.
Questions
Honest answers about scope and limits.
Does Nimcue send anything to a server?
No. It reads hook events your agents emit on this Mac and writes answers back to the same local process. There are no accounts, API keys, analytics or cloud components. History stays in ~/Library/Application Support and is kept for seven days.
Why is the download not notarized?
This is a preview build, ad-hoc signed on the developer’s machine. macOS may ask you to confirm the first launch. Only follow Apple’s instructions for opening it if you trust where you got the archive.
How does a follow-up reach the same conversation?
For Claude Code and Cursor, Nimcue holds the completion hook open for up to 110 seconds and returns your message to that hook. For Codex it queues a turn on the exact thread UUID through the installed CLI. It never starts a separate session or guesses a “most recent” chat.
Will it change my agent’s approval or trust settings?
Never. Connecting adds hooks or an MCP server entry, preserves everything else in those files and saves a backup. Codex still requires you to review and trust the new hooks yourself.
Which Macs are supported?
macOS 13 Ventura or later. The packaged build is for Apple silicon. Intel Macs can build from source with Swift 5.9 and the Xcode command line tools.
What about the Spotify mini player?
It is optional and uses the Spotify desktop app’s local scripting interface, so macOS asks once for Automation permission. No web login or API key. Turn it off in Settings → Music.