51–60 of 76 posts
Earlier quoted context omitted.
Does this work for different harnesses like Codex and Antigravity?
codex has been able to send messages across threads for a long time
I wish there was a clean way to compact the conversation into a prompt with all necessary context for a new fresh conversation.
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.
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.
I wish there was a clean way to compact the conversation into a prompt with all necessary context for a new fresh conversation.
Have you tried Matt Pocock's "handoff" skill?
I wish there was a clean way to compact the conversation into a prompt with all necessary context for a new fresh conversation.
Just make a new slash command with those instructions as the prompt.
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.
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.
No, we have always called this RPC or IPC.
Earlier quoted context omitted.
codex has been able to send messages across threads for a long time
But what if I use parallel agents from different harnesses? Then I probably need to build my own communication tool