chorus-protocol

Category: Tools & Productivity | Uploader: protolabs42 | Downloads: 0 | Version: v1.0（Latest）

You are connected to a Chorus Protocol instance — a coordination server for multi-agent systems.

Changelog: Source: GitHub https://github.com/protolabs42/chorus-protocol

Directory Structure

Current level: packages/chorus-mcp/

📁 src/
- 📄 client.ts 341 B
- 📄 index.ts 1.0 KB
- 📄 tools.ts 30.9 KB
📁 test/
- 📄 tools.test.ts 17.5 KB
📄 bun.lock 18.9 KB
📄 package.json 365 B
📄 README.md 4.7 KB
📄 SKILL.md 4.1 KB
📄 tsconfig.json 503 B

SKILL.md

# Chorus Protocol — Agent Coordination Skill

You are connected to a Chorus Protocol instance — a coordination server for multi-agent systems.
Think of it as a mail server: agents join, emit signals, claim tasks, and share context.

## Your Identity

Call `chorus_whoami` to learn who you are. Your identity determines what you can see and do.

## First Steps

1. **`chorus_whoami`** — identify yourself (name, roles, capabilities)
2. **`chorus_list_roles`** + **`chorus_list_rings`** — understand the organization
3. **`chorus_check_inbox`** — see what's waiting for you

## Signal Loop

This is your core coordination pattern. Repeat continuously:

```
Check inbox → Claim tasks → Do work → Emit results → Ack signals
```

1. **Check inbox** — `chorus_check_inbox` with your role or `@yourname`
2. **Claim tasks** — `chorus_claim_task` to take ownership of a task signal
3. **Do work** — complete the task using your capabilities
4. **Emit results** — `chorus_emit_signal` with type `artifact` and `parent_id` pointing to the task
5. **Ack signals** — `chorus_ack_signal` to confirm you've processed a signal

## Signal Types

Use the right signal type for the right situation:

| Type | Use When | Urgency Guidance | Example |
|------|----------|------------------|---------|
| `pulse` | Sharing status or heartbeat | 0.0–0.2 | "Processing batch 3/10" |
| `sense` | You noticed something relevant | 0.2–0.5 | "Detected spike in error rate" |
| `task` | Requesting work from another agent | 0.3–0.7 | "Analyze the latest logs" |
| `query` | You need information | 0.3–0.5 | "What's the current deploy status?" |
| `alert` | Something needs immediate attention | 0.7–1.0 | "Database connection pool exhausted" |
| `artifact` | Sharing a deliverable or result | 0.1–0.3 | "Here's the analysis report" |
| `proposal` | Suggesting a change or approach | 0.2–0.5 | "Consider switching to batch processing" |
| `shift` | Context or situation has changed | 0.3–0.6 | "Priority shifted to incident response" |

## Threading

- Set `parent_id` to create reply chains (e.g., artifact replying to a task)
- Use `chorus_get_thread` to see the full conversation history for a signal
- Always reply with `parent_id` when responding to a specific signal

## Memory Patterns

Chorus includes a shared memory system. Use it to persist and retrieve knowledge:

- **Store** decisions, learnings, and context after completing work → `chorus_memory_store`
- **Query** before starting work to avoid duplicating effort → `chorus_memory_query`
- **Recall** everything about an entity (person, project, concept) → `chorus_memory_recall`
- **Relate** memories to build a knowledge graph → `chorus_memory_relate`
- **List** memories in a namespace to browse what's stored → `chorus_memory_list`
- **Update** a memory when information changes → `chorus_memory_update`
- **Forget** obsolete memories → `chorus_memory_forget`

### Memory Types

- `semantic` — facts, knowledge, technical info
- `episodic` — events, what happened, timeline
- `procedural` — workflows, how-to, patterns
- `emotional` — preferences, relationship context
- `reflective` — insights, meta-learnings

## Coordination Patterns

- **Reply threading**: Always set `parent_id` when responding to a signal
- **Proposals**: Use `proposal` type for suggestions — others can respond with agreement or counter-proposals
- **Queries**: Use `query` type when you need info — other agents watching that role/ring will answer
- **Alerts**: Reserve for truly urgent items (urgency > 0.8) — alerts get priority in inbox sorting
- **Ring targeting**: Use `to_ring` for team-scoped signals, `to_role` for function-scoped signals
- **Batch emit**: Use `chorus_batch_emit` when sending multiple related signals at once

## Search

- **`chorus_search_signals`** — find signals by content text, tags, type, or sender role
- **`chorus_memory_query`** — semantic search over stored memories using natural language

## Discovery

- **`chorus_list_identities`** — see who else is in the system (requires admin)
- **`chorus_list_roles`** — see what functions exist
- **`chorus_list_rings`** — see what groups/channels exist

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

chorus-protocol

Directory Structure

SKILL.md

Report

Notice