Concepts and architecture
Gas Town organizes multi-agent work into a hierarchy of workspace objects and workflows.
Architecture overview
Key roles
| Role | Description | Primary interface |
|---|---|---|
| Mayor | AI coordinator | gt mayor attach |
| Human (you) | Crew member | Your crew directory |
| Polecat | Worker agent | Spawned by the Mayor |
| Hook | Persistent storage | Git worktree |
| Convoy | Work tracker | gt convoy commands |
Beads integration
Gas Town stores work state as Beads (a git-backed issue tracker). Beads are referenced by IDs with a prefix and 5-character alphanumeric suffix, like gt-abc12 or hq-x7k2m. You can pass those IDs to commands like gt sling or gt convoy to assign or track work.
Propulsion principle
Hooks act as a propulsion mechanism:
- Persistent state — work survives agent restarts.
- Version control — changes are tracked in git.
- Rollback capability — revert to any previous state.
- Multi-agent coordination — shared through git.