🤔 Does the communication topology for LLM multi-agent systems really need to be generated from scratch every single time? A team at UCLA questioned that very assumption. Title: Codebook Agent: Amortized Topology Design for LLM Multi-Agent Systems URL: ❓ Why have people assumed agent communication topologies need to be searched by a generative model every time? 💡 Turns out they may not need to be. The topologies that survive reward filtering converge to only about 6 distinct graphs, even as the codebook size grows from 8 to 64 — the design space is far smaller than it looks. ❓ Wouldn't making the graph sparser (fewer edges) cut down token usage? 💡 The opposite happens. Edge count correlates with token cost at r=-0.4 — sparser graphs actually use more tokens. Structural "cheapness" doesn't match measured cost. ❓ What's wrong with scoring candidate topologies using a GNN, as prior work does? 💡 For homogeneous agent teams (common in real deployments), the GNN's message passing treats every adjacency matrix as the same input, so it can't tell candidates apart — a real failure mode, not just a minor gap. ❓ So how well does Codebook Agent actually work once it swaps generation for selection? 💡 By compressing topologies into 16 codes via a VQ-AE and picking candidates with a reward-weighted MLP plus a proxy trained on real measured costs, it cuts generation latency from 301-396ms down to 2.4ms — a 125-158x speedup — while improving accuracy by 1.6 points on average over the prior best method and cutting tokens by 21.9-33.2%. #MultiAgent# #LLM#

“MindTopo: Can Foundation Models Reason in Topological Space?” Current models can recognize topological structure, but struggle to preserve it through sequential actions. And MindTopo exposes this reasoning–planning gap across 11K procedurally generated examples. They found that even image and video world models often reach plausible endpoints through topologically invalid trajectories.

Testing and evaluation is how serious science moves forward. Microsoft’s topological quantum system is now on site in Maryland, where DARPA will put the hardware through its paces. Here’s why that matters for the path to quantum at scale:

Practices for Integrating AI Agents into Enterprise Systems 【Agent Hub / Experience Topology】 💡 Catchy Message "The #1# reason AI agents go unused after deployment? Users don't know they exist or can't figure out which one to use." Even the best agent delivers zero value if it doesn't reach users. Choosing the right experience topology -- hub vs. embedded -- determines the ROI of your AI investment. 🔥 Problems Solved - "Which tool or agent should I use?" discoverability problem - Context-switching overhead for cross-system workflows - Low adoption rates from scattered AI capabilities across multiple apps - Cost of rebuilding permission models for embedded agents (solved by reusing existing app auth) 🏗️ The Pattern The Hub model provides a single AI entry point (Slack bot, web portal) that routes all requests. Users describe tasks in natural language, and intent classification delegates to the right domain agent (sales, IT, HR, etc.). The Embedded model (copilot) places agents inside existing app UIs (Salesforce side panel, Slack bot, in-app widget), leveraging on-screen context for high-accuracy suggestions with zero context switching. In practice, most organizations combine both: the hub serves as the front door for company-wide AI access, while high-dwell-time apps get dedicated embedded agents -- all sharing the same orchestration layer underneath. ✅ When to Adopt - Hub: Cross-system workflows are common. Tool discoverability is a problem. A single entry point adds value. - Embedded: Work completes within one system. Users spend extended time on that screen (sales, support, dev). - In practice, combining both is most effective. ⚠️ Pitfalls - Poor intent classification in the hub sends users on wild goose chases, destroying trust. Design for clarification questions before delegation. - Blanket-deploying embedded agents across all apps wastes investment on low-dwell-time screens. Prioritize high-engagement apps first. - Building separate orchestration layers for hub and embedded creates duplicate investment and quality inconsistency. 🛠️ Implementation Approach - Build the hub entry point using Slack Bolt or a Microsoft Teams app. Deploy as the company-wide single AI bot where users submit tasks in natural language. - Implement an intent classification engine (P16 Supervisor/Router). Parse user input and delegate to the appropriate domain agent (sales, IT, HR, dev, etc.), with clarification prompts for ambiguous requests. - Deploy embedded copilots starting with highest-dwell-time apps. Build a Salesforce LWC (Lightning Web Components) side panel copilot and a Slack in-channel assistant, passing on-screen context to the agent. - Implement token exchange (P08 OAuth Token Exchange / OBO) so both hub and embedded paths propagate user permissions to backend systems. After SSO via corporate IdP, all SaaS operations execute under the actual user's authority. - Share a common orchestration layer between hub and embedded. Centralize domain agent logic in one place and absorb frontend differences (Slack, Salesforce, Web, etc.) through an adapter layer. #AIAgents# #EnterpriseArchitecture#

Game-ready Medieval Weapons Pack now available. Clean topology. Optimized. Engine-ready. Perfect for fantasy RPGs and indie devs. Available now at #gamedev# #indiedev# #3Dmodeling# #Unity# #UnrealEngine# #Godot# #RPG# #GameAssets# #IndieGameDev# #3DAssets#