trellis-channel

Coordinate multi-agent collaboration through Trellis channel event logs and spawned workers.

Updated Sep 5, 2026
One-click install
npx skills add https://github.com/jiozhaoyue/ST-BgLoader --skill trellis-channel-jiozhaoyue
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-channel
Source: https://github.com/jiozhaoyue/ST-BgLoader/tree/main/.cursor/skills/trellis-channel
Command: npx skills add https://github.com/jiozhaoyue/ST-BgLoader --skill trellis-channel-jiozhaoyue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Coordinating multiple AI agents (Claude, Codex) on shared work requires a durable communication layer; ad-hoc prompting loses history, truncates progress, and makes worker supervision unreliable. This Skill provides the operational knowledge to use the trellis channel CLI for durable event-log messaging, worker spawning, forum channels, and debugging. ## Core Features & Use Cases - Multi-Agent Collaboration: Spawn Claude or Codex workers as peer processes, route messages with --to, and wait on system done/turn_finished events instead of unreliable custom tags. - Forum Channels: Create durable --type forum boards with threads, context entries, labels, and summaries for issue tracking, design feedback, and internal changelogs. - Worker Lifecycle & Debugging: Soft-interrupt mid-turn work, kill and resume sessions, diagnose stalled workers via raw event inspection and worker logs, and enforce OOM guards. - Use Case: A dispatcher agent spawns a check reviewer worker with injected task files, sends a review brief via stdin, waits on --kind done with a timeout, then reads the final message — all auditable through the channel event log. ## Quick Start Ask the agent to create a Trellis channel, spawn a Codex worker with your task files injected, send it a brief, and wait for its done event.

Frequently Asked Questions about trellis-channel

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I spawn a Claude or Codex worker agent with Trellis channel?▼

Use `trellis channel spawn <channel> --provider claude|codex --as <name>` after creating the channel. Inject context with repeatable `--file` or `--jsonl` manifest flags, then wake the worker with `send --to <name>`.

How do I wait for a Trellis worker to finish its task?▼

Use `trellis channel wait <channel> --as <you> --from <worker> --kind done,turn_finished --timeout 30m`. Rely on system-emitted `done` events, not custom tags, since workers often fail to emit user-defined signals.

What is the difference between Trellis chat and forum channels?▼

Chat channels are flat message timelines, while forum channels (`--type forum`) organize durable threads with titles, labels, statuses, and context entries. The type is fixed at creation and forum channels must be read via `forum`, `thread`, and `messages --thread` subcommands.

Why is my Trellis channel worker alive but producing no output?▼

Check the supervisor and worker PIDs, tail the `<worker>.log` file, and inspect raw events with `messages --raw --last 50`. Common causes include provider cold starts, blocking MCP servers, or hung tool subprocesses.

Can I interrupt a running Trellis worker without killing it?▼

Yes, use `trellis channel interrupt <channel> --as <caller> --to <worker>` with a replacement instruction via stdin. For runaway workers, use `kill` followed by `spawn --resume` with the saved session id.

When should I not use Trellis channel for agent collaboration?▼

Skip it for one-off static reviews where a markdown file and prompt suffice, and do not use it as a substitute for normal tool calls or long-term memory retrieval. Use `trellis mem` for session history search instead.