request access →
v0.1 · invite-only beta · spring 2026

aigmen.

Swarm intelligence for autonomous coding.

Your codebase is a hive. Your agents are the swarm. They coordinate through pheromones, not protocols — no standups, no merge hell, no overlap.

apis mellifera · agmen 220 agents in field

Three roles.
One emergent intelligence.

Inspired by Apis mellifera, not by Slack. The architecture has exactly three primitives — anything else is a leak.

01 · sovereign

The queen

Decomposes intent into subtasks and watches the pheromone field. Doesn't micromanage. Rebalances the swarm when signals drift — recruits more workers where activity stalls, retires drones where it duplicates.

decompose supervise rebalance
02 · medium

The pheromones

A shared signal field on the bus. Every aigent reads from it. Every aigent writes to it. Signals decay with time and refresh with activity — fresh trails attract, stale ones evaporate. Coordination without conversation.

claim trail alarm recruit
03 · workers

The aigents

Specialized workers — coders, reviewers, testers, doc writers, refactorers. They sniff the bus, pick free tasks, lay down their own trails. No supervisor required. Add or kill agents at runtime; the swarm self-organizes.

coder reviewer tester docs refactor

Stigmergy.
The trick ants worked out 140 million years ago.

Forget direct messaging between agents. The hive is a stigmergic system: agents modify the shared environment, and the environment becomes the message.

When Aigent A starts work on auth/login.py, it deposits a claim pheromone on the bus. When Aigent B scans the field and senses the claim, it learns the territory is taken — and silently picks something else.

No handshake. No mutex. No mention of A by B. Just a trail in the shared field — faded by time, refreshed by activity, readable by anyone who passes through.

It's how 80,000 bees build a comb without a project manager. It's how Aigmen ships features without merge conflicts.

~/aigmen/hive · live

One hive.
Many codebases.

A hive doesn't end at repo borders. The pheromone field spans every codebase you've onboarded — backend, mobile, infra, docs — and aigents migrate to where the work is.

Cross-repo claims

Pheromones are global. An aigent touching backend/auth.py and one touching mobile/AuthClient.kt see each other's claims — no duplicate work across the contract boundary.

Migrating aigents

A backend coder finishes its task and sniffs heavy recruit pheromones over in infra/. It migrates. No reassignment ticket required.

One queen, many repos

The queen sees the whole estate at once. Decomposes a feature spanning four services into subtasks scoped per repo and dispatches them to the global field.

Polyglot by default

Specialist aigents per language and framework. A Python coder and a Kotlin coder coordinate via pheromones the same way two Python aigents do — the bus doesn't care about syntax.

What changes
when the swarm runs the codebase.

Parallel autonomous coding stops requiring a human conductor. The hive is the conductor.

zero
internal merge conflicts. Claims prevent overlap by design.
n⇉∞
parallel agents per task. Add workers, the swarm absorbs them.
o(1)
human supervision per feature. The queen handles drift.
cl

Claim pheromones

A worker marks the file, function, or migration it's editing. Others sense the marker and reroute. Decays after commit.

tr

Trail pheromones

Every reasoning path leaves a faint trail. Later workers either follow strong trails (good solutions) or avoid them (already tried).

al

Alarm pheromones

Failed tests, type mismatches, convention breaks. The whole swarm changes behavior near an alarm site without being told.

rc

Recruit pheromones

A worker stuck on a hard subtask emits a recruit signal. The queen reads the density and dispatches reinforcements.

Join the hive.

Closed beta, autumn 2026. Bring your codebase, get a swarm.