menger

For software teams of people and AI agents

Agents show youwhat they'd build,and ask.

The page itself, built in the ticket and shown at phone and desktop width; the map it came from; the question that decides the rest. The team notes and answers in place; the work goes on.

open source · MIT licence

The whole app: the plan's tree on the left; on the right the ticket OFFLINE-16, holding a help page an agent built in a phone frame and a desktop frame side by side. Both frames scroll down the page together, then back up.
[ fig. 1 — OFFLINE-16: the page an agent built, both screens scrolling, in the plan ]
01 — one page, start to finish

Mapped, built, shown, decided — together.

Two screens. Left, a Claude Code session in a terminal: asked to queue the question in a ticket, the agent runs the queue command for OFFLINE-15 at now, then await_reply, which says waiting. Right, the app: a red tab arrives along the bottom edge; the owner opens it, reads the reason and the question, picks One page, and submits. Left again, await_reply prints replied, answered, shape equals one; the agent says the owner picked One page and closes the input.
[ fig. 2 — replayed from a real session: the agent queues its question and listens; the owner answers in the app; the agent hears it ]
01 · an agent

An agent builds the page.

The map, the page, the components it needs, filed under the build, at every width.

doc→390 · 1440

02 · you

The team looks, notes, answers.

The agent queues its question; it arrives on every open screen. A note pinned on anything; one decision, each option with its cost.

now→decided

03 · the build

The deploy says where it runs.

The agent builds what you picked; the deploy records itself; the ticket says it reached prod.

Complete→prod

02 — what is different

Built for people and agents together, then for shipping, then for scripts.

A ticket holds whatever an agent builds, and the talk about it.

A body is markdown, a diagram or a whole HTML page, a decision in it like any paragraph. Anyone pins a note on any part; notes and answers stay with the work.

Inside a ticket
A ticket page in annotation mode: the help site mapped as a graph, the decision with its options beneath, and at a pin on the title the team's two notes listed, each with Resolve.
[ fig. 3 — OFFLINE-15: the plan, the team's notes, the decision ]

Your own components, their look and feel agreed first.

Define a component in a ticket, with its docs and the parts a theme may skin, and use it in any body. Every state is seen before the app has a line of it.

Components
A ticket defining two components: the banner shown in its three states with the markup beside them, and the conflict card's preview, both values side by side with Keep mine and Keep theirs.
[ fig. 4 — OFFLINE-17: the team's banner and card, in every state ]

Every deploy writes itself into the plan.

Your CI records each deploy; menger works out which tickets it carried. A ticket says where it runs; the board, what reached prod and what still waits.

Deployments
The deployments page for OFFLINE: the Complete work still waiting for prod, then beta and prod as columns, each with what it runs, its deploy and the tickets it carried.
[ fig. 5 — OFFLINE's beta and prod: each deploy, what it carried, what still waits ]

One wire for people, scripts and agents.

Everything menger does is a method on one connection; the app has no side door, and ships inside the binary. Anything you can click, an agent can call.

The command line
# file the page under the build, then put its question in front of the owner
synapse -P 4455 menger tickets create --epic OFFLINE --parent OFFLINE-15 --kind doc \
  --title 'Page · Working offline' --body "$(cat page.html)"
synapse -P 4455 menger tickets queue --id OFFLINE-15 --urgency now --input shape \
  --reason 'OFFLINE-15 is idle until the shape is picked'
[ fig. 6 — the calls behind fig. 1 and fig. 3 ]
03 — get menger

On your own machine.

Your own machine

Two commands with Rust installed.

cargo install menger --features embedded-app
menger --db-path ~/menger/tickets.db

The web app is built into the binary. Then open 127.0.0.1:4456.

The ports, the flags and checking the file: the guide →