Launch HN:Hyper (YC P26) – 以公司大脑赋能代理式开发

9作者: shalinshah30 天前
各位 HN 的朋友们,我们是 Shalin 和 Kanyes,是多年的挚友,一起编程超过十年,现在是 Hyper (<a href="https://heyhyper.ai/">https://heyhyper.ai/</a>) 的创始人。Hyper 是一个共享的“公司大脑”,能够接入公司内部的信息流,从而提升 AI 代理和自动化系统的能力,最终为人们节省时间。 现在的模型已经足够强大,可以(在很大程度上)处理长周期、复杂的任务。我们认为当前的瓶颈在于,这些足够智能的模型往往缺乏关于你公司的信息,而这些信息分散在人们的头脑中、Slack 聊天记录里、过时的文档中,以及与 AI 的来回对话中。 MCP(多模态上下文处理)对于将部分信息提供给代理很有用,但存在一些问题:(1)一旦会话结束,洞察力也随之消失,所以每次都需要复制粘贴整个文档,而不是让代理每次都去翻阅云盘——这并没有带来多少便利;(2)即使 MCP 有效,它收集到的信息也不是全面的,因为人们会在白板上做决定,大声头脑风暴,在 Slack 上发一些零散的信息,然后把剩下的写在文档里,这导致代理只能基于不完整的信息进行工作;(3)即使它拥有所有信息,它也无法进行出色的工作所需的元推理。如果你粘贴一个 Notion 文档,它不会学习你的设计品味或写作风格,除非你明确告知,而且它也不会知道某个决定是如何做出的,或者是在什么时候做出的。 五年前,我们还是大学生时,就热衷于“思维工具”的浪潮,成为了 Notion、Obsidian、Roam、Anki 的重度用户,坚信构建“第二大脑”。在 GPT-3.5 发布后,我们开始意识到,如果 AI 能够真正阅读这个第二大脑,它将变得多么强大,因为突然之间,它就能了解我们的背景故事、品味和偏好,并解锁真正全新的能力。这就是我们构建 Hyper 的**原因**。 我们知道 Hyper 不适合所有人!但对于那些希望走在技术前沿的人来说,它是一个强大的倍增器,能让代理更快、更好。它增加了代理可以执行的任务数量,以及它们执行任务的效率。 Hyper 的工作原理是摄取你授予它访问权限的所有内容,包括文档、Slack、电子邮件、日历、Granola 等,并将其合成为一个包含事实及其关系的知识图谱,并带有用于语义搜索的嵌入。我们构建的记忆系统是混合式的,具有两种模式。**事件(Episodes)**是作为事实来源的原始数据。**事实(Facts)**是从每个事件中提取的含义,以主语-谓语-宾语记录的形式存储,并附有事实引入的时间戳以及失效时间戳(主语=人,谓语=在...工作,宾语=公司)。事实形成一个图谱,它们之间有类型化的边:X 与 Y 存在冲突,A 源自 B,J 优先于 K。每当有新事实进来时,我们都会更新其邻近的事实,以保持图谱的最新状态,这就是我们处理过时信息的方式。当“我们周五发货”后来被“我们周一发货”所否定时,新事实会取代旧事实,而不是两者看起来都同样真实,而且我们从不自动丢弃被取代的版本,因此你仍然可以询问我们是如何决定周一发货的。 每个事实都带有其来源的出处和访问控制标签,标明谁有权查看它。在检索时,我们进行查询扩展,然后将基于嵌入的语义搜索与 Postgres 全文搜索结合起来,使用倒数排名融合(reciprocal rank fusion),并且我们只针对该用户有权访问的事实和事件评估查询,这意味着同一团队的两个人提出相同的问题可能会得到不同的答案。我们通过 Webhook(如果存在)和轮询(如果不存在)来保持信息的新鲜度,并通过哈希内容来捕获没有原生去重功能的数据源的变化。代理通过两条路径进行读写:在 Claude Code、Cowork、Codex 和 Cursor 等工具中的生命周期钩子(lifecycle hooks),我们在每次提示时注入相关上下文,并从每次响应中提取有趣的事实;以及用于所有不暴露钩子的通用 MCP 工具调用。 我们非常喜欢它!我们的早期用户也是如此:一位 CEO 使用 Hyper 以他自己的风格起草电子邮件,并包含完整的公司背景信息。过去每周需要数小时的工作,现在只需几分钟,而且随着 Hyper 对他思维方式和公司变化的了解越来越多,每次都更加精准。一位 YC 的创始人一次性完成了产品发布视频脚本的撰写,因为 Hyper 已经了解了他们几个月来积累的产品、语调和定位信息。 我们提供 3 天的免费试用,更多信息请参阅我们的定价页面 (<a href="https://heyhyper.ai/pricing">https://heyhyper.ai/pricing</a>),FAQ (<a href="https://heyhyper.ai/faq">https://heyhyper.ai/faq</a>) 中也有更多细节,包括隐私、合规性以及我们与其他“记忆”公司的区别。 快来试试吧!尽情地测试它!并告诉我们它还有哪些不足:<a href="https://heyhyper.ai/">https://heyhyper.ai/</a>。我们很乐意为您打造一个 10 星的体验 :) 欢迎评论!
查看原文
Hey HN, we’re Shalin &amp; Kanyes, best friends who&#x27;ve been hacking together for 10+yrs, and now founders of Hyper (<a href="https:&#x2F;&#x2F;heyhyper.ai&#x2F;">https:&#x2F;&#x2F;heyhyper.ai&#x2F;</a>). Hyper is a shared “company brain” that plugs into information flowing inside a company to make AI agents and automations better and ultimately save people time.<p>Models have gotten good enough that they can (mostly) take on long-horizon, complex tasks. We believe the bottleneck now is that these smart-enough models often lack information about your company, which is scattered in people&#x27;s heads, Slack threads, stale docs, and in back-and-forth convos with AI.<p>MCP is useful for getting some info in front of an agent, but there are problems: (1) Once the session dies, so does the insight, so instead of copy-pasting a whole doc each time you&#x27;re telling the agent to dig through Drive each time - not much of a win; (2) Even when MCP works, what it gathers isn&#x27;t comprehensive, because people decide things on a whiteboard, brainstorm out loud, post a little in Slack, and scribble the rest in a doc, which leaves the agent working from partial information; (3) And even if it had everything, it doesn&#x27;t do the meta-reasoning required to do a great job. If you paste in a Notion doc and it won&#x27;t learn your design taste or your writing style unless you tell it to, and it won&#x27;t know why a decision was made or when.<p>As undergrads 5 years ago, we were into the tools-for-thought wave and became power users of Notion, Obsidian, Roam, Anki, real believers in building a second brain. After GPT-3.5 came out we started to realize how much more powerful that second brain could be if an AI could actually read it, because suddenly it would know our backstory, our taste, our preferences, and unlock genuinely new capabilities. That’s <i>why</i> we’re building Hyper.<p>We know it’s not for everybody! But for people who do want to be on the cutting edge, this is a force multiplier that makes agents faster and better. It increases the number of tasks they can do, and how effectively they do them.<p>Hyper works by ingesting everything you give it access to, Docs, Slack, Email, Calendar, Granola, and synthesizes it into a knowledge graph of facts and their relationships with embeddings for semantic search. The memory system we’ve built is hybrid, with two modalities. Episodes are the raw source items kept as the source of truth. Facts are the meaning pulled out of each episode, stored as subject-predicate-object records with a plain summary and timestamps for when the fact was introduced and when it was invalidated (subject=person, predicate=works_at, object=company). Facts form a graph with typed edges between them: X is in tension with Y, A is derived from B, J supersedes K. Every time a new fact comes in we update the facts in its neighborhood, so the graph stays current, and that&#x27;s how we handle stale information. When &quot;we&#x27;ll ship Friday&quot; is later contradicted by &quot;we&#x27;re shipping Monday,&quot; the new fact supersedes the old one instead of both looking equally true, and we never auto-discard the superseded version, so you can still ask how you landed on Monday.<p>Every fact carries provenance back to its source and access-control tags for who is allowed to see it. At retrieval we query-expand, then fuse semantic search over embeddings with Postgres full-text search using reciprocal rank fusion, and we only ever evaluate a query against the facts and episodes that person has access to, which means two people on the same team can ask the same question and get different answers. We keep information fresh with webhooks where they exist and polling where they don&#x27;t, hashing contents to catch changes for sources that don’t handle native dedupe. Agents read and write through two paths: lifecycle hooks in tools like Claude Code, Cowork, Codex, and Cursor, where we inject relevant context on every prompt and pull interesting facts out of every response, and plain MCP tool calls for everything that doesn&#x27;t expose hooks.<p>We love it! and so do our early users: one CEO uses Hyper to draft emails in his voice with full company context. What took hours&#x2F;week now takes minutes and gets sharper each time Hyper learns more how he thinks and how his company is changing. One YC founder one-shotted a launch video script because Hyper already knew their product, voice, positioning accumulated over months.<p>We have a 3-day free trial, explained more on our pricing page (<a href="https:&#x2F;&#x2F;heyhyper.ai&#x2F;pricing">https:&#x2F;&#x2F;heyhyper.ai&#x2F;pricing</a>) and there are more details in our FAQ (<a href="https:&#x2F;&#x2F;heyhyper.ai&#x2F;faq">https:&#x2F;&#x2F;heyhyper.ai&#x2F;faq</a>), including things like privacy, compliance, and how we’re different from other “memory” companies..<p>Give it a spin! break it! and tell us where it falls short: <a href="https:&#x2F;&#x2F;heyhyper.ai&#x2F;">https:&#x2F;&#x2F;heyhyper.ai&#x2F;</a>. We&#x27;d love to build you a 10-star experience :) Comments welcome!