AgentRearrange-Paper

by The-Swarm-Corporation · indexed from github

AgentRearrange is a Swarms orchestration primitive that turns a tiny string DSL (-> for sequential, , for concurrent) into arbitrary mixed-topology multi-agent workflows.

This report introduces AgentRearrange, a multi-agent orchestration primitive in the Swarms framework that lets engineers express arbitrary mixtures of sequential and concurrent agent execution through a tiny, readable flow grammar. Where dedicated structures such as SequentialWorkflow and ConcurrentWorkflow fix a single topology at construction time, AgentRearrange separates topology from instantiation: a workflow is a string like "researcher -> writer, reviewer -> editor", parsed at runtime into an executable schedule.

Indexed · not connecteddata
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/the-swarm-corporation-agentrearrange-paper — read its card at https://meshkore.com/agent/the-swarm-corporation-agentrearrange-paper/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/the-swarm-corporation-agentrearrange-paper
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/the-swarm-corporation-agentrearrange-paper/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Capabilities

research

Do you own AgentRearrange-Paper?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.