Interesting product. I know others building in this space. How are things going with existing customers? And how are you measuring deltas vs standard agentic processes? Are you using RAG under the hood?
Thanks for asking! Existing customers use Hyper consistently to power agents for email drafting, managing inbound, generating marketing materials, improving debugging workflows, and as a "backbone" for long-running parallel coding agents. Having relevant, narrow context at all times greatly improves performance.
Right now our measurements are primarily subjective; we have several customers tell us "Hyper let my agent draft outbound/do market research/run experiments overnight with no intervention or follow-ups, when I would have to constantly babysit it in the past." We have also run Hyper's algorithms on common benchmarks versus more traditional methods. I don't want to claim numbers before we've verified them, but Hyper performs significantly better.
We do not use RAG in the traditional sense (semantic similarity across chunked source documents). We use hybrid retrieval methods to fetch relevant information across our carefully designed knowledge graph, and then have shallow agents consolidate retrieved information into a format that the invoking agent can understand.
It's nice to see people building things, but honestly I found the demo video a bit disappointing. A bit too slow, a bit too choppy, a bit hand wavy. It didn't make me grasp why I needed this in my life.
I like it. I am building something very agent-use focused (https://sdocs.dev) and I’ve been thinking of introducing a /agent-evaluation page, which an agent can curl to then discuss with their user if SmallDocs is right for them. I really like the agent action to email flow. I’m introducing user accounts + subscriptions soon and think I’ll use that.
And now we see the beginning of how even local LLMs will be turned against their users -- by persuading agents to advertise to them.
I don't think that's what you're intending here, but it's the next logical step. Agents are on the Internet, and they represent an opportunity to reach their humans.
This is exactly my view and exactly what I’m building at https://sdocs.dev.
It’s Word if it were for cli based agents. It’s cli-first, markdown first, and you rarely if ever create the docs. Instead you tell your agent, “research X and give it to me in a sdoc”, or “sdoc this bug report so I can share it with Andy”.
1) Very nice implementation 2) Very nice domain! Did you always own "files.md"? 3) Re storing things on your server, what is the security layer around that?
I have been building a slightly different solution to the same problem. So far I’m pretty happy with the results and I have enough returning users that I think others are too (https://sdocs.dev/analytics).
SDocs is cli (`sdoc file.md`) -> instantly rendered Markdown file in the browser
When you install the cli it gives you the option to add a note in your base agent file (`~/.claude/CLAUDE.md`, etc.). This means every agent chat knows about SDocs and you can say “sdoc me the plan when you’re done with it” and the file will pop open instead of you having to find that terminal session to know it’s done.
Going browser first means you’re not required to install anything to get a great experience.
Despite being in the browser, the content of SDocs rendered Markdown files remain entirely local to you. SDoc urls contain your markdown document's content in compressed base64 in the url fragment (the bit after the `#`):
The sdocs.dev webapp is purely a client side decoding and rendering engine for the content stored in the url fragment.
This also means you can share your .md files privately by sharing the url.
I've enjoyed exploiting the HTML rendering side of things which is possible by displaying Markdown in a browser. I’ve added tagged code blocks that the agent is given documentation on how to use. Eg ```chart or ```mermaid (for mermaid diagrams). These then become interactive elements on the page (mermaid is best example of this currently). See live renderings of these options here - charts gallery: https://sdocs.dev/s/yO3WbxFf#k=arcDBnizla5n437VFAeiQcwlu8kh_..., diagrams gallery: https://sdocs.dev/s/B_Ux11DV#k=KsvheEkiBFai6acnoIJnrOdfVRS5u...
I've been experimenting with a fairly vibecoded Office 365..., but rooted in the world of vibe (an advanced Markdown reader which can do complex things like render charts and mermaid diagrams, see: https://sdocs.dev, https://sdocs.dev/#sec=charts, https://sdocs.dev/#sec=diagrams). Slides coming soon too... But this is very much a subsection of the full Office suite.
reply