blend-a-gnt Beta: a Work Task, a Bench, and a Prompt Walk Into a Bar

It is Tuesday. You have a ticket. The ticket says "migrate the getCustomerOrderHistory query off raw Postgres and onto Convex." It is not a hard ticket. It is a tedious ticket. It is the kind of ticket where you already know the shape of the answer and you just need someone to help you type it out without getting the details wrong, because the details in a query migration are where everything goes sideways — a column type you forgot, a join you half-remember, a null-handling quirk you wrote three years ago and have never once revisited.

You could open Claude Code cold. You could paste the query, explain what Convex is, explain what the schema looks like, explain that you want a rewrite-with-explanation, and then start working. You have done this a thousand times. It works. But it is also a thousand tiny setup decisions every time, and by Tuesday afternoon you are tired of making them.

So this Tuesday you open blend-a-gnt instead.

What blend-a-gnt is, as briefly as I can say it

blend-a-gnt is in beta on a-gnt right now. The conceit is simple and the experience is not quite like anything else I use. You bring three things to it: a bench, a task, and a prompt. A bench is a curated stack — tools, MCPs, souls, reference prompts — that someone (you, me, or a creator on the catalog) put together around a specific kind of work. A task is what you want done, in your own words. A prompt is the shape of the answer you want back.

You mix those three into a single session and you get going.

That is the whole thing, mechanically. The reason to care is what it feels like, which I will get to, and the reason it actually works better than opening Claude cold, which I will also get to, and which is not just vibes.

The Tuesday walkthrough

Back to the ticket. I open blend-a-gnt. The page loads with what Joey keeps calling the "tuxedo bar" — a dark wood frame, an amber spotlight in the middle where your work lives, and a little line of bartender text at the bottom that says something like "evening. what are we making." The metaphor is cheesy described in a sentence and somehow not cheesy when you are looking at it. Classy, not cheesy, is Joey's line for it. I think he's right.

I pick a bench first. I have one saved called "backend migration" that has neon MCP (so I can poke the live Postgres schema if I need to), convex MCP (so the model has current Convex docs and can query my deployment state), context7 (because I will inevitably need to look up some library I half-remember), soul-athos for the tone — athos is the one with gravitas, the musketeer, serious about the work — and a couple of prompts pinned that I reach for a lot, including one called "rewrite this query with explanation" that does exactly what the label says.

I drop the query into the task slot. I type, in English, what I want: "migrate this to convex, keep the pagination behavior, tell me anywhere the semantics change." I pick the "rewrite with explanation" prompt. I hit the thing that says pour, because of course it does.

And then it just works. Athos is serious, so the answer comes back measured and a little formal. The convex MCP has already pulled my current schema so the rewrite is against the real shape of my deployment, not a guessed one. Context7 is in the background if anything niche comes up. The prompt has pinned the output shape — rewritten query at top, semantic-diff callouts below, migration notes at the bottom — so I do not have to ask for that, I just get it.

I read it. I push back on two things. It updates. I take the output back to my editor and ship it in the afternoon.

That is the whole Tuesday.

Why the mix is more than the parts

Here is the part that took me a second to understand, because when I first heard about blend-a-gnt I thought, "okay, so it's a preset loader, cool." It is not a preset loader. The three things it combines do three different jobs, and any one of them alone is not the same thing.

The MCP gives you fresh state. This is the thing people most underestimate. A model without an MCP is working from whatever it learned in training, which is already months old by the time you talk to it. A model with convex or neon or supabase in its toolbelt can look at your actual schema, your actual docs, your actual deployment right now. For a migration task — or frankly for almost any task that touches a real system — this is the difference between "plausible answer" and "correct answer." The MCP is the ground truth.

The soul shapes how the answer arrives. This sounds cosmetic. It is not. If I run the same migration with soul-athos versus running it with no soul at all, I get different answers — not because the facts change, but because athos will catch himself and say "wait, before we do this, have you considered what happens on rollback." A blank model usually will not. The soul is the voice of the person you wish was reviewing with you, and that voice changes the shape of the thinking, not just the prose.

The prompt pins the output format. This is the least sexy and possibly the most load-bearing. When you know you want your answer in the shape "code block, then bullet list of changes, then migration notes," and you say so up front, you save yourself five rounds of "can you reformat that." The prompt is the mold you pour the answer into.

Mix them: fresh state, shaped thinking, pinned shape. That is meaningfully different from any one of the three. You can feel the difference.

The emotional thing I am going to admit

Work is not supposed to be fun. I mean, fine, work can be satisfying, work can be interesting, work can be the thing you choose to do — but in the day-to-day of shipping tickets, "fun" is not usually the word. Ticket migration on Tuesday afternoon is a grind on a good week.

blend-a-gnt is fun. I resent saying that in a blog post because it sounds like marketing, and I am skeptical of any tool that describes itself as fun, and yet here we are. The amber spotlight is fun. The bartender line is fun. Walking up and going "evening, I would like a backend migration with a twist of athos, neat" is — I cannot overstate this — fun. And the fun is not decorative. It makes me more likely to actually reach for the tool on a Tuesday afternoon when I am tired, which means I do better work, which means I ship cleaner tickets.

I think the tuxedo bar framing is doing real cognitive work here, not just aesthetic work. When you treat your setup as a thing you order — as a thing a bartender makes for you — you stop white-knuckling every detail and you start trusting the composition. You get to be the person who sat down at the bar, not the person running the kitchen. That shift, for me, has been weirdly meaningful.

The honest caveats

It is in beta. There are rough edges. Saving a bench sometimes takes a second longer than you'd expect. The MCP auth dance for some servers is still a little clunky the first time. The prompt library is small right now because it's mostly Joey and a handful of early creators seeding it. These are all fixable and I expect most of them fixed by the time you read this, but I want to be honest that we are not at "1.0 smooth."

The thing that is not rough is the core idea. The core idea is the best articulation I have seen of what a working day with these tools should feel like, and I have been thinking about this problem a lot.

How to get in

The invite link for the beta lives on the a-gnt homepage right now. Look for the blend-a-gnt block. Click it, get the link, come in. You can bring your own bench or borrow one of the public ones to start.

The bar is open. Come sit down. There is a ticket with your name on it and it is going to go faster than you think.