kanyesrthaker

7 ms·

1.
by kanyesrthaker 3mo ago
the predicates are determined by Hyper. this lets hyper shape a "custom" memory system for every organization based on the shape of information coming in.
2.
by kanyesrthaker 3mo ago
You are correct. In the onboarding process we install hooks to your machine (and also give an MCP option for unsupported agents that don't have a hook protocol). We do this because MCP is inherently unreliable -- you are at the whim of
3.
by kanyesrthaker 3mo ago
Hyper's focus is on the entire end-to-end experience from data coming in to agents performing work. We have made several distinct architectural decisions that we think make a significant difference, though we will be verifying this mor
4.
by kanyesrthaker 3mo ago
Appreciate the feedback. We are not currently a good fit for highly-regulated industries like gov't or medical, though we are working to meet those requirements. We currently run Hyper on our (cloud) infra because it's far and awa
5.
by kanyesrthaker 3mo ago
appreciate the congrats! This is a good question. The core thesis is that the brain is continually self improving. If your initial information is really bad or messy, then Hyper is going to only be able to start with that. But we provide ma
6.
by kanyesrthaker 4mo ago
In your specific example, we can use on external tool calls to supplement limited information. If the memory system isn't rich enough to get a good answer, we can always call back into the original data source for more information. Ext
7.
by kanyesrthaker 4mo ago
Thanks for the congratulations :) There is no magic sauce when it comes to differentiation in this space. Ultimately it comes down to having a very deep understanding of the problem, and a lot of empathy and love for our users. We have cert
8.
by kanyesrthaker 4mo ago
We do not train on any data, or sell the data that we host. Information on privacy can be found in our FAQ https://heyhyper.ai/faq and our privacy policy https://heyhyper.ai/privacy
9.
by kanyesrthaker 4mo ago
very sharp questions, love 'em. Yes, your intuition is correct. We by default will gather information k layers removed from the "frontier", and then have a shallow agentic step that can determine if we need to go further and
10.
by kanyesrthaker 4mo ago
Appreciate the vote of confidence! And definitely hear the concerns re: data control. We're of the opinion that it's much easier to have a trusted vendor securely handle the system, keep it up-to-date, fix issues with some SLA, et
11.
by kanyesrthaker 4mo ago
really great perspective. A lot of techniques from the past aren't conceptually wrong, we just have the tools today to make them efficient. The intuition behind them was always reasonable, if you could amortize the cost of making them
12.
by kanyesrthaker 4mo ago
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
13.
by kanyesrthaker 4mo ago
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, infrastru
14.
by kanyesrthaker 4mo ago
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
15.
by kanyesrthaker 4mo ago
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
16.
by kanyesrthaker 4mo ago
sure thing, feel free to shoot an email to founders@heyhyper.ai :) looking forward to it
17.
by kanyesrthaker 4mo ago
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 experi
18.
by kanyesrthaker 4mo ago
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 righ
19.
by kanyesrthaker 4mo ago
fair enough :) that's why it's a hard problem! different people have different levels of "trustworthiness" and this is exactly the kind of implicit mental model that employees form over years of working at a company. Hyp
20.
by kanyesrthaker 4mo ago
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
21.
by kanyesrthaker 4mo ago
Interestingly enough, this is how Hyper is structured under the hood. Rather than have one mega-agent whose job it is to go in and try to solve every problem simultaneously, we prefer a "production line" of narrowly scoped agents
22.
by kanyesrthaker 4mo ago
totally, honestly it's super inspiring to see how fast the field is moving. That being said though, I think there's a long way to go in this category. Efficient memory across tools, especially in a multiplayer/collaborative s
23.
by kanyesrthaker 4mo ago
Good question. User data is the right of the user. We don’t have automations for everything yet (we’re super early!) but any user has total right to request deletion, updates, or deliverance of their data, which we seek to comply with fully
24.
by kanyesrthaker 4mo ago
Thank you! Very hot space right now and excited to be building in it
25.
by kanyesrthaker 4mo ago
Thanks Nils!
26.
by kanyesrthaker 4mo ago
The current conflict resolution is fairly simple: always trust humans, and trust recent human info more than old human info. We're very aware that as the knowledge system gets more complex, we'll need more sophistication, includin
27.
by kanyesrthaker 4mo ago
Very strange, haven't seen this before. Could you shoot us an email at founders@heyhyper.ai with some more details about what you're seeing?
28.
by kanyesrthaker 4mo ago
Hey HN! Kanyes here, one of the cofounders of Hyper. Here all day to answer any questions :)
29.
Ask HN: Leaving Notion, Codebase as a Wiki?
3 points by kanyesrthaker 6mo ago|3 comments
30.
Show HN: Hyper – Voice Notes for Whiteboarding Sessions(apps.apple.com)
4 points by kanyesrthaker 6mo ago|0 comments

More ›