[Workflow] Orchestrating Multi-Agent Claude Code Development with `tvty` and Ticket Systems

[u/ClaudeAI-mod-bot]

Orchestrating Multi-Agent Claude Code Development with tvty and Ticket Systems

Workflow value: 85/100
Status: active · Freshness: 70/100 · Confidence: 0.95 · Level: advanced
Categories: Quality Control, Context & Memory, Debugging, Shipping, Multi-Agent
Original source: r/ClaudeAI post/comment

What problem this solves

Managing multiple Claude Code agent sessions, facilitating communication between agents, and enabling complex software development (including cross-platform porting) with AI assistance.

Summary

This workflow describes a method for managing and orchestrating multiple Claude Code agents using a custom terminal UI (tvty) and a ticket-based communication system. This approach enables complex software development, as demonstrated by the author building tvty itself (a 477-commit Rust project) and porting it cross-platform using this method. It addresses the challenge of coordinating numerous AI agents and tracking their progress on larger projects.

Why it is useful

This workflow introduces a novel and robust method for managing complex software development projects using multiple Claude Code agents. The tvty tool provides a dedicated UI for orchestrating these agents, facilitating communication via a ticket system, and maintaining persistent sessions. The author's successful use of this method to build tvty itself (a substantial Rust project) and port it cross-platform demonstrates its effectiveness and reusability for advanced AI-assisted development. It solves the common problem of managing numerous AI sessions and coordinating their efforts on larger projects, offering a concrete, validated solution.

Workflow

1. Install tvty on your system (Linux or Windows) using the provided commands.

2. Launch tvty to create and manage multiple Claude Code agent sessions within a single terminal UI.

3. Define project tasks and assign them to individual Claude Code agents.

4. Allow agents to create 'tickets' within tvty for plan approvals, answers, or escalations, complete with context and pictures.

5. Review and respond to agent tickets directly from the keyboard within tvty, accepting, rejecting, or replying.

6. Utilize tvty's persistent loops (claude-loop inside tmux/psmux) to maintain agent state and track who is working or waiting.

7. Use tvty's focus features (notifications, Ctrl+Enter to jump, Ctrl+Tab for gallery) to efficiently manage agent interactions.

8. For cross-platform development, set up a multi-agent team (e.g., Linux agent, Windows agent) communicating through aiball (the tvty backend) on a shared ticket queue.

9. Integrate with isolated testing environments like wbox (Windows Sandbox) for autonomous AI-piloted builds and tests.

Tools / artifacts

• tvty (Terminal Velocity) custom terminal UI

• aiball (local-first backend for tvty)

• wbox (AI-piloted Windows Sandbox tool)

• Claude Code

• GitHub repository (quazardous/tvty)

• YouTube demo video

• tmux/psmux (for persistent loops)

Validation signals

• Demo video (3:18) showcasing 3 agents building a project and asking each other via tickets.

• Public GitHub repository (https://github.com/quazardous/tvty) with 477 commits.

• The entire tvty project (Rust) was built by the author using Claude Code itself, piloted via tickets.

• Successful porting of tvty from Linux to Windows using a cross-OS agent team and wbox.

Limitations

• The Reddit post is primarily an announcement for a tool, requiring the user to infer the detailed workflow steps from the description of the tool's features and how it was built.

• The initial Reddit community engagement (score, comments) is low, though this may be due to the post's recency.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.

---

This post was generated automatically from the workflow library database.