[flagged]
Launch HN: Hyper (YC P26) – Company brain to power agentic development
41–50 of 88 posts
Re: Launch HN: Hyper (YC P26) – Company brain to power agentic development
#42Pretty cool. I understand the concept, but I wasn't able to get a clear answer on what the app actually does. Is it an MCP server? Or some viewer for my agent-compiled notes? Or just a UI for me to set up integrations? I got to the integrations page, but I'd like to understand what the app does before I just start connecting all my data.
Update: turns out that when you run the app it installs a hook to run every time you start a session, submit a prompt, or agent ends a turn on all your coding agents / platforms. Zero notice was given, pretty shady. I get it, you want to ingest data, but installing things onto my system without being transparent isn't great.
Re: Launch HN: Hyper (YC P26) – Company brain to power agentic development
#43why not just vibe code this?
several of our customers have tried. Turns out the long tail is very long, and the amount of maintenance/edge cases/access control issues/quality issues explodes dramatically. It's a tremendous amount of work to get right, especially as a company grows. If you have been able to vibe code this and see great results, would love to learn what you've done!
aren't the edge cases not generalizable and specific to the business? It doesn't seem like a one size fits all solution would work
Re: Launch HN: Hyper (YC P26) – Company brain to power agentic development
#44Pretty cool. I understand the concept, but I wasn't able to get a clear answer on what the app actually does. Is it an MCP server? Or some viewer for my agent-compiled notes? Or just a UI for me to set up integrations? I got to the integrations page, but I'd like to understand what the app does before I just start connecting all my data.
Update: turns out that when you run the app it installs a hook to run every time you start a session, submit a prompt, or agent ends a turn on all your coding agents / platforms. Zero notice was given, pretty shady. I get it, you want to ingest data, but installing things onto my system without being transparent isn't great.
We use hooks because they're the only reliable way to interact with the lifecycle of an agent without relying on the agent to constantly remember to make a tool call. It's much more reliable and guarantees a better end-user experience. We do explicitly say that we use hooks in the application, on the same page that you use to connect and manage your agents, but recognize that we can be more clear about it in the onboarding flow. Appreciate you trying out the product and also appreciate the candid feedback.
Re: Launch HN: Hyper (YC P26) – Company brain to power agentic development
#45Earlier quoted context omitted.
Thanks! We build as much in-house as possible. We've found that this is the only way to really build an excellent end-user experience without putting any of the burden on the user. Regarding sales, we've found that the most useful thing has just been putting the product in people's hands and demonstrating that it gives upfront value. The hard part with memory is that most of the value comes with compounding, so we've…
Thanks for the replies! Would love to swap notes at some point if you are up for it?
sure thing, feel free to shoot an email to founders@heyhyper.ai :) looking forward to it
Re: Launch HN: Hyper (YC P26) – Company brain to power agentic development
#46Interesting 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.
Re: Launch HN: Hyper (YC P26) – Company brain to power agentic development
#47Earlier quoted context omitted.
Appreciate the thoughtful questions. 1. I'll address this in two parts. (a) Memory vs. Enterprise Search. I consider search to address targeted, stateless retrieval whereas memory solves temporal, tacit, and derived problems. Glean can tell you why a ticket was filed or answer a specific question regarding a customer call. But in many companies, important questions are broader: "What went wrong the first time we went…
I made a mistake; apparently Glean uses knowledge graphs too: https://www.glean.com/resources/guides/glean-knowledge-graph This raises a follow-up question: what is your differentiation?
Fair enough, i was drawing the comparison between traditional enterprise search and what we do. There are several companies that borrow the graph-based data structure; this part is not so unique. They do have different methods for how that information is orchestrated, but I think I would reframe a bit: the end user problem does not start and stop with the memory algorithm and technical layer.
The main thing we see in the world is that (a) teams already struggle to coordinate information over many different personalities and data sources. This was a more dull problem before when the actual IC/execution overhead was so large. But now with AI the execution overhead is way smaller, and "being on the same page" is a much bigger problem. (b) As agents do more and more of the mechanical work in the company, it's vital that they have a consistent big picture-view to perform tasks efficiently without errors.
Hyper aims to solve this problem end-to-end; the memory system is a vital part of this, but Hyper does more. We already support native agentic email-writing and LinkedIn-drafting automations, and will be expanding on that front. Today it's a "brain that knows everything," but so much of the value is in using that brain to perform work in a self-improving way. And on the other side, we need to make sure that getting information into the system is as frictionless as possible. We care a ton about UX -- one-click integrations, using hooks to get context in and out invisibly and reliably.
Re: Launch HN: Hyper (YC P26) – Company brain to power agentic development
#48arent there a bunch of products just like this one?
It's a hot space right now! No one yet knows how this is going to shape up. We've realized (through tons of talking to users) that UX is a criminally underrated aspect of building this system effectively. The algorithms, infrastructure, performance, security have to be airtight, that much is true. But the reason that there is no winner yet in this space (even those these types of companies have been around for years) is because they often fail to deeply understand how users work, and how to build their products in a way that solves user problems comprehensively. It is a massive product design challenge; this is a core piece of infrastructure for how companies are going to be built in the future.
Re: Launch HN: Hyper (YC P26) – Company brain to power agentic development
#49It's a good idea to bet on this. There's a lot of business and domain knowledge trapped in random places and mostly aggregated in employees heads. Not very accessible to AI agents currently.
That said, this is the ultimate moat. Once everything about how to operate a business lives in your product, the business must rely heavily on it. I personally would only use something like this if I knew it was open source and that data could live on my own servers. If agents and my own team are consulting Hyper for things and you go out of business or move upmarket or something, it's pretty much back to the stone age for us.
Very useful idea though with a lot of potential, especially for companies like OpenAI and Anthropic looking for a moat!
Re: Launch HN: Hyper (YC P26) – Company brain to power agentic development
#50Earlier quoted context omitted.
several of our customers have tried. Turns out the long tail is very long, and the amount of maintenance/edge cases/access control issues/quality issues explodes dramatically. It's a tremendous amount of work to get right, especially as a company grows. If you have been able to vibe code this and see great results, would love to learn what you've done!
aren't the edge cases not generalizable and specific to the business? It doesn't seem like a one size fits all solution would work
Let me rephrase: vibe-coding something that will solve 80% of a company's problems in this domain still takes a tremendous amount of work, more than it seems on first glance, and it isn't worth the effort for many teams. We focus on solving this problem to the Nth level, full time, so that a company can exclusively focus on the things that are truly specific to them.