DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to review how agents interacted during a run with Sprawling Agents

Export the city's message history with playback and check it against the Ledger.

Who it is forA researcher or developer studying how a group of agents coordinates without human relay.

The problemAgent-to-agent messages are hard to audit after the fact, so claims about who did what are hard to verify.

The outcomeAn exported history of agent messages you can check against the Ledger record.

What you need first

  • Node.js and npm for the npm install route, or Bun, or the Rust toolchain for cargo install
  • A model provider account you can connect, or a local model
  • A browser to use the page the city opens
  • Alpha software: data formats and the interface may change between versions

Steps

  1. Start the city with sprawling up ./cities/first.
  2. Let residents message one another, find each other and coordinate a task.
  3. Ask the Mayor to run the playback skill described in crates/city/skills/playback/SKILL.md to export the history. (inferred, check the README)
  4. Open the exported history and compare a sample of messages with the Ledger entries.

Prompt for your agent

In the 2youg1/sprawling-agents repo, read crates/city/skills/playback/SKILL.md, then export the message history of the city at <city path>. Expected output: an exported history file. Verify that three messages picked at random appear in the Ledger with matching content.

Caveat. The README describes playback as exporting history for checking against the Ledger, so the exact export format should be read from the skill file, not assumed.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for 2youg1/sprawling-agents and "Review how agents interacted during a run"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer