SYNTHESIS NOTE
Topics›Agents Multi›this note

Can AI systems design unique multi-agent workflows per individual query?

Explores whether meta-agents trained with reinforcement learning can automatically generate personalized multi-agent system architectures tailored to individual user queries, rather than applying fixed task-level templates uniformly.

Synthesis note · 2026-02-23 · sourced from Agents Multi

Previous approaches to automating multi-agent system design operate at the task level: design one workflow for "code generation tasks," another for "summarization tasks," and apply each uniformly to all queries of that type. FlowReasoner (2025) shifts this to the query level — generating a unique multi-agent system for each individual user query.

The architecture has two phases. First, distill from DeepSeek R1 to give the meta-agent basic reasoning about how to design multi-agent workflows. Then enhance via RL with external execution feedback — the meta-agent generates a multi-agent system, that system runs on the query, and the execution result provides reward signal. A multi-purpose reward guides training across three dimensions: performance (did it work), complexity (how many agents and steps), and efficiency (how much compute).

This matters because one-size-fits-all multi-agent systems lack the capability for automatic adaptation to individual queries. A code generation task where the user wants "build a 2048 game" needs a fundamentally different agent composition than "fix a sorting bug." The query-level approach treats multi-agent architecture design as itself a reasoning problem amenable to RL.

The progression is notable: manual design → fixed template optimization → graph-based workflow search → code-based meta-agents → RL-trained query-level meta-agents. Each step automates one more degree of freedom. The connection to Can we automatically optimize both prompts and agent coordination? is direct: FlowReasoner represents multi-agent systems as code and optimizes them, but at the individual query level rather than the task level.

Since Can computational power accelerate scientific discovery itself?, the RL-trained meta-agent approach may follow similar scaling dynamics — more compute for the meta-agent should yield better per-query system designs.

MasRouter as structured alternative (from Arxiv/Routers): MasRouter provides a more constrained approach to per-query MAS design than FlowReasoner. Where FlowReasoner generates arbitrary multi-agent systems via RL-trained code generation (maximum flexibility, less interpretability), MasRouter uses a cascaded controller: variational latent variable model for topology selection → structured probabilistic cascade for role allocation → multinomial distribution for LLM routing. The cascade provides interpretable intermediate decisions at the cost of a fixed structure-type vocabulary (Chain/Tree/Graph topologies, predefined role categories). FlowReasoner trades interpretability for expressiveness; MasRouter trades expressiveness for interpretability and likely faster convergence. Both achieve per-query optimization. See What decisions must multi-agent routing systems optimize simultaneously?.

Inquiring lines that read this note 31

This note is a source for these research framings, grouped by the broader line of inquiry each explores. Scan the bold lines of inquiry; follow any specific question forward.

How do neighboring agents influence whether others cooperate or collude? How can conversational agents maintain consistent personas across multi-turn dialogue? What reasoning architectures enable models to solve complex problems efficiently? When do multi-agent systems outperform single frontier models? How do pretraining biases affect reward signal effectiveness in RLVR? How do standardized protocols improve multi-agent coordination and reliability? What makes step-level supervision effective for complex reasoning traces? How well do AI systems understand human social norms? How do agent-learned skills transfer and improve across different tasks? Do structural constraints outperform deep architectures in recommendation systems? Does AI assistance promote real skill development or substitute for independent learning? How should agents manage memory granularity to improve long-term performance? Can harness architecture and protocols provide agent reliability without model scaling? What fundamental constraints limit how effectively agents can improve themselves? How does AI adoption across firms reshape employment and inequality? What execution architectures enable agents to most effectively use tools?

Related concepts in this collection 5

This note in its neighbourhood — explore the map, then jump to a related concept in the list below.

Concept map
14 direct connections · 98 in 2-hop network ·medium cluster Open in graph ↗

Click a node to walk · click center to open · click Open in graph to see this note in the full knowledge graph

your link semantically near linked from elsewhere

Related papers in this collection 8

Papers most semantically related to this note, ranked by cosine similarity in the embedding space.

Original note title

query-level meta-agents generate personalized multi-agent systems per user query via RL with execution feedback