21–29 of 29 posts
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?
Earlier quoted context omitted.
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
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?
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.
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.
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.