trinity

AbilityaiApache-2.0活跃维护

自托管的 AI Agent 平台,统一接入 Claude Code、Codex、Gemini 等编码代理,帮 AI 原生团队做代理编排、运行时管理与可观测治理。

Self-hosted AI Agents Platform for AI Native companies. Claude Code, Codex, Gemini, OpenCode agents. Apache 2.0.

v1.0.0发布于 2026-10-20 19:43 UTC754star +8 / 7 天147fork同步于 2026-11-10 11:56 UTC

怎么上手

由 README 提炼,执行前请确认
curl -fsSL https://raw.githubusercontent.com/abilityai/trinity/main/install.sh | bash
硬件要求按 README 说明

README 未说明具体显存或 GPU 要求;部署需要 Docker 与 Docker Compose v2,可跑在自有服务器或 DigitalOcean、AWS、Vultr 云主机上。

有 Docker 镜像
下载:源码 zip·GitHub Releases(安装包)本站不镜像安装包

项目说明

由 README 自动翻译提炼

自托管的 AI 智能体平台,让 Claude Code、Codex、Gemini 等智能体带状态、权限和审计记录地跑在生产里

自托管的 AI Agent 平台,统一接入 Claude Code、Codex、Gemini 等编码代理,帮 AI 原生团队做代理编排、运行时管理与可观测治理。

核心能力

  • 把智能体按部门、角色和汇报线组织成公司结构
  • 用 gated skills 把不可逆操作冻结到人工审批收件箱
  • 以 git 历史、审计日志和人工门禁留下可追溯凭据
  • 支持 Claude Code、OpenAI Codex、Gemini CLI 多运行时
  • 内置调度、循环、智能体互调与故障恢复编排

容易踩的坑

需要先装好 Docker 和 Docker Compose v2;安装后要打开 http://localhost 认领管理员账号并在设置里连接模型;用 CLI 部署智能体需另装 trinity-cli。

内容由模型根据 README 生成,可能不完整或不准确,以官方文档为准。看原文 README

最近发版

5 个版本v1.0.0
  1. v1.0.0v1.0.0 — the Tandem release: agents take a seat on the team最新正式版2026-10-20 · 2026-10-20 19:43 UTC

    v1.0.0

    Released: 2026-10-20 Tag: v1.0.0  ·  Diff: v0.9.5...v1.0.0

    443 commits · 406 merged PRs · 2,485 files (+352k/−34k) · 217 public + 156 private-tracker issues · enterprise submodule 08cd4dd → 982735f · release candidates rc1–rc4 cut from dev along the way; the release is cut from the dev tip after rc4.

    Freeze plan and coherence review: v1.0.0-freeze-plan.md. User-facing summary: What's New in v1.0.0.

    Highlights

    1.0 is built around one story: an agent takes a seat on the team. It has a named role, serves named people, works inside projects, is bounded by approvals the platform enforces, is measured against business numbers, and reaches people through one Inbox.

    • Agents are assigned to people. An admin names who an agent serves (its primary), who approves for it, who collaborates and who views; the agent knows this on every run. One companion can serve several seats, an agent can hold a seat itself, and every assignment change is audited. Workspace shows each person a role card with the role, objectives and metric freshness (ent#500, ent#527, ent#810, ent#811, ent#814, ent#817, ent#676).
    • One Inbox, platform-native approvals. Workspace opens on an Inbox (Action / Unread / All, reading pane) across every agent. Agents ask over MCP; an ask can be answered with an option, "something else", discussed in a linked chat, or dismissed, and stays attached to the chat it was raised in. Asks are addressed to a role, never a named person (ent#610 in part, ent#611, ent#606, ent#816, ent#748, ent#747, ent#738, #2915, #3242, #3243, #3247).
    • Gated skills. Mark a skill requires approval by role X: the approval reaches a person who can open the agent before the agent ever sees the request, an approved run executes once with exactly the approved input, and an in-container hook refuses the bypass lane. The requester is told how it ended (ent#751–#756, ent#844, ent#881, #3653, #3654).
    • Self-change grants and agent reach. An agent changes its own skills, schedules, instructions, other agents or projects only with an admin-granted toggle. An agent key reaches only itself, the agents it may call and the agents it spawned — on fleet routes too; an edge exposes the skills the target declares, and library skills need a per-skill grant (ent#164, ent#756, ent#662).
    • Projects. A project is a platform record with members, visibility, a Continue card, Tasks / Log / Files tabs and a Steward agent; agents work on projects over MCP (ent#661, ent#896, ent#588).
    • Business metrics and objectives. Templates declare metrics; agents push points over MCP (batched, idempotent, restatements reported); dashboards and the role card show target vs actual with freshness, and a stale metric says so (ent#477–#479, ent#666, ent#812, ent#727, ent#729–#731, ent#671).
    • Suggestions and readiness. "Things you can ask" and "Suggested for you"; a companion stays in calibrating (no proactive brief) until its owner marks it ready (ent#465, ent#637, ent#663, ent#689).
    • One Settings home per agent and a restored agent header — in-place name and avatar, funding switcher, live sparklines, 7-day spend, GitHub line, capacity bars; a two-pane New agent dialog (ent#887, ent#888, ent#890, ent#891, ent#353, ent#950, ent#955, #3792).
    • Git sync that pulls. Auto-syncing agents fetch and rebase on a heartbeat; conflicts are recorded; divergence over 24h turns red on the agent card and fleet health (ent#703–#708, #3010, #3011).
    • Workspace-only users. Platform role user signs in to Workspace only; sharing an agent no longer creates an operator login (ent#837).
    • Hosting. Hosted compose ships a bundled PostgreSQL; AWS one-click (AMI + CloudFormation) and a Vultr Marketplace listing join DigitalOce
  2. v1.0.0-rc3v1.0.0-rc3 — release candidatepre-release2026-10-13 · 2026-10-13 12:22 UTC
    查看更新说明

    Release candidate for v1.0.0, cut from dev at 15e3502.

    Published to GHCR as v1.0.0-rc3 and 1.0.0-rc3. latest is deliberately not moved.

    Not a release: no issues are closed by this tag and main is untouched. The full cut runs the normal /release path when the release floor is met.

  3. v1.0.0-rc2v1.0.0-rc2 — release candidatepre-release2026-10-10 · 2026-10-10 15:26 UTC
    查看更新说明

    Release candidate for v1.0.0, cut from dev at 96f88f9.

    Published to GHCR as v1.0.0-rc2 and 1.0.0-rc2. latest is deliberately not moved.

    Not a release: no issues are closed by this tag and main is untouched. The full cut runs the normal /release path when the release floor is met.

  4. v1.0.0-rc1v1.0.0-rc1 — release candidatepre-release2026-10-09 · 2026-10-09 11:28 UTC
    查看更新说明

    Release candidate for v1.0.0, cut from dev at c90c711.

    Published to GHCR as v1.0.0-rc1 and 1.0.0-rc1. latest is deliberately not moved.

    Not a release: no issues are closed by this tag and main is untouched. This is the build for the 1.0 testing matrix (Abilityai/trinity-enterprise#847, Rule 2). The full cut runs the normal /release path when the release floor is met.

  5. v1.0.0-aws.2v1.0.0-aws.2 — AWS Marketplace AMI candidatepre-release2026-10-05 · 2026-10-05 13:02 UTC
    查看更新说明

    Pre-release for the AWS Marketplace AMI (#3004), cut from dev at 1e77bf3. Supersedes v1.0.0-aws.1.

    Adds the AMI cleanup-check fix (#3182) and the container CPU cap at the host's CPU count (#3184), so the system agent starts on a 2-vCPU instance.

    Published to GHCR as v1.0.0-aws.2 and 1.0.0-aws.2. latest is deliberately not moved.

    Not a release: no issues are closed by this tag and main is untouched.

用户点评

登录用户的真实使用记录,可按版本和硬件筛选
共 0 条

    还没有人点评。第一个说出真实体验的人最有价值。

    README 原文

    未翻译

    Trinity is the operating system for the AI-native company - that you own. Compounding intelligence your company owns.

    Persistent agents that keep their memory, share what they learn, and ship their own improvements - governed by receipts: git history, audit logs, human gates. Open source and self-hosted: your infrastructure, your data, your compounding intelligence - not rented from a vendor.

    Your coding agent writes the agent. Trinity runs it in production - with state, permissions and receipts. It runs agents on Claude Code, OpenAI Codex or Gemini CLI, organised into departments with roles and reporting lines, with Cornelius, our cognitive architecture for making the work compound, built in.

    Apache 2.0 · independently pentested, UnderDefense Grade A · we run our own company on it.

    Find this useful? ⭐ Star the repo - it's how other people find Trinity.

    [!NOTE] 📦 Trinity 1.0 is the release where Trinity runs a company, not a console:

    • a role for every agent, with objectives tied to a number the company actually tracks
    • approvals in your Inbox - anything irreversible waits for a person, and the answer wakes the agent
    • gated skills, approvers by role, skill sets you assign as one unit
    • Projects with tasks, a log and a steward (Enterprise)
    • rate the work, reply in-thread, one Skills tab, agents that pull their own repo

    What's new → · Release notes → · Previous: v0.9.5

    See it move

    One task, end to end: a schedule fires, the agent works in its container, reaches an action it may not take alone, asks the right person in their Inbox, and finishes with a commit, an audit row and a metric point.

    Watch more

    More in the workshop archive. Live and free, every Thursday.

    Organised the way your company is

    Agents live in departments, hold a role, and report along lines you draw. A role is a seat on record: who the agent serves, what it is for, and which objective it moves. Objectives bind to declared metrics, so "is it working" is a number with a date on it, not an impression. Nothing crosses a line you have not granted: an agent can call only the agents it has an edge to, and may change its own shape only with a grant.

    # template.yaml - the agent declares the number it moves ...
    metrics:
      - name: close_rate
        type: gauge
        unit: percent
        direction: up_good
    
    # ... and the company's canon declares the objective that binds it to a seat
    id: q4-close-rate
    statement: Lift close rate to 35% by the end of Q4.
    owner: role:revenue-lead
    metrics:
      - { name: close_rate, direction: up, target: 35, by: 2026-12-31 }
    

    Anything irreversible waits for a person

    Mark a skill as gated and name who approves: the primary contact, or a role. From then on any request that names that skill - from a person, another agent, a schedule or a channel - is frozen before the agent sees it. The approver gets one card in their Inbox: the agent, the skill, the input, who asked. Approve runs it once; Discuss opens the thread; Reject ends it. The agent that asked is told how it ended. Guardrails bound agents by what they hold, not what they are told: hooks an agent cannot switch off, cost limits, loop budgets, a kill switch for outbound calls.

    # the same gate, over MCP
    set_skill_gate(agent="proposal-writer", skill="send-proposal", approver="role:revenue-lead")
    

    Every agent has a history you can read

    An agent is a git repository you own. Create it from github:owner/repo, let it commit its own work, pull it back, reset it to upstream. Every tool call lands in an append-only audit log; compliance mode adds an opt-in SHA-256 hash chain with verification. Every run is a row in the execution ledger with its trigger, cost and outcome, and you can search across all of them.

    $ git log --oneline agents/proposal-writer
    a1f3c9e Q4 proposal v3 - pricing from the October sheet
    8e21bb0 Q4 proposal v2 - reviewed by revenue-lead
    4d07a1c Lessons from the September proposals (kept by Cornelius)
    

    One Workspace. Every agent.

    A chat per topic, a conversation rail, a live Work card while the agent runs, deliverables you can rate, files by drag-and-drop, a canvas each agent can draw on, and voice over the current chat. The same agents answer in Slack, Telegram and WhatsApp, on a phone call, over a public chat link, over MCP and from the CLI. Projects (Enterprise) give a cross-agent piece of work its tasks, its log, its health and a steward that keeps it moving.

    The work compounds

    Cornelius is our cognitive architecture for making the work compound. It turns what agents do into knowledge the company keeps: lessons from a run become notes, notes become instructions, instructions become the next agent's starting point - all as files in repositories you own, without retraining a model. Swap the model and what the company has built up stays.

    Inside your perimeter. On any model.

    Three runtimes - Claude Code, OpenAI Codex, Gemini CLI - and a model picker per chat. Each agent is its own container on a network the data plane cannot see. Credentials are encrypted at rest and scrubbed from the runtime; no telemetry leaves unless you opt in. Export every agent, every log and every credential, and walk away whenever you choose.

    Quick start

    One line, on a machine you control (Docker and Docker Compose v2):

    curl -fsSL https://raw.githubusercontent.com/abilityai/trinity/main/install.sh | bash
    

    Then open http://localhost, claim the admin account, and connect a model in the setup overlay. Prefer to read what runs first: git clone https://github.com/abilityai/trinity && cd trinity && ./scripts/deploy/start.sh (--hosted pulls the prebuilt images; --unattended prints a generated admin password).

    One click, in your own cloud account - the image brings itself up behind HTTPS in about ninety seconds:

    Deploy to DigitalOcean Launch on AWS Marketplace

    Let your agent install it. Tell Claude Code, Codex or any capable coding agent: "Install Trinity on my computer. Follow the runbook at https://raw.githubusercontent.com/abilityai/trinity/main/docs/AGENT_INSTALL_GUIDE.md."

    Then deploy your first agent from the coding agent you already use:

    /plugin marketplace add abilityai/abilities      # Claude Code; Codex and Gemini CLI via the CLI below
    /plugin install trinity@abilityai
    /trinity:connect                                 # instance URL + email code → MCP key
    /trinity:onboard                                 # from any agent directory: check, package, deploy, start
    

    Or from a terminal: pip install trinity-cli && trinity init && trinity deploy . (CLI reference). Or in the browser: Create Agent → a template, a GitHub repo, or a system manifest.

    An AI agent reading this? AGENTS.md is your entry point: exact commands, key facts and a verification step for every path.

    Up and running? ⭐ Star the repo. Hit a rough edge? File an issue - we read them.

    Open source is the whole platform. Enterprise adds governance.

    Open source - Apache 2.0, freeEnterprise adds
    Agent platform - fleet, Workspace, chat, voice, canvas, web terminalUser & org management - invite, deactivate, activity per user
    Multi-runtime - Claude Code, Gemini CLI, OpenAI CodexSingle sign-on (OIDC) - Okta, Entra ID, Google Workspace
    Orchestration - schedules, loops, agent-to-agent calls, fan-out, recoveryTwo-factor authentication - authenticator apps, recovery codes, policy per role
    Roles, objectives, gates - role per agent, gated skills, approvers, InboxAdvanced RBAC - teams, granular roles, people-per-agent assignments
    System agent - built-in ops agent: health, restarts, schedules, costsProjects - tasks, log, health, steward across agents
    Channels & APIs - Slack, Telegram, WhatsApp, voice calls, MCP, REST, CLIFleet permissions matrix - one view of which agent may call which
    Git-native agent state - GitHub sync, commit history, reset to upstreamCompliance suite - audit dashboard, SIEM export, auditor export, retention
    Skills library & marketplace - tag-pinned library, skill sets, pluginsCredential vault - named encrypted secrets, deny-by-default grants
    Security core - encrypted credentials, hardened containers, audit logA2A management - exposure control, inbound allowlist, paid calls
    Guardrails & cost controls - hooks agents cannot disable, quotas, loop budgetsCross-model validation - a second model referees a run
    Tamper-evident audit log - opt-in SHA-256 hash chainEphemeral agents - short-lived agents with a lifetime and a budget
    Self-hosted - your hardware, no telemetry unless you opt inLicence management - offline-verified, air-gap friendly

    Open core: Enterprise includes everything in open source. The private modules live in optional submodules; cloning without them needs no credentials (docs/ENTERPRISE.md). Get enterprise access →

    Build on it

    A system from one manifest - departments, agents, permissions and schedules, deployed together:

    name: revenue
    agents:
      revenue-lead:
        template: github:abilityai/agent-corbin
        schedules: [{ name: weekly-pipeline, cron: "0 9 * * 1", message: "/pipeline-review" }]
      proposal-writer:
        template: github:abilityai/agent-ruby
        folders: { expose: true, consume: true }
    permissions:
      preset: full-mesh
    

    deploy_system over MCP, or POST /api/systems/deploy. Multi-Agent System Guide →

    Templates and import - start from the template registry, any GitHub repo, or a local directory. Skills library - a tag-pinned community library (trinity-skills) plus your own repos; assign a skill or a set to any agent, re-injected fleet-wide when the library moves. Plugins - the abilities marketplace covers scaffold, develop, deploy and iterate from Claude Code:

    PluginWhat it does
    create-agentScaffold a Trinity-compatible agent (custom, website, clone, review, adjust)
    agent-devPlaybooks, memory systems, git sync, backlog workflow, pipelines, work loops
    trinityconnect, onboard, sync, loop, create-dashboard, deploy-new-instance

    MCP - every Trinity instance is an MCP server (http://<instance>:8080/mcp, agent- and user-scoped keys) for agents, schedules, executions, projects, metrics, canvases, skills and more. No instance yet? npx -y trinity-docs-mcp answers questions about Trinity from any MCP client. MCP reference →

    Architecture

    One host runs the control plane - a Vue frontend, a FastAPI backend, the MCP server, the scheduler, Redis for secrets and locks, and PostgreSQL for data - on a network the agents cannot reach. Each agent is its own container on a second network, with its repo, its credentials and its schedule. Operators reach the UI and API over your VPN; public users and channel webhooks reach only routes you publish through an outbound tunnel, so the host opens no inbound ports. Logs ship through Vector; metrics export over OpenTelemetry. Ports, services and profiles: Deployment Guide · docs/memory/architecture.md.

    Database. Trinity 1.0 runs on PostgreSQL. The bundled container comes up with the stack; point DATABASE_URL at your own instance to use one you already run. SQLite support ended on 2026-09-01; an older instance migrates with the Trinity Ops Agent's /migrate-to-postgres.

    We run our company on it

    Ability AI runs on Trinity: 41 agents across product, engineering, docs, operations and the company brain, as of 2026-10-14. Every number in this README is dated for that reason.

    Security - Grade A (Excellent) in an independent web application penetration test by UnderDefense, April 2026; all critical and high findings remediated. Attestation letter → · SECURITY.md

    Documentation

    Community & support

    License

    Apache License 2.0 - free for any use, commercial included, with an explicit patent grant. Enterprise modules are under a separate commercial licence. See CONTRIBUTING.md to contribute; development setup lives there now.