Skip to content
| Marketplace
Sign in
Visual Studio Code>AI>BullseyeNotifyNew to Visual Studio Code?ย Get it now.
BullseyeNotify

BullseyeNotify

Karish911

|
1,937 installs
| (1) | Free
๐ŸŽฏ Your coding agent on your own machine, reachable from anywhere. BullseyeNotify runs a full interactive Claude Code, Codex or Copilot CLI and mirrors that one real session in your browser โ€” attach from your phone, type, resize, reconnect. MCP reaches the same session and streams the console's live
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

BullseyeNotify

BullseyeNotify

🎯 Your coding agent, on your machine, from anywhere. BullseyeNotify runs a full interactive Claude Code, Codex or Copilot CLI on your own computer and mirrors that one real session in your browser โ€” reach it from your phone, from ChatGPT, from claude.ai, from Telegram, Slack or email, and let its live output stream to an MCP caller. It works in your own projects, with your own files and tools, and when it finishes, needs a decision or hits trouble, it reaches you back.

Claude Code ยท Codex ยท GitHub Copilot โ€” a server on your machine, a sign-in you control, nothing hosted by anyone else.

A conversation in BullseyeNotify's web page: the question, the agent's answer drawn as Markdown with a real table, and the measured times


Summary

What you get
🤖 A real agent CLI, on your machine, in your browser One full Claude Code, Codex or Copilot CLI per session, mirrored to your phone โ€” attach, type, resize and reconnect; up to 10 message sessions at once, resumed where they stopped.
🔭 MCP sees the same session A Claude conversation runs in ONE real Claude CLI: bn MCP types each turn into it and streams that CLI's own screen, the very one the browser opens โ€” or just takes the finished reply.
🚪 Every door in ChatGPT and claude.ai (MCP), a web page, REST, Telegram, Slack, Discord, Teams, ntfy, SMS and email.
🔐 Sign-in that is yours Passkey, authenticator code, texted code or OAuth 2.1 โ€” behind a Cloudflare tunnel you switch on in one wizard.
โ“ It asks, you answer notify and ask reach your phone; ask blocks until you reply.
🌙 It respects your attention Do Not Disturb, quiet hours and idle gating decide what rings and what waits.
🛠๏ธ The server is controlled from the panel Start, Stop and Restart with a measured pid, version and heartbeat age.

1. A real agent CLI, on your machine, mirrored in your browser

BullseyeNotify runs a Claude Code, Codex or Copilot CLI on your computer and lets you reach that one real session from wherever you are.

  • One full interactive CLI per session. The โ–ถ New Agent form starts the actual claude, codex or copilot program in the project you pick, drawn in the browser through xterm.js over a node-pty worker. It is the same CLI you would run in a terminal, not a re-implementation of it.
  • The browser mirrors the CLI and adds nothing of its own. Typing, pasting, mouse and resize all reach that one CLI, and reconnecting hands you back the screen you left. Pasting a screenshot or dropping a file writes it on the machine running the CLI and sends its path in.
  • One page creates and manages it. GET / and GET /terminal both serve BN's native CLI page: the โ–ถ New Agent form is the one way to start an agent, and the page lists, attaches, reattaches and closes your CLI sessions beside the message conversations the REST, MCP, Telegram and email doors create.
  • MCP reaches the same session. A Claude conversation started over MCP runs in its own real Claude CLI, the same process the browser opens: a chat client streams that CLI's real screen as it arrives, or simply takes the turn's single reply.
  • The message doors still answer a question. Through MCP, REST, Telegram or email the agent opens a conversation, works in the project your message names (else your default project) and answers; up to 10 run at once, a process idle for 8 hours is ended, and the next message resumes the same session where it stopped. Every reply shows three measured times: end-to-end, the part queued, and the part the agent worked.

A real Claude Code CLI running on the machine, mirrored in the browser โ€” the same program, drawn through xterm.js

BN's native CLI page: the โ–ถ New Agent form with the provider, project and model, beside the conversations it manages

2. Every door opens onto the same agent

