Show HN: Segue – Save context in one AI, load it in another by a short handle

Posted by csaguiar 4 days ago

Counter31Comment21OpenOriginal

Comments

Comment by fny 4 days ago

This is dangerous.

You're sending your context to someone's relay in plain text and loading it in plain text.

Comment by Flavius 4 days ago

Don't worry, they pinky promise not to save anything.

Comment by chmod775 4 days ago

Isn't saving it kind of the point?

Comment by vulture916 4 days ago

Either I'm an idiot or am missing something entirely (maybe a demo video would help?)

I've got to send it to your server so you can spit it back when I say a fancy word? What's worse, I pay you to just store/retrieve text? Why wouldn't I just write to a file?

Comment by mondainx 4 days ago

I'm glad you posted this before I took the time to review the link; saved me time. I'm certainly interested in a feature like this that's all local in my file system as I'm sure others are as well.

Comment by csaguiar 4 days ago

[dead]

Comment by tracker1 4 days ago

I 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.

Comment by csaguiar 4 days ago

[flagged]

Comment by planb 4 days ago

Why? "Summarize in detail what we're doing here and what we have done/learnt so far so another agent can continue" usually works and does not burn the full context length of tokens (uncached) in the new session.

Comment by 44za12 4 days ago

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?

Comment by pcpliu 4 days ago

This problem (context as code) is real, but for most individuals it’s not painful enough to paying for something or even setting up a thing.

I was having a similar product idea and quickly abandoned it after a demo ready.

Checkout https://memory.store/ (not affiliated). They target 2B users and focus more on centralized knowledge management for organizations, which I feel is more reasonable.

Comment by csaguiar 4 days ago

Thanks for the pointer. Memory.store seems to be capturing the context automatically. Segue is more a deliberate action. Some people want their AI to just remember. Some want to know exactly what crosses the boundary between tools. I am betting the second group exists and pays. You may be right that it is the smaller group. That is what the free tier is measuring.

Comment by orsenthil 4 days ago

This would be better if it was open source, and giving the option for the user to save the context in their storage (like Google drive) and load from it. I think, people might find it useful. The target audience could be folks who use claude , chatgpt on web or as desktop clients. They hardly know or care about .md files.

Comment by hsienchuc 4 days ago

I 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?

Comment by csaguiar 4 days ago

[flagged]

Comment by firasd 4 days ago

Very 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

Comment by tracker1 4 days ago

Ask your LLM in session to create a summary.md file... you can carry that into other sessions with different/new contexts.

Comment by firasd 4 days ago

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

Comment by tracker1 4 days ago

yeah, because downloading and copy/pasting file contents are so very hard to do.

Comment by telecuda 4 days ago

I like the name! I'd consider a self-hosted and open-source version as your "free" plan then a cloud-hosted paid version, and for $10+ if your goal is to make a profit vs. run a hobby project.

Comment by csaguiar 4 days ago

[dead]

Comment by KetoManx64 4 days ago

This 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"?

Comment by jensabacik 4 days ago

What was your initial problem? I usually work with contexts where they were created, like code session in Cursor / chat in Claude app. When do you have the need to often transfer the history?

Comment by rpicard 4 days ago

This 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.

Comment by 4 days ago

Comment by janrakete 4 days ago

It’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.

Comment by codeprimate 2 days ago

[dead]

Comment by outoftheweed 4 days ago

[dead]