Join the discussion
Write your take first — we'll ask for email only when you're ready to publish.
- Hacker News
- I love how like most of the comments are some form of "oh I already built this for myself" what a fascinating time -- so much personal, almost disposable software being made!by tengada1
- Something related that I've thought of for a long time. Browsers have had the BroadcastChannel API for almost a decade now, and yet sites like HN and Reddit don't use it to synchronize state between multiple open tabs.
- I just started exploring this stuff with herdr, it's pretty cool! But I prefer my multiplexer having this functionality built in, as it lets me also have the agent organize my panes and tabs automatically based on what it is working onby borzi
- I made my own version of this and have been using it since the start of the year using telegram with plugins for Codex and Claude.
The bots autonomously coordinated around and diagnosed some alerts while I was on a plane just now and filed the appropriate tickets.
Sometimes they get a bit long winded with each other, Codex even goes as much as calling Claude "expansive"
by zeafoamrun - I hacked this together with a small local irc server
- This sounds coolby thehamkercat
- I built a general version of this, with global addresses and messaging between any terminal-based agent + MCP for browser agents. OSS if you want to run your own server at https://github.com/awebai/aweb and hosted version at https://aweb.aiby juanre
- This totally breaks sandbox / VM isolation if you have Remote Control enabled. This feature isn't just within sessions on a single machine, but can send commands to any session accessible by your account.
Reading "Claude Code instructs the receiving Claude never to change permission settings" and so on in the docs makes it seem like they're using LLM classifiers to determine what commands are safe or not.
- I have built this with Claude as a script, but it can also message other models and get responses from them, and throughout my fleet of Linux machines via Tailscale. It's been mostly very useful, although occasionally you have to step in and interrupt if they start going the wrong way.by Cyuonut
- I wish there was a clean way to compact the conversation into a prompt with all necessary context for a new fresh conversation.by Alifatisk
- Just ask for one? Or maybe this was tongue in cheek!by resonious
- There is, but your wish of "clean" is ambiguous.by 4b11b4
- Just make a new slash command with those instructions as the prompt.by aqme28
- Have you tried Matt Pocock's "handoff" skill?by wccrawford
- Create your own protocol. I created a "wind down session" protocol my agents use that takes detailed notes in a "next_session_prompt.md" file that covers what was done this session, what is still open, and where they need to pick up the next session.
You can refine the protocol as you realize what's working and what isn't. I've been using that for months and it rarely drops important things now.
by anonym00se1 - I'm fed up with compaction. I want my agent to get compacted but also retain full access to the prior conversation via search and tool calls - I want it to know "the requirements for X were discussed in detail previously in conversation C51E31CE-C985-4633-A749-DCC9805A7FEB" and have a tool that lets it dispatch a subagent to find those details again.
Do any of the coding agents have this already?
by simonw - I was reading about the HF hack and one of the first thing the GPT swarm did was build a messaging system for themselves. This reminded me of that. (Also of how weirded out I was by Moltbook when it came out. Time flies!)
Unrelated: when my Claude/Codex finishes cooking (or needs my attention), it pings a local HTTP endpoint that plays a frog sound on my laptop. I found this massively boosts quality of life.
by andai - How do you know when they’re done (or need your attention)? Is that a standard “api”/hook? I want that!by zhoujianfu
- Does your terminal emulator not support bells/notifications? If it does, Claude Code (and albeit without checking surely Codex too) supports them natively.by liamwire
- Like some others, I also built this myself. Overly simply, with tmux, a memory tree, and handoff files and an orchestrator. And yet for how simple it was, it was so effective at minimizing the amount of duplicate context. It's like having shared specialist subagents who source and derive important shared knowledge from separate threads. It's useful because some skills just take too much of a token penalty to invoke and a single shared persistent session just lets that issue melt away. One agent pays the cost of that large skill once, and you don't have to keep paying for it in input tokens for the rest of that conversation.by eigenblake
- Have you maybe documented this anywhere or do you have suggestions for repos to look at that do this? This sounds interesting and I'd like to look into this myselfby Yokolos
- Does this work for different harnesses like Codex and Antigravity?
- Likewise I have the ability for agents to talk cross harness etc. pretty useful, token efficiency in question :p useful when you got lazy though and have 2 convergent sessions.by maxrev17
- This is obviously cool and useful so kudos, but wow security researchers have to throw their hands up all the time.
Now we open another attack surface where you can ask a remote agent to do things by default. There was a time when you call this a Remote Code Execution vuln. It's of course a feature here.
by zurfer - Making calls across a trust boundary, what could go wrong?by nizbit
- No, we have always called this RPC or IPC.by bsian
- Remote Control requires (relatively) manual pairing per session and setting the controlling session as trusted, even if the controlling session is a web browser. You can enable a more well-encompassing remote control "server" mode, but it requires extra configuration that isn't (at least clearly) visible in the app itself.by smileybarry