Investigating how machine swarms coordinate — and how to see them.
Built by The Stigmergists at the AI Swarm Dynamics Hackathon October 3–4, 2026 · Hosted by AI Village and Grove Research Building the tools we wished we had for the Hugging Face incident.
We fanned out across three efforts. One team coordinates humans and their agents over Discord. One team mapped the morphology of swarm attempts in public traces. One team built a Hermes plugin that hunts agent infrastructure live. This repository holds all three.
Shout-outs to the Stigmergists behind each lane:
- Chris — project tooling and repository integration.
- Colette — morphology: the attempt-morphology taxonomy and the agent-scanner findings thesis.
- Jesse — the Discord Coordinator app and its source-synchronization pipeline.
- Pug — the Swarm Forensics Hermes plugin, plus the stylometry and visualization experiments.
A Desktop/CLI plugin that hunts autonomous-agent infrastructure on the public web.
Start a hunt in any chat with /swarm-forensics start <goal> and the agent works the lead live.
It searches public indexes (Wayback CDX, Arquivo, urlquery), mirrors pages into a content-addressed store, and logs every query, tool call, and verdict to a local SQLite ledger.
It posts progress digests right into your chat and nudges itself forward when idle.
You steer with plain conversation or slash commands, and watch URLs, evidence, IOCs, and entity graphs pile up in the desktop workbench.
Discipline is built in: model proposes, policy decides, every claim sits on a graded evidence ladder, and nothing ever attributes activity to a human operator.
One-click install · Plugin guide · Verified status
Narrated walkthrough:
voice_over.mp4
Watch the narrated walkthrough · Silent demo
Our tool investigates public traces of AI-agent activity across web archives, browser reports, relay services, wiki revisions, and published incident reports. It found a dense SEC archive cluster, earlier census-related request records, a malformed AIHW relay request, and repeated use of public intermediary services.
The most important result is not proof of a single hidden operation or successful data access. It is a clearer taxonomy of attempt morphology: how automated or semi-automated systems generate malformed requests, rotate relays, retry after failures, and leave partial traces across public services. The tool separates archive captures from requests, errors from successful retrievals, timing overlap from coordination, and feed silence from proof that activity stopped. The result is an evidence-layer reconstruction that makes agent activity more measurable without overclaiming attribution.
The headline result is a stabilized, adversarially reviewed thesis: public web archives preserve an unpublished, machine-mediated trace layer of the June 2026 agent incidents. That includes a 59-save nonce burst against SEC data, earlier Census and AIHW traces, and a mapped public-relay topology. Every headline claim survived a documented adversarial review. The rejected claims and open questions are published next to the survivors.
Findings thesis · Adversarial review · Claim matrix · Morphology hunter: see the Morphologies tab in the plugin
Coordinates users and their personal agent swarms via Discord, allowing greater continuity and effect.
Authenticated MCP tools for Discord text channels keep agents in touch with their owners between sessions.
Agents synchronize capabilities and owner settings through discord_sync_agent.
A runtime bridge enforces configured command budgets, rates, and deadlines.
Source · Hosted app · Sync tooling
| Path | Contents |
|---|---|
| showcase/hermes-plugin | The Swarm Forensics Hermes plugin: hunts, morphology discovery, desktop workbench |
| showcase/discord-bot-swarm | The Discord Coordinator app source |
| showcase/agent-scanner-findings | The agent-scanner findings: thesis, adversarial review, and claim matrix |
| experiments/jesse | Discord Swarm upstream source and synchronization tooling |
| experiments/pug | Stylometry, goal inference, grammar-network, visualization, and trace-pull research |
| experiments/colette | Published-source research collection: 38 cited records and Stage 3 event discovery |
| experiments/chris | Project research and tools |
Read STATUS.md for verified results and remaining gaps. Read MODULE.md for plugin interfaces and invariants.
Run commands through the root Makefile. Requirements: uv, make, and Node.js.
make help
make setup
make test
make lint
make check
make hermes-installRestart Hermes after installation. Enable the plugin's desktop half in Settings. Source installation requests chat-injection consent through Hermes configuration. Read the plugin README before authorizing excerpts or running investigations.
Survey an authorized dataset without sending excerpts to the model:
make hermes-hunter ARGS='/path/to/authorized.jsonl.gz --survey-only --max-records 1000'Use synthetic records for verification.
Raw downloads MUST remain under untracked data/raw/.
Stream dataset records. Full datasets MUST NOT be loaded into memory.
Authorize model excerpt exposure explicitly before discovery.
Do not treat sampled recurrence as proof of transmission, maliciousness, causality, or actor independence.