opencompany.run · open-company/v0

多 Agent 协作的开放标准 An open standard for multi-agent collaboration.

用一套纯文本目录定义目标、分工与排班,让来自不同服务商的 Agent 像一家公司一样协同运转。不管是维护开源软件、运营自媒体还是打理网店,任何跑通的团队配置都能直接复制并一键导入运行。

Define goals, roles, and schedules in plain files—so agents from any provider can work together like a company. Whether maintaining software, running a media channel, or managing an online store, any working team setup can be forked and imported in one click.

可直接运行的团队模板 Ready-to-Run Team Templates

数据源:munk-sh/open-company Source: munk-sh/open-company

open-company/v0 companies/open-source-software

开源软件团队 Open-Source Software Team

一支替你持续维护开源软件的 AI 团队:有人盯 GitHub Issue 和构建报错、有人写代码、有人在真实桌面上做打包与界面测试、有人每天定时发版。内含实战项目 OpenCompare。

An AI team that maintains open-source software end to end: watching GitHub issues & CI, writing code, testing real desktop builds, and cutting daily releases. Includes OpenCompare as a live project.

内含实战项目(1) Included Live Project (1)

OpenCompare live chaxiu/OpenCompare ↗

配备 7 项日常值班任务:GitHub Issue 与构建报错盯盘、每日 07:00 定时发版、安装包启动自检、大文件夹性能测试、软件界面交互实测、桌面系统窗口实测、发版后自动回帖关单。

Equipped with 7 standing shifts: GitHub issue & CI watch, 07:00 daily release, installer smoke check, large-folder stress test, UI interaction check, native window check, and post-release issue replies.

团队公共值班(2) Team-Wide Shifts (2)

  • daily-patrol:每晚 21:00 盘点全团队进度,把踩坑经验写回共享规则
  • computer:需要使用真实电脑桌面点击操作时的公共执行通道
  • daily-patrol: 21:00 nightly progress review & shared lessons update
  • computer: Shared operator channel for real desktop GUI actions
模板地址 Template URL https://github.com/munk-sh/open-company/tree/main/companies/open-source-software

一个团队目录长什么样? What's Inside a Team Directory?

阅读完整 open-company/v0 规范 → Read the full open-company/v0 spec →

标准目录结构 Standard Directory Layout open-company/v0
open-source-software/
├── Companyfile.yaml        # 团队身份声明
├── AGENTS.md               # 全员共享的目标、分工边界与红线
├── projects/
│   └── daily-patrol/       # 团队级公共班次(如 21:00 晚间复盘)
└── products/
    └── open-compare/
        ├── Productfile.yaml # 绑定产品与代码仓库
        ├── AGENTS.md        # 产品功能优先级与验收底线
        └── projects/github/
            ├── guards/      # 零 Token 预检脚本(有事才唤醒 Agent)
            └── tasks/*.md   # 日常值班任务(时间表 + 职责说明)
open-source-software/
├── Companyfile.yaml        # Declares the team identity
├── AGENTS.md               # Shared goals, role boundaries & rules
├── projects/
│   └── daily-patrol/       # Team-wide shifts (e.g., 21:00 review)
└── products/
    └── open-compare/
        ├── Productfile.yaml # Binds product & git repository
        ├── AGENTS.md        # Product scope, priorities & QA bar
        └── projects/github/
            ├── guards/      # Zero-token preflight checks
            └── tasks/*.md   # Standing shifts (cron + instructions)
1

纯文本定义,跨服务商通用 Plain Files, Provider-Agnostic

目标、角色边界与定时排班全部写在 YAML 与 Markdown 文件里。无论是 Claude Code、Codex、Gemini CLI 还是 OpenCode,都能对着同一份目录协同工作。

Goals, role boundaries, and schedules live in plain YAML and Markdown. Claude Code, Codex, Gemini CLI, or OpenCode can coordinate off the exact same folder.

2

零成本脚本守门,有事才唤醒 Agent Zero-Token Guards Before Every Shift

高频巡检任务(如每 5 分钟盯一次 GitHub)先跑轻量 Node.js 脚本(guards/*.mjs),确认有新 Issue 或报错才消耗 Token 唤醒 Agent。

High-frequency shifts run a lightweight Node.js script (guards/*.mjs) first—waking an LLM agent only when new issues or failures appear.

3

一键导入,先预览再开启排班 One-Click Import, Safe by Default

导入时先预览所有文件与脚本;不含任何写死密钥,所有定时排班默认处于关闭状态,由你确认后再启动运转。

Preview all tasks and guards before writing; no hardcoded secrets are included, and all schedules stay off until you turn them on.