Show your setup: How are you using Batty?

[Zedmor]

We'd love to see how people are using Batty.

Share your setup:

• Template: Which team template are you using? (solo, simple, squad, custom?)
• Agents: Which coding agents are your engineers running? (Claude Code, Codex, Aider, mix?)
• Project type: What kind of project is the team working on?
• Team size: How many engineers in your config?
• Anything surprising? What worked better (or worse) than expected?

Screenshots of your tmux layout welcome.

[Zedmor]

Here's my current setup for a side project (Rust CLI tool):

Template: Custom — 1 architect + 2 engineers

Config:

roles:
  - name: architect
    role_type: architect
    agent: claude
    instances: 1
    talks_to: [manager]

  - name: engineer
    role_type: engineer
    agent: claude
    instances: 2
    use_worktrees: true
    talks_to: [manager]

Agents: Claude Code for both roles

What works well: The architect reviews the kanban board, breaks down tasks, and the two engineers work in parallel on separate git worktrees. No merge conflicts during active work — worktree isolation handles that. Tests gate everything before merge.

Surprise: Two engineers is the sweet spot for my repo size. Three caused more test conflicts than the parallelism was worth. Your mileage will vary depending on how decomposable your tasks are.

tmux layout: I run batty start --attach in a dedicated terminal and let it manage the panes. Ctrl-b [ to scroll through an agent's output when I want to see what it's doing.