Agentry: a landing page for the Parallel Agent Control Board idea

See which coding agent is blocked on you, at a glance

Ghostlaunch led with the pain people raised first: by lunch they could not tell which agent was blocked on them. The headline promises that answer at a glance. It names one concrete outcome instead of the whole system. File claims and live decisions are left to the subheadline.

Words it borrows from real posts:

• “Whoever saved last wiped the others”
• “No errors anywhere”
• “blocked on me”
• “still writing”

1. Navigation: It gives developers quick jumps to how it works, features, pricing and FAQ, and keeps the early access button in reach from the top.
2. Hero: It pairs the headline with a mock dashboard showing one session blocked on you, so visitors see the fix before reading. The local-only line answers a worry about code leaving the machine.
3. Problem: It plays back what people wrote: losing track, silent wipes, copying between windows, stale context. Two pains here, the 40-minute wait and half a day pasting, go past the posts.
4. How it works: Four short steps show the idea is a small layer added to an existing setup. That matters to people who already juggle several sessions and don't want more to manage.
5. Features: Each feature maps to one complaint: who is waiting, silent overwrites, stale decisions, and being the go-between. The small mockups make each one concrete.
6. Who it's for: It names who the test is for, people running several sessions on one repo, and who it is not for. That keeps sign-ups honest and the test clean.
7. Comparison: One post said keeping files apart doesn't prevent incompatible decisions. This table makes that point: isolation tools keep agents apart, but they don't share decisions or show who is blocked.
8. Pricing: It sets out a free status view and a paid plan for collision control, and repeats that both run locally.
9. FAQ: It answers the doubts a developer would raise: which agents, where data goes, why not separate checkouts, what happens on a clash, and setup time.
10. Final call to action: It restates the two core pains, who needs you and silent overwrites, and asks once more for early access in the same words.
11. Footer: One line sums up the idea as a local coordination layer, so the page ends on what it is.

• Free: Free
• Pro: $19 a month

The free plan gives the status view, the part people missed most. Pro at $19 a month is pitched for when you want agents to stop colliding. It tests whether people will pay for that. The FAQ claims one overwrite costs more than $19, but no post backs that up.

The button says Get early access. After the click: Agentry is almost ready

Get early access is honest because the product does not exist yet. The click asks only for interest. A dialog then says Agentry is almost ready, so Ghostlaunch can count how many developers want it.

Brand colour #F2A93B, the “technical” font pair, a dark theme.

A dark theme and technical fonts match the terminals these developers already live in. The amber brand colour reads like a status light. That suits a page about spotting which session is blocked and needs you.