Door How you use it
ChatGPT and claude.ai Add your tunnel address as an MCP server; the agent is a set of tools (below). OAuth 2.1 with dynamic client registration, so they sign themselves in.
Web page Open / on your server โ€” from the panel's Web page button or from your phone. BN's native CLI page: open a CLI and attach to it, then read the message conversations the other doors created โ€” a sortable table and a transcript drawn as Markdown with real tables, lists, links and code.
REST /v1/* for your own scripts, with the same token.
Telegram ยท Slack ยท Discord ยท Teams ยท ntfy ยท SMS Prefix a message with ! to talk to the agent. /stop stops the turn, /new starts a fresh conversation.
Email Write to the mailbox (Gmail IMAP/SMTP); the answer comes back in the same thread.

The same conversation on a phone-width screen

Each conversation row names its own id and its opened and updated times to the millisecond, so rows that read alike are told apart. A reply is drawn as Markdown; raw HTML in it stays literal text and nothing it names runs.

3. Sign-in and reach you control

  • Four ways in: a passkey, an authenticator code, a code texted to you, or OAuth 2.1 for ChatGPT and claude.ai.
  • Public access wizard. The panel's Public access button walks you through exposing your server on your own Cloudflare tunnel โ€” you bring the tunnel, nobody hosts your agent.
  • Nothing opens by itself. The notify door is on loopback only (127.0.0.1:7475); the agent gateway (default port 7470) is token, OAuth or passkey gated.
  • The page names what served it: BN <build> ยท pid <pid> ยท started <time> under its header, so a page reloaded after an update shows the new build.

4. The server is controlled from the panel

The server is one daemon per machine. It starts at login, beats a heartbeat every 10 seconds, and survives a closed editor.

The BullseyeNotify panel: the lifecycle strip with Start, Stop and Restart above the Agent Conversations tab

  • Start, Stop and Restart sit in a strip above the panel's tabs, so they are there even when the page cannot load. It shows what was measured โ€” pid, version, and the age of the last heartbeat โ€” else Stopped or Unreachable.
  • A Stop stays stopped. No window, login or restart brings the server back until you press Start. Every press runs under one machine-wide lock, so two windows never make two servers.
  • You are told what a press costs first. Stop and Restart say how many conversations have a turn in flight and what a cut costs; a restart resumes the same session where it stopped.
  • A live server is never called stopped. A quiet heartbeat from a running process reads as running or unreachable, and refuses a second start.
  • Two tabs: Agent Conversations (BN's page inside the panel) and Settings (every channel, Do Not Disturb, quiet hours, idle and the master mute, each save read straight back).

The Settings tab: every channel and its credentials, Do Not Disturb and quiet hours, idle and the master mute

5. The agent as tools โ€” bn MCP, 13 tools

Add the gateway's /mcp to ChatGPT, claude.ai or any MCP client and the agent on your machine becomes these tools.

Tool What it does
agent_prompt Ask the agent and get its answer; continues the same agent, or new=true for a fresh one.
agent_start Start a conversation in a named project and return at once with its id.
agent_wait Read the next events of a running turn until an answer, question, failure or stop.
agent_stream Attach to the session's LIVE stream over Server-Sent Events โ€” while its CLI runs, that CLI's real screen bytes; reconnect with after=<seq> and miss nothing.
agent_send Send a follow-up or an answer to a question the agent asked.
agent_status The state, the project and the measured times of a conversation.
agent_list Every active conversation.
agent_stop Stop a running turn; the next message resumes it.
agent_open Open an empty conversation: no text, no project, nothing spent.
agent_project Set or switch a conversation's project folder between turns.
agent_projects The project folders the agent can work in.
agent_archive Move a conversation off the active list; its transcript stays.
agent_delete Delete a conversation.
agent_terminals The agent CLIs open on this machine and the CLIs New Agent can open.
agent_terminal_open New Agent: open a conversation's own CLI, or make one on a project and provider.
agent_terminal_close End a terminal's CLI process; the conversation stays.
agent_terminal_input Type raw keystrokes into a terminal's live CLI.
agent_terminal_resize Resize a terminal's screen.
agent_terminal_files Hand files to a terminal's CLI.
settings_get Everything the Settings page shows: channels, rows, values, the conversation switch.
settings_save Save one Settings row, checked against its kind and read back.
conversation_switch Read or flip the agent-conversation On/Off switch.
public_access Read the Public access wizard or press one of its steps.
bn_lifecycle BN's own state, Start, Stop and Restart, as the dashboard row runs them.

6. Your AI reaches you โ€” notify MCP, 10 tools

The notify server ships inside the extension and serves one loopback door, http://127.0.0.1:7475/mcp. You tell your AI what you want in a sentence; it sends, asks and waits. The agent never picks a channel โ€” routing is server-side.

Tool What it does
notify Send a message at low, normal or high priority.
ask Send a question and block until you answer from your phone.
poll Drain messages you sent while it was busy.
wait_for_inbox Block up to 55 s and return the moment you type something.
get_idle_seconds Seconds since your last keypress.
get_idle_config The idle-gating policy.
get_delivery_status Whether you can actually be reached, from real transport readings.
get_dnd_status Whether Do Not Disturb, the master mute or a per-client disable is holding messages.
update_instructions Persist a behavioural rule into CLAUDE.md so it survives restarts.
reply The Claude Code Channels return path.

Messages over 500 characters are split into numbered (1/N) parts and delivered in order, up to 5000.

Say it to your AI

Prompt: run the full test suite and notify me when it finishes. The notify call, the Telegram message as sent, and the result the agent gets

  • "Run the full test suite and notify me when it finishes." โ€” the agent is told outcome=delivered, failed if it reached nobody, or blocked if Do Not Disturb held it on purpose. A summary names any channel that did NOT carry it.
  • "Before you delete anything in /releases, ask me and wait." โ€” ask stops the agent until you reply.

Prompt: before you delete anything, ask me. The question arrives on Telegram, the reply goes back to the agent

  • "I am asleep. Only wake me for something really broken." โ€” with Do Not Disturb on, every message of every priority is held before any channel is tried.

Prompt: I am asleep, only wake me for something really broken. Every message is held by Do Not Disturb

  • "Can you actually reach me right now?" โ€” get_delivery_status and get_dnd_status answer from real transport checks; a revoked token reads as not carrying.

Prompt: can you actually reach me right now? get_delivery_status and get_dnd_status results

  • "Remember: always notify me when something takes more than a minute." โ€” update_instructions writes the rule into CLAUDE.md.

Prompt: remember to always notify me. update_instructions writes the rule into CLAUDE.md

Pictures 03-07 are the shipped notify daemon run for real over its MCP door against a local Telegram-API stand-in; pictures 08-11 are the shipped panel and web page over the real REST door, 09b a real CLI started through that door and mirrored in the browser. Every name, id and token is invented.

7. How delivery is decided

Three switches suppress first: the master mute kills everything including urgent messages; a per-client disable kills one agent; Do Not Disturb โ€” manual, or scheduled quiet hours per day of the week โ€” kills everything, high included.

Then idle gating: while you are at the keyboard a normal message degrades to a desktop notification only, rather than lighting up your phone. Slack is exempt so a channel log stays complete. SMS fires only on high. high bypasses idle gating only. Idle detection works on Windows, macOS and Linux.

8. A status bell that never lies

The bell in the status bar is refreshed every 10 seconds and never shows green over a channel that carries nothing: NO CHANNEL, UNCHECKED, NO REPORT, MCP OFF, DOWN, NOT VERIFIED, MUTE UNREAD, a plain bell when it can really deliver, and the mute you chose yourself. Click it to focus the panel.

The status-bar bell, and what each of its faces means

9. Channels

  • Desktop โ€” native toast, silent; optional neural text-to-speech named by desktop.ttsVoice.
  • Telegram โ€” two-way; replies land straight in the agent.
  • Slack โ€” bot token or webhook; a shared channel works as a cross-machine bus with @<name>.
  • SMS โ€” AWS End User Messaging, high only.
  • ntfy โ€” your own server or https://ntfy.sh.
  • Discord โ€” a channel webhook.
  • Teams โ€” Adaptive Card into a Workflows webhook.
  • Email โ€” Gmail IMAP/SMTP, threaded.

Every session declares a tag (host plus project). Untagged messages broadcast; @<tag> โ€ฆ goes to one agent. clientAliases names a tag and disabledClients silences one.

10. Self-wiring

On every window start the extension registers the notify server with Claude Code (~/.claude.json), GitHub Copilot Chat in agent mode (the HTTP definition for the one door, carrying the project in x-notify-project) and the workspace's .vscode/mcp.json. A notify entry that differs from ours is yours and is left alone. When BullseyeUber hosts the members, this extension stands aside so one host owns the server.

Any other client points at the same door:

{ "mcpServers": { "notify": { "type": "http", "url": "http://127.0.0.1:7475/mcp" } } }

Better together: BullseyeUber

BullseyeNotify works alone and gains the most inside BullseyeUber โ€” FleetView, BullseyeBacklog, DeepAgent, BullseyeSync and BullseyeNotify in one Bullseye Control tab, one dialog for every member, a shared safe reload.

Release notes

Version Change
1.3.265โ€“268 BN is a manager of remote CLI sessions: one full CLI per session mirrored in the browser (#3351, #3401), the agent's live output streamed to an MCP caller (#3402), copy/paste and file drop into the CLI (#3429, #3431), terminate removes a CLI conversation (#3428)
1.3.218 The listing is rewritten around the agent: new screenshots of the panel, the conversation list and the chat
1.3.216 Start, Stop and Restart the server from the panel; a Stop stays stopped; a live server is never called stopped (#2728)
1.3.215 A stopped conversation leaves the active list at the same 15-minute bound (#2738)
1.3.214 An idle conversation archives itself after 15 minutes (#2738)
1.3.203 Replies drawn as Markdown; the page names the process serving it; each row names its id and times (#2726, #2731)
1.3.202 A session opens with no prompt and no project; the project is picked and switched later (#2723)
1.3.196 Copilot agent mode is pointed at the one notify door (#2706)
1.3.185 A BN agent serves the folder it runs in, never the window it was started from (#2336)

License

MIT. Source and issues: https://github.com/menih/BullseyeNotif

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
ยฉ 2026 Microsoft