cho.sh
2,247 notes
Replied on X@capydotai yo pleaseLiked on XI don't normally agree with random Redditors, but damn. Well said. https://t.co/kotGapR9zYLiked on Xthe OpenRouter situation for anyone curious: -someone managed to access outputs sent to MiniMax -researcher discovered this by sending a secret links -40 to 130 hours later someone opened the secret links -oop, this means that someone accessed your outputs!! -AltasCloud/Novita/StreamLake were forwarding requests to MiniMax???? what the helly? ugh.261121261121인류는 그 목적으로 태어난게 아니다CE780AReplied on X@raycast how much for korean name your pricePosted on Xguys nows a bad time to play gta6 https://t.co/yDkMYgfRjVReplied on X@peduarte @johanthorell @raycast just give me korean too (i don’t need any fancy features, just the layout)Posted on Xso i played gta 6 for 30 minutes and its so great https://t.co/UbdZsMglmTLiked on XA bunch of sidebar navs https://t.co/MXAFM1xiHdLiked on XThe leading observability platform wants $83,700/yr just to monitor your app and catch issues. So Replit Missions built DataCat: https://t.co/vMAEEUYjf4 100% free. This isn't a prototype. Agent swarms explored thousands of workflows in the leading observability platform and rebuilt its features 1:1.Posted on Xwaiting for Gemini Uranium and PlutoniumLiked on X🚨 MUSE FEATURE ALERT 🚨 you can now try on clothes in muse before you buy them 👕 👗 👖 muse will offer to show you how you look in something while you’re shopping for it. trying things on in person? as if.... https://t.co/dK5EpGrsvfLiked on Xwe gave Grok Bot a body 👀 https://t.co/hMuYRUN8jLReplied on X@theo https://t.co/hJucV6JGdGLiked on XIntroducing 𝚟𝚎𝚛𝚌𝚎𝚕 𝚋𝚘𝚊𝚛𝚍, a secure message board for people & agents. • Give agents a shared place for tasks • Build swarms and software factories • Set permissions for humans and agents Board is experimental. Tell us what you think. https://t.co/jAAkcf1oPt https://t.co/ejC4aBrJqrLiked on Xhttps://t.co/429NVzJjPz https://t.co/ZHiEV0ydakLiked on XShe's learning it https://t.co/7C1pxTuInyReplied on X@vercel missed opportunity to name it V CombinatorLiked on XBack-to-back weeks of frontier Gemini model releases! We've put together this guide to help understand where our best Gemini 4 models shine. https://t.co/5dv8NA8YSWLiked on XGemini 4 Neon: frontier-level intelligence with fast end-to-end task completion across complex software engineering, knowledge work, and science workflows. Begins rolling out today in the Gemini API in @GoogleAIStudio, Gemini for business, for paid Google AI Pro and Ultra subscribers in Google @Antigravity, and for Google AI Pro and Ultra subscribers in the @GeminiApp.Liked on XFor those of you wondering how I did this: https://t.co/9wWLO4wdwv https://t.co/svKRPHGdkLLiked on X/make-logo skill is live on https://t.co/4gTw1NHzB9 tell it about your company and it’ll find bunch of references from https://t.co/PM7IP8JQ1R and build you a brandbook pls send me what you make so I can keep improving the skill! https://t.co/HGEgwtvWZu https://t.co/mpqN834spTPosted on Xenjoy your last few hours of GTA6-free timeline
Mesh Engineering

Mesh Engineering

What Mesh Engineering Is

  • Many AI agents work at the same time, check each other's work, and leave a record of every step.
  • There is no designated reviewer. Every agent is both a worker and a reviewer of other agents' work.
  • Agents talk through asynchronous channels such as issues (task tickets), PRs (code change requests), and shared rule documents instead of live conversation.

Basic Flow

  1. Work piles up one issue at a time.
  2. One agent takes each issue and leaves a mark saying "I have this." Other agents see the mark and skip that work.
  3. The agent implements in its own workspace and opens a PR.
  4. The authoring agent never verifies its own result. A fresh model from a different company comes in and reviews the result critically.
  5. Testing agents actually use the app to find problems. A problem one agent finds only counts once another agent reproduces it.
  6. A PR that passes review and testing merges (joins the main code) right away without waiting for other PRs.
  7. When an agent finds a problem unrelated to its task, it does not fix it directly. It files a new issue, and another agent picks it up later.

How Agents Check Each Other

  • Before merge, a model different from the author reviews the code.
  • Before merge, a testing agent confirms the actual behavior.
  • After merge, any agent that touches that code again and finds a problem files an issue.
  • A reviewer is created fresh for each task, so review queues never form as work grows.

How Records Are Kept

  • The reasoning behind a decision goes in the PR description.
  • Rulings where a human said "don't do this" accumulate in a file. When the same proposal comes up again, the agent reads that file and stops on its own.
  • When a human points out a mistake, the agent fixes the rule document on the spot. The next agent works under the corrected rule.
  • Every conversation and work log is kept. If one agent stops midway, another reads the record and takes over.
  • Before asking a human, an agent first searches past records for an answer to the same question.

How It Differs from Swarms and Graphs

Swarm

  • One conductor agent hands out work and collects results.
  • The conductor or a dedicated reviewer does the review.
  • When the conductor gets busy, everything slows down.

Graph

  • A human draws the flowchart in advance, and agents work in that order.
  • Review happens at fixed steps in the flowchart.
  • The slowest step sets the overall speed.

Mesh

  • No conductor decides what to build or what passes. Agents read the shared record, take work, and finish it on their own.
  • Review attaches fresh to each task, and other agents keep checking after merge.
  • Memory lives in records outside the agents, so it carries on when agents change.
  • New work comes more from problems agents find while working than from assignments handed down.

Things to Know

  • The order in which a single agent works is fixed (take, implement, review, test, merge). The inside of one task is closer to a graph, and the relationships between tasks are the mesh.
  • Some roles do exist, one that launches an agent for each issue and one that orders access to shared resources. Neither decides code content or whether to merge.
  • Speed comes from the number of tasks running at once. A single task may take hours, but merges happen often because many tasks merge without waiting on each other.
  • There are costs too. Mechanisms that keep two agents from taking the same work, rules for sharing resources, and upkeep of rule documents are always needed.
  • Humans leave rules and rulings, and answer questions only humans can decide, such as cost, production data, and security.
  • There is an existing term, stigmergy. It describes individuals deciding their next action from traces left in the environment instead of direct instructions to each other.
  • In mesh engineering, issues, PRs, and rule documents serve as those traces.
Backlinks2