Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Message your other Claude Code sessions

code.claude.com

Post reply on HN
Print view View original

71–76 of 76 posts

Re: Message your other Claude Code sessions

#71

Post by maxrev17 »

eigenblake wrote: post #10

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 a…

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.

Re: Message your other Claude Code sessions

#73

Post by pixel_popping »

nizbit wrote: post #58
zurfer wrote: post #42

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.

Making calls across a trust boundary, what could go wrong?

Pretty much nothing with minimum viable guardrails (restricted shell into Container into MicroVM into VM + Firewall) which any dev knows how to setup, the fact that most don't is mostly about lazyness/recklessness.

Ready for the downvotes.

Re: Message your other Claude Code sessions

#74

Post by andai »

liamwire wrote: post #47
andai wrote: post #4

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.

Does your terminal emulator not support bells/notifications? If it does, Claude Code (and albeit without checking surely Codex too) supports them natively.

I spent a little while messing with configurations and I got the PC beep speaker working on Ubuntu again, but it was a horrible sound so I turned it off again.

Re: Message your other Claude Code sessions

#75

Post by deviantintegral »

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.

Re: Message your other Claude Code sessions

#76

Post by smileybarry »

zurfer wrote: post #42

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.

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.
Post reply on HN