12,000 starlings, each watching only its 7 nearest neighbours. No leader, and you still get a murmuration.
Built in the browser: plain JavaScript, no libraries, no build step. Plus colliding galaxies on the GPU and a fluid you paint with light.
Try it: https://t.co/d0AVlqnP2X
@_avichawla same weights run twice saves memory, but each loop still costs compute. does the 4B looped one end up about as slow per token as the 9B it's matching?
@omarsar0 the most similar memory is usually just a recap of where the agent already is ha. what do they score memories by instead, whether it changed the next action in earlier runs?
@addyosmani themes being mods underneath is a nice call, one system instead of two. can the backdrop react to the session itself, like shift when a tool call fails or a long task finishes?
Tasking's /api/health still answers {"status":"Jenkins5"}.
Wiring GitHub webhook → Jenkins → Docker, I couldn't tell if a push had really deployed. So I bumped one string and curled it.
OK, Jenkins1, 2, 3, 4, 5 over three days in January. It never went back to OK.
One of aidevkit's tests hands the installer a skill with a file named ../../../.ssh/authorized_keys.
The hub rejects .. paths at publish. The CLI checks again before it writes anything, in case the registry itself gets hacked.
I don't fully trust my own server either.
@kentcdodds worth the wait imo. aidevkit scans skills and MCP servers at publish and again at install, and even a plain regex pass flagged 13 Copilot skills for things like curl | bash. curious what npm's scan looks at
@zeeg the actually _recurring_ part is doing a lot of work in that sentence ha. was Sentry's revenue sticky from the start, or did that take a while too?
@wesbos the speed is what makes the voice part work. are the WebMCP tools registered by the page itself, so the agent only sees what the builder chose to expose?
@hwchase17 framework-agnostic is the part I'm curious about. does LangSmith trace a Claude Code or Codex session the same way, or only agents you build on your own stack?
@GergelyOrosz so rolling back wasn't even on the table. was that because the migration had already written data the old Exchange side couldn't read anymore?
@wesbos same. the demos i trust are a screen recording of the real thing running, boring parts included. the cinematic ones always cut right before it breaks