86625df15d
Key Decision #11 renamed from "Beads as Swarm State" to "Work is a Stream (No Swarm IDs)". Work flows through the system as a continuous stream: - The epic IS the grouping (no separate swarm ID) - The merge queue IS the coordination (no batch boundaries) - Workers process issues independently (add/remove anytime) - Dependencies provide sequencing (multi-wave emerges naturally) Updated sections: - Introduction: Added key insight about stream model - Work Dispatch: Renamed from "Swarm Dispatch", updated diagram - Multi-Wave Work Processing: Renamed from "Multi-Wave Swarms" - Key Decision #11: Full rewrite explaining stream model - Various terminology updates throughout This aligns with the vision that Gas Town manages work as a stream, not as discrete batches requiring explicit start/end boundaries. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Gastown (Go)
Go port of Gas Town - a multi-agent workspace manager.
Status
Work in Progress - This is the Go rewrite of the Python gastown tool.
See the Python version for current functionality.
Goals
- Single binary installation (
gt) - Self-diagnosing (
gt doctor) - Federation support (coordinate agents across VMs)
- Performance improvements over Python version
Development
# Build
go build -o gt ./cmd/gt
# Run
./gt --help
Related
- gastown-py - Python version (current)
- beads - Issue tracking for agents