HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
gastownhall
gastown
Go2026–2026
gastownhall / gastown

gastown

Gas Town - multi-agent workspace manager

25Distinct people
26Mentions
0Explicit recommenders
18.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Gas Town - multi-agent workspace manager

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 7:37:51 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month26 dated mentions

Observed mentions: 2026-01-02 03:41:51 UTC to 2026-09-02 14:12:26 UTC.

0510152026-01-01 00:00:00 UTC to 2026-02-01 00:00:00 UTC (exclusive): 14 mentions; 4 submissions, 10 commentsJan 20262026-02-01 00:00:00 UTC to 2026-03-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-03-01 00:00:00 UTC to 2026-04-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2026-04-01 00:00:00 UTC to 2026-05-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2026-05-01 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsMay 20262026-06-01 00:00:00 UTC to 2026-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-01 00:00:00 UTC to 2026-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-01 00:00:00 UTC to 2026-09-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2026-09-01 00:00:00 UTC to 2026-10-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsSep 2026

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jan 20262026-01-01 00:00:00 UTC2026-02-01 00:00:00 UTC14410
Feb 20262026-02-01 00:00:00 UTC2026-03-01 00:00:00 UTC101
Mar 20262026-03-01 00:00:00 UTC2026-04-01 00:00:00 UTC202
Apr 20262026-04-01 00:00:00 UTC2026-05-01 00:00:00 UTC413
May 20262026-05-01 00:00:00 UTC2026-06-01 00:00:00 UTC202
Jun 20262026-06-01 00:00:00 UTC2026-07-01 00:00:00 UTC000
Jul 20262026-07-01 00:00:00 UTC2026-08-01 00:00:00 UTC000
Aug 20262026-08-01 00:00:00 UTC2026-09-01 00:00:00 UTC202
Sep 20262026-09-01 00:00:00 UTC2026-10-01 00:00:00 UTC101

What Hacker News says

14 sources
This smells like Claude's own version of Gas Town by Steve Yegge. Probably more constrained and less of a crazy bull ride. But seems we are heading this way, from initially: - a Senior Dev pairing with Junior Dev (2024/25) - a tech lead/architect in charge of several Developers (2025) - a Product Owner delegating to development teams (2026?) --- - https://github.com/steveyegge/gastown - https://steve-yegge.medium.com/welcome-to-gas-town-4f25ee16d...
In Claude Code's new hidden feature: Swarms
Originally I thought that Gas Town was some form of high level satire like GOODY-2 but it seems that some of you people have actually lost the plot. Ralph loops are also stupid because they don't make use of kv cache properly. --- https://github.com/steveyegge/gastown/issues/503 Problem: Every gt command runs bd version to verify the minimum beads version requirement. Under high concurrency (17+ agent sessions), this check times out and blocks gt commands from running. Impact: With 17+ concurrent sessions each running gt commands: - Each gt command spawns bd version - Each bd version spawns 5-7 git processes - This creates 85-120+ git processes competing for resources - The 2-second timeout in gt is exceeded - gt commands fail with "bd version check timed out"
In Gas Town's agent patterns, design bottlenecks, and vibecoding at scale
My mental model is that ai coding tools are machines that can take a set of constraints and turn them into a piece of code. The better you get at having it give its self those constraints accurately, the higher level task you can focus on. Eg compiler errors, unit tests, mcp, etc. Ive heard of these; but havent tried them yet. https://github.com/hmans/beans https://github.com/steveyegge/gastown Right now i spent a lot of “back pressure” on fitting the scope of the task into something that will fit in one context window (ie the useful computation, not the raw token count). I suspect we will see a large breakthrough when someone finally figures out a good system for having the llm do this.
In Provide agents with automated feedback
Hey HN, I built this after getting frustrated with Claude Code forgetting everything between sessions. *The problem:* Every new session, AI has no memory. You end up re-explaining architecture, past decisions, why you chose X over Y. Gets old fast. *What CodeSyncer does:* Records AI decisions as comment tags directly in your code. ```typescript // @codesyncer-decision [2026-01-15] Chose sync over async (UX feedback) // @codesyncer-inference Min $1 (Stripe policy) async function processPayment(amount: number) { ... } ``` Next session, AI reads the code and instantly knows the context. No re-explaining. *Setup:* ```bash npx codesyncer init npx codesyncer watch ``` *Why not just use CLAUDE.md?* CLAUDE.md is great for rules ("use TypeScript strict mode"). But it doesn't capture why specific code was written a certain way. CodeSyncer stores th
Read the rest
at context where it belongs—in the code itself. *Similar project:* Steve Yegge's Gas Town (https://github.com/steveyegge/gastown) solves this for teams with 20-30 agents. CodeSyncer is the solo developer version—simpler, 5-min setup. Would love feedback, especially: - Does this solve a real problem for you? - What's missing? - Any concerns with the approach?
In Show HN: CodeSyncer – Store AI coding context in code comments
> What they all seem to be just glossing over is how the project unfolded: without human intervention, using computers, in an exceptionally accelerated time frame, working 24hr/day. Correct, but Gas Town [1] already happened and what's more _actually worked_, so this experiment is both useless (because it doesn't demonstrate working software) _and_ derivative (because we've already seen that you can set up a project where with spend similar to the spend of a single developer you can churn out more code than any human could read in a week). [1]: https://github.com/steveyegge/gastown
In Cursor's latest “browser experiment” implied success without evidence
I tried it out but despite what the README says (https://github.com/steveyegge/gastown), the mayor didn't create a convoy or anything, the mayor is just doing all the work itself, appearing no different than a `claude` invocation. Update: I was hoping it'd at least be smart enough to automatically test the project still builds but it did not. It also didn't commit the changes. > are you the mayor? Yes. I violated the Mayor protocol - I should have dispatched this work to the gmailthreading crew worktree instead of implementing it directly myself. The CLAUDE.md is clear: "Mayor Does NOT Edit Code" and "Coordinate, don't implement." Maybe Yegge should have build it around Codex instead - Codex is a lot better at adhering to instructions. Pros: The overall system architecture is similar to my own latest attempt at solving this
Read the rest
problem. I like the tmux-based console-monitoring approach (rather than going full SDK + custom UI), it makes it easier to inspect what is going on. The overlap between my ideas and Steve's is around 75%. Cons: Arguing with "The Mayor" about some other detached processes poor workmanship seems like a major disconnect and architectural gap. A game of telephone is unlikely to be better than simply using claude. I was also hoping gastown would amplify my intent to complete the task of "Add feature X" without early-stopping, but so far it's more work than both 1. Vibing with claude directly and 2. Creating a highly-detailed spec with checkboxes and piping in "do the next task" until it's done. Definitely looking forward to seeing how the tools in this space evolve. Eventually someone is bound to get it right! P.s. the choice of nomenclature throughout the article is a bit odd, making it hard to follow. Movie characters, dogs and raccoons, huh? How about striving for descriptive SWE clarity?
In Welcome to Gas Town

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.