WeWorkBuddy

Show HN: Swarm World – local LLM creatures living in a little tile world

This is a hobby project: a small tile world where every creature is a local language model. A creature only knows what its body senses, written out as text ("You see: a boulder 4 steps northwest; a campfire (burning) 5 steps east ... Others: Loam 2 steps southeast, carrying a stone knife"). It acts by stating an intention, and the world decides whether that works. There are 34 verbs, things like gather, craft, give, teach, dig and climb. I been watching these swarms happen and I wanted

Read original source
Source page screenshot: Show HN: Swarm World – local LLM creatures living in a little tile world
Source page screenshot · news.ycombinator.com

Source record

Recorded metrics

points · 2 votes
2026-11-04 18:30:32.860Z
cumulative since publication

Research analysis

What changed

Source account: This is a hobby project: a small tile world where every creature is a local language model. A creature only knows what its body senses, written out as text ("You see: a boulder 4 steps northwest; a campfire (burning) 5 steps east ... Others: Loam 2 steps southeast, carrying a stone knife"). It acts by stating an intention, and the world decides whether that works. There are 34 verbs, things like gather, craft, give, teach, dig and climb. I been watching these swarms happen and I wanted

Version & cost evidence

Source votes: 2 votes (Nov 4, 2026 UTC; cumulative since publication) Recent records to compare: “Show HN: Pico-WAM – smallest world-action-model” (Show HN, Nov 6, 2026); “Show HN: UUMit – turn idle machines into model endpoints” (Show HN, Nov 6, 2026). Shared themes are navigation hints; they have not been verified as the same need or independent corroboration.

Who is affected

Identify the existing workflow this change affects before recommending an upgrade. Launch attention does not establish improvement; an API, pricing or availability change may instead create migration work.

Missing comparison points

Missing checks: old versus new behavior, affected plans and regions, availability date, compatibility, rollback path and cost under the same workload.

Migration check

Save the release or policy notice, run the same task on the old and new option, and compare outputs and the full bill. For retirement notices, verify the deadline before scheduling migration.