Trinity AI工作流

Install listener dependencies

brew install websocat jq

3. Build the base agent image

./scripts/deploy/build-base-image.sh

Phase B — Build & deploy agents from Claude Code

Most of the Trinity workflow lives in the abilities plugin marketplace — Claude Code plugins covering the full agent lifecycle: scaffold, develop, deploy, iterate. You need the instance from Phase A (localhost or remote) and Claude Code.

```bash

1. Add the marketplace and install the core plugins (one-time)

/plugin marketplace add abilityai/abilities /plugin install trinity@abilityai /plugin install create-agent@abilityai

4. Deploy it to Trinity

/trinity:onboard

→ Compatibility check, creates the Trinity files, deploys + starts the container

Other ways to deploy

Trinity CLI — terminal-first alternative to the plugin workflow:

pip install trinity-cli                     # or: brew install abilityai/tap/trinity-cli

trinity init                                # connect: instance URL + email code → JWT + MCP key
cd my-agent/ && trinity deploy .            # package, upload, create + start the agent
trinity chat my-agent "Hello, what can you do?"
trinity logs my-agent                       # container logs
trinity health fleet                        # fleet overview

Redeploys (trinity deploy . again), multi-instance profiles, and the full command reference: CLI documentation.

Web UI — open the Trinity web UI → Create Agent → pick a template (blank, built-in, or github:org/repo@branch) → configure credentials → start chatting.

Multi-Agent System — define a fleet in one YAML manifest and deploy via MCP (mcp__trinity__deploy_system) or the REST API. See Multi-Agent Systems below.

Add the marketplace (one-time), then install the plugins you need

/plugin marketplace add abilityai/abilities /plugin install trinity@abilityai /plugin install create-agent@abilityai ```

See the abilities repository for full plugin documentation and skill references.

Rebuild after changes

docker compose build backend docker compose up -d backend ```

Quick Start

Two phases: stand up an instance (Phase A), then build and deploy agents to it from Claude Code (Phase B).

Design Guides

2. Configure environment

cp .env.example .env

Edit .env - at minimum set:

Set your MCP API key (from Settings → API Keys)

export TRINITY_API_KEY="trinity_mcp_xxx"

Configuration

Environment Variables

See .env.example for the complete list.

→ MCP API key auto-provisioned, .mcp.json written

Via REST API

curl -X POST http://localhost:8000/api/systems/deploy \ -H "Content-Type: application/json" \ -d '{"manifest": "...", "dry_run": false}' ```

See the Multi-Agent System Guide for architecture patterns and best practices.

MCP Integration

Trinity includes an MCP server for external orchestration of agents:

{
  "mcpServers": {
    "trinity": {
      "type": "streamable-http",
      "url": "http://localhost:8080/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}