社区 Community 需审批 Needs approval 多Agent Multi-agent

Open Bot:开源「每席一电脑」Grok Bot 替代(任意 AG-UI harness) Open Bot: open-source Grok Bot-style coworkers on any AG-UI harness

Open Bot: open-source Grok Bot-style coworkers on any AG-UI harness

开源同事席:每席一台电脑,可接任意 Agent。 Open-source coworkers, each with a computer and any agent harness.

Open Bot:开源「每席一电脑」Grok Bot 替代(任意 AG-UI harness) 预览
打开原文Open source

详细介绍Details

Show HN CopilotKit/OpenBot:MIT 开源「AI coworkers」——每席有独立电脑(浏览器/文件/工具),动作先决策后记录;可接任意 AG-UI agent harness,不绑死单一厂商。仓库 README 与站点可核验;维护者在 HN 注明仍为 alpha。对想对照 Grok Bot「专席电脑 + 可审动作」的人,是可自建的相邻方案。 Show HN CopilotKit/OpenBot: MIT open-source AI coworkers — each seat gets its own computer (browser/files/tools), with actions decided before and recorded after; bring any AG-UI agent harness, no single-vendor lock-in. README and site verified; maintainers note alpha on HN. A self-hostable adjacent option for people comparing Grok Bot’s per-seat computer + reviewable actions.

为什么推荐Why we recommend it 来源已核对;本站没有实测,效果以原文为准。 Sources checked; not tested here. Results follow the original source.

核验记录:来源、抓取与截图说明Verification log: sources, checks, and captures

MIT(2026-09-22 gh api)。Show HN item 49365575:alpha,路线图仍在推进;收录为可复现的开源相邻栈,不当官方 Grok Bot 替代品宣传。 (item 49365575)MIT (gh api, 2026-09-22). Show HN item 49365575: alpha with an active roadmap; catalogued as a reproducible open-source adjacent stack, not marketed as an official Grok Bot replacement. (item 49365575)

上手路径How to start

审批边界Approval boundary

自建部署的账号、密钥与对外动作权限自行管控;alpha 功能勿直接上生产。 Self-host deployments need your own account/key/action controls; do not put alpha features straight into production.

  1. 先跑一次安全范围Run a safe first pass

    先在可撤回、不外发的范围内试跑。本条未批准前:自建部署的账号、密钥与对外动作权限自行管控;alpha 功能勿直接上生产。。 Try it first in a reversible, non-outbound scope. Until approved: Self-host deployments need your own account/key/action controls; do not put alpha features straight into production..

  2. 存 SkillSave a Skill

    把跑通的步骤存成 Skill,下次同类任务直接复用,而不是重新口述。 Save the working steps as a Skill so the next similar job reuses them instead of being re-explained.

  3. 再上 RoutineThen add a Routine

    确认输出可靠后,再考虑定时或事件触发;例行默认仍应停在待审。 After output is reliable, consider a schedule or event trigger. Routines should still stop at review by default.

相关案例Related cases