Launch HN: OneCLI (YC S26) – OSS sandboxed agent harness for teams
Launch HN: OneCLI (YC S26) – OSS sandboxed agent harness for teams
我们发现了什么
enjoy global connections at the team level, like shared LLM keys or service accounts Here’s a demo: https://www.youtube.com/watch?v=dlW-44ntpbE We started working on this by accident, even t
- 来源:Hacker News(首次 2026-07-24 · 最近 2026-08-20)
- 证据等级:D · 发现产品或需求信号,暂未获得可核验的商业证据。
- 商业模式:API / Usage-based
- 主题:AI Agent
- 初筛评分:27.9/100 · 收录 2 次
证据,比故事更重要。
规则清洗与初筛,未经人工商业核验。原文语境、实际客户和付费情况仍需自行验证。
引用与数字披露
来源类型(原作者自述/第三方测算/媒体转引)需采集端标注,本版尚未落字段。
- 作者
- 未标注
- 抓取日期
- 来源类型
- 未标注
- 币种
- 未标注
- 口径
- 未标注
- 披露主体
- 未标注
- 披露日期
- 未标注
中文辅助译文(全文)
HN 大家好,我们是来自 OneCLI 的 Jonathan 和 Guy,这是一款为团队打造的智能体(agent)管理框架(harness),让每位员工都拥有一个安全、沙箱化的个人智能体。你可以用它做这些事情:
- 获得一个沙箱化的智能体,所有 OneCLI 能力都已就绪,例如直接从聊天中连接你的 GitHub 账户、Gmail、Notion 或 Dropbox。
- 在聊天中即可完成确定性的“人机协同”审批,适用于那些你需要 100% 把控的事情,比如发送邮件或删除 Linear 工单。
- 在一处管理团队策略,并将其强制执行到工作区中的每个智能体上。
- 在团队级别享受全局连接,例如共享的 LLM 密钥或服务账户。
这是演示视频:https://www.youtube.com/watch?v=dlW-44ntpbE
我们其实是偶然开始做这个项目的,尽管我们的职业生涯都来自安全领域。我们当时在做一个名为 ChartDB 的开发工具,是一款开源数据库工具。今年一月 OpenClaw 火起来时,我们开始用它来在 ChartDB 之上编排智能体。我们很快意识到认证方面存在一个重大问题:智能体需要凭证才能完成实际工作,但把这些密钥交给它们并非明智之举。它们会把密钥保存在内存中,还会以明文形式写入本地文件和会话中。我们知道智能体很容易被骗,从而交出这些 API 密钥/凭证。因此我们需要某种方式来控制智能体,阻止提示注入(prompt injection)诱使它利用其服务为攻击者牟利。我们创建了 OneCLI,最初它只是一个用 Rust 编写的 AI 智能体保险库。我们发现,对 OneCLI 的大部分需求来自像 Hermes、OpenClaw 和 NanoClaw 这样面向个人和团队的自主智能体。用户希望找到能为自己执行任务的实用智能体,但缺少两块拼图:1) 密钥和权限管理;2) 面向团队的多人协作管理。我们决定转型,直接把智能体本身作为面向团队的框架提供给每位员工。我们看到团队不得不一次又一次地搭建自己的框架,而我们已经把保险库作为网关,因此想到把智能体管理这块缺失的部分开箱即用地提供出来,并将其开源(Apache-2.0 协议,含少量企业例外条款)。
我们坚持开源优先——是整个平台,而不仅仅是像其他智能体那样的一小部分,这样企业才能真正看到代码、评估它并信任它,而不是凭我们的一面之词。他们可以在自己的环境中以生产级的质量隔离运行它,完全由自己掌控,而不是一个托管在某处的封闭黑盒。这意味着安全不仅仅是承诺,而是他们可以自行验证的东西。结合真正的自主性和最小权限访问,这就是为什么它是一家企业可以完全拥有和信任的东西,而不仅仅是采用它。
我们也从企业视角而非个人视角来解决这个问题。我们的解决方案代表每位员工管理智能体,并用由公司管理员通过集中策略配置的确定性护栏将其包裹起来。智能体引擎本身,我们使用的是 jcode,它是 agent-loop 的核心。我们发现它能提升体验,让智能体更聪明、更快速。
它的工作原理如下:
- 运行在你控制的基础设施上。完全开源,几分钟内即可自托管或部署到云端。
- 智能体永远不持有真实凭证。它获得的是一个占位符。真实凭证在调用获得授权后,在网关处按请求注入。它永远不会进入智能体的上下文、内存或日志。
- 在模型之外强制执行。提示只是建议。由组织管理员定义的策略在网络层运行,位于智能体和 LLM 之外。封锁端点、按智能体限速、要求审批、按员工限定权限。由网关来决定。智能体无法绕过它。
- 每个智能体独立的隔离虚拟机。独立的内存、独立的密钥、独立的权限。爆炸半径仅限于单个智能体。
- 框架的速度:智能体循环之下是 Rust 引擎。
- 完整的身份追溯。每个智能体都绑定到一名员工。每次调用都记录了它为谁执行,以及哪条策略授权了该操作。
人们用该平台在做的一些事情包括:
- 完全通过销售电话来管理公司的整个生命周期,再到产品端自动向工程团队开单,从而启动开发智能体完成交付并发布到生产环境。
- 运营方面,比如在通话后自动维护 CRM、筛选潜在客户、预约会议并管理跟进邮件。
- 我们的一些客户还让这些智能体完成他们所有的杂货采购,并让它们处理日常事务,比如在线下单。
关于团队:两位创始人都出身网络安全背景。Jonathan 曾在 Axis Security 工作多年,主攻零信任网络访问。其核心理念是永远不信任客户端。你来决定一个人可以访问什么,并在网络层(即客户端之外)强制执行,因此客户端尝试做什么并不重要。这就是如今每家严肃的公司向人类提供访问权限的方式。Guy 是 Argon Security 的第一名员工,负责应用安全(AppSec)。我们非常期待听到你对这次转型的看法,欢迎提交 issue 以帮助我们改进,让你的智能体既强大又安全——为团队而设计,而不仅仅是面向个人。
译文由上游机器翻译生成,可能有误;判断请以英文原文为准。
英文原文(来源本站未改写)
Hi HN, Jonathan & Guy here from OneCLI, an agent harness built for teams, giving every employee a secured, sandboxed personal agent.Here’s what you can do with it: 1. get a sandboxed agent, with all the OneCLI capabilities in place like connect your GitHub account, Gmail, Notion, or Dropbox simply from the chat. 2. deterministic human in the loop approval in the chat itself for things that you need 100% control like sending an email or deleting the Linear ticket. 3. manage team policy in one place, enforced across every agent in the workspace 4. enjoy global connections at the team level, like shared LLM keys or service accounts Here’s a demo: https://www.youtube.com/watch?
v=dlW-44ntpbE We started working on this by accident, even though our careers were in the security space.We were working on a devtool called ChartDB, an open-source DB tool.When OpenClaw took off back in January, we started using it to orchestrate agents on top of ChartDB.We quickly understood there is a big issue around auth.Agents need credentials to do real work, but to give them those secrets would not be the best idea.They keep them in their memory and also write them down to local files and their sessions as plain text.And we knew that agents can easily be fooled into giving up those API keys/secrets.
So we needed some way to control the agent and stop prompt injections from tricking it into using its services for an attacker's benefit.We created OneCLI that started as a vault for AI Agents built in Rust.We found out that most of our demand for OneCLI came from autonomous agents like Hermes, OpenClaw and NanoClaw for individuals and teams.Users looked for useful agents that do things for the person who runs them with two missing parts: 1) managing secrets and permissions. 2) and for teams - multiplayer management.We decided to pivot and provide the agent itself as a harness for teams, to give each employee an agent.
We saw that teams had to deal with setting up their own harness again and again, and basically as we already had the vault as a gateway.We got the idea to provide the missing piece of the agent management out of the box and open source it (Apache-2.0, with a small enterprise exception).We're open source first - the entire platform, not just a small portion of it like other agents, so companies can actually see the code, evaluate it, and trust it instead of taking our word for it.They run it isolated, in their own environment, fully under their control, at production quality, not a locked black box hosted somewhere else.
That means the safety isn't just a promise, it's something they can verify themselves.Combined with real autonomy and least-privilege access, that's what makes it something a company can fully own and trust, not just adopt.We also approach this from a company perspective rather than an individual one.Our solution manages agents on behalf of each employee, wrapped in deterministic guardrails that company admins configure through centralized policies.For the agent engine itself we’re using jcode which is the core of the agent-loop.We found out that it improves the experience and makes the agent smarter and faster.Here’s how it works: It runs on infra you control.
Fully open-source, self-host or cloud in minutes.The agent never holds a real secret.It gets a placeholder.The real credential is injected at the gateway, per request, after the call is authorized.It never enters the agent's context, memory, or logs.Enforcement outside the model.Prompts are suggestions.Policies defined by the org admin run at the network layer, outside the agent and the LLM.Block endpoints, rate limit per agent, require approval, scope per employee.The gateway decides.The agent can't bypass it.Isolated VM per agent.Own memory, own keys, own permissions.Blast radius is one agent.Speed of the Harness: Rust engine under the agent loop.Full identity trail.
Every agent is bound to an employee.Every call logged with who it acted for and which policy allowed it.Some things people are doing with the platform include: - Managing their company life cycle entirely from the sales calls, to the product side automatically open tickets to the engineering teams, that would kick the development agents to deliver and ship to production. - Operational side, like automatically hygiene the CRM after calls, sourcing leads, book meetings and manage follow ups emails. - Some of our customers also doing their entire grocery shopping using those agents and send them to take care of their chores like ordering things online.
About the team: Both founders come from cybersecurity backgrounds.Jonathan spent years at Axis Security building zero trust network access.The core idea is that you never trust the client.You decide exactly what a person can reach, and you enforce it outside of them, at the network layer, so it doesn't matter what the client tries to do.That's how every serious company gives access to humans today.Guy was the 1st employee in Argon security doing AppSec.We would love to hear your thoughts on the move, happy to get issues open to improve and get your agent to be powerful and secure - designed for teams, not just individuals.
这条还缺什么证据?
下面每条都由本条已有字段推出(等级、理由、商业模式、来源次数、是否演示), 本站不生成推测性结论;通用验证方法放在方法论页。
- 可核验的收入或付费证据查官网定价页与付费口径;第三方数据源(如 GetLatka)只作旁证,需标注来源与时点。
通用验证清单(谁有这个问题/谁愿意付费/一个人能交付哪一小步)见我们的筛选方法。