Bridge/notification channel between a Claude Code session and Claude Desktop
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
I use Claude Code and Claude Desktop together daily on the same project (Rezycle.me, an AI resume-optimization tool). Both work on the same codebase, on the same machine, but they can't signal each other at all.
Claude Code runs an autonomous background loop that checks analytics, email, and code drift for me. Claude Desktop (Cowork) separately runs its own scheduled tasks on the same project files. When one side finds something the other should know about, there's no way to pass that along — I have to manually relay it myself by copy-pasting between the two.
Proposed Solution
A lightweight, official notification channel between a Claude Code session and a Claude Desktop project working on the same local files -- even something minimal like "a scheduled task in Desktop can flag Code (or vice versa) that there's something new to check" would remove the need for the manual workaround below.
Alternative Solutions
As a workaround, I built a simple async file-based mailbox: two text files that each side appends timestamped notes to. Claude Code checks one of them on every tick of its own background loop; Claude Desktop would need one of its scheduled tasks configured to check the other. It works, but it's manual to wire up and easy to forget to maintain -- not something most users would set up on their own.
Priority
Low - Nice to have
Feature Category
Other
Use Case Example
Example scenario:
- I'm working on a Next.js project with Claude Code (VS Code) and, separately, Claude Desktop open on the same project folder for planning/personal-context tasks.
- Claude Code's background loop finds something Desktop should know about (e.g. a security fix just shipped, or a decision that changes how the project should be worked on).
- Right now, the only way to pass that along is for me to manually copy it from one chat and paste it into the other.
- With a lightweight official channel, Code could flag Desktop (or vice versa) automatically, so I don't have to be the relay between two tools working on the same project.
Additional Context
_No response_