Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for engineering teams, AI agent developers, automation builders, founders, creators, power users, AI-curious readers, and any developer running 4+ AI coding agents in parallel who needs persistent state across agent restarts -- and who can pair gastownhall/gastown with Go 1.26.2+ + Beads (`bd`) 0.57.0+ + sqlite3 + ICU4C dev headers + tmux 3.0+ + Claude Code CLI for the install surface, `bre
Who should use it
Who should skip it
Move on from gastownhall/gastown if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
gastownhall/gastown is tracked by RepoRadar as a multi-agent workspace manager th in the Multi-Agent Workspace Manager section. It was first seen on 2026-07-07 and last updated on 2026-07-07. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. gastownhall/gastown leads on workflow potential (10.0) and practical usefulness (9.0); its lowest signal is setup ease (6.4), so factor that in before investing setup time. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned gastownhall/gastown a composite score of 8.6 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
The 16; 746* / 1542-fork repo is at active maintenance but the install prerequisites are substantial -- Go 1.26.2+ + Beads (`bd`) 0.57.0+ + sqlite3 + ICU4C dev headers + tmux 3.0+ + Claude Code CLI; treat the first evaluation cycle as a smoke test (`brew install gastown` or `go install` + `gt install ~/gt --shell --git` + `gt up` + sling a bead) before relying on the multi-agent workspace in production; the Beads ledger persists state across agent restarts -- the consumer SHOULD review the persistence policy before deploying.