Others have already pointed out the absurdity, but just to put it across. Why not just ask first agent to update AGENTS.md adding context and next steps, and ask the next agent to continue from there?
Show HN: Segue – Save context in one AI, load it in another by a short handle
11–20 of 29 posts
Re: Show HN: Segue – Save context in one AI, load it in another by a short handle
#12Very interesting. This is the #1 thing LLMs don’t have and should: discrete data handles. Like literally you can’t save & manage a todo list in the default Claude or ChatGPT web or iOS apps. So this is like a pastebin that works cross chat I assume
Re: Show HN: Segue – Save context in one AI, load it in another by a short handle
#13It’s not a bad idea in itself, but as others have already said, it can be handled more securely using a local file. Especially now, with all the discussion about sovereignty and local hosting, a service like this is rather counterproductive.
But perhaps this could be used to build a local solution with a little more added value. It might be interesting to use the context to determine which AI solves the problem best or most cost-effectively.
Re: Show HN: Segue – Save context in one AI, load it in another by a short handle
#14I use two AI CLIs every day (one for main tasks and the other for review), and context migration is a real pain point.
My current workaround is to write the context as a Markdown file and save it to disk, then let both of two CLI to read. I'd like to ask you, what are the advantages of this tool compared to using a file as a bridge?
Re: Show HN: Segue – Save context in one AI, load it in another by a short handle
#15I usually just ask the agent to create a summary document in markdown format... I'll sometimes play out what I want to do on my phone in conversational modes, then take that output and start with it against a coding tool to continue/start actual work on things.
I tend to spend a lot more time planning than what it takes to execute/build what I'm after.. then more time reviewing again than the produce step(s) and iterate.
For that matter, I'll track what I'm wanting and what has been done via TODO.md file in project(s).
I'm not sure I would ever use/trust a service like this myself. I barely trust the AI providers as it is.
Re: Show HN: Segue – Save context in one AI, load it in another by a short handle
#16Very interesting. This is the #1 thing LLMs don’t have and should: discrete data handles. Like literally you can’t save & manage a todo list in the default Claude or ChatGPT web or iOS apps. So this is like a pastebin that works cross chat I assume
Ask your LLM in session to create a summary.md file... you can carry that into other sessions with different/new contexts.
Re: Show HN: Segue – Save context in one AI, load it in another by a short handle
#17This is such a great name and domain for this purpose.
I don’t think I’d like using a third party server for this, but a skill that just handles it locally or something would be useful.
Re: Show HN: Segue – Save context in one AI, load it in another by a short handle
#18This is a paid, more complex version alternative to just telling your agent to "update the agents.md, plan.md and decisions.md for future agents after you finish and test your changes"?
Re: Show HN: Segue – Save context in one AI, load it in another by a short handle
#19Very interesting. This is the #1 thing LLMs don’t have and should: discrete data handles. Like literally you can’t save & manage a todo list in the default Claude or ChatGPT web or iOS apps. So this is like a pastebin that works cross chat I assume
Ask your LLM in session to create a summary.md file... you can carry that into other sessions with different/new contexts.
So in this session.md idea the user has to figure out how to download and re upload this file each time? Really annoying workflow that almost nobody will use
Re: Show HN: Segue – Save context in one AI, load it in another by a short handle
#20I usually just ask the agent to create a summary document in markdown format... I'll sometimes play out what I want to do on my phone in conversational modes, then take that output and start with it against a coding tool to continue/start actual work on things. I tend to spend a lot more time planning than what it takes to execute/build what I'm after.. then more time reviewing again than the produce step(s) and iter…
[flagged]