Built by builders.

AI coding tools gave individual developers a step change. A single engineer can now do in hours what used to take a week. That's real, and it's only getting faster.

When you can build anything, the question changes. It's no longer about capacity. It's about direction. What should you build? Why? Does your whole team see it the same way?

Product, design, engineering. They all need a place to refine ideas together and get clear on what matters before agents start running. When a PM can shape a brief as fast as an engineer can ship one, when a designer's context flows directly into what gets built, when a founder's customer insight becomes a shipped feature in a single session. That's when teams find another gear.

That's the product we're building.

We started with Taskmaster, an open-source tool that gives coding agents a structured plan before they execute. The insight was simple: agents with a plan produce better work than agents without one. Every time. Taskmaster hit 1.5 million downloads and 25,000 GitHub stars. Every major coding tool shipped their own planning mode after.

Taskmaster solved a real problem, but only for one person at a time. One developer, one plan, one execution. Customers kept asking the same question: how do I take this to my team? How do we get everyone building from the same understanding?

That question led us to Hamster. Not just a plan for an agent, but shared direction for the whole team. The context, the reasoning, the decisions that shaped the work, all connected in one place, available to whoever or whatever picks it up next.

Taskmaster showed us what happens when agents have good inputs. Hamster applies that lesson to the whole product team.

We use Hamster to build Hamster. That's not a tagline. Most of our day is spent in briefs with customers, working out exactly what they need, then watching agents deliver it. When something doesn't work, we feel it immediately because we're the first users.

We ship to customers multiple times a day. If you ask for something in Slack, you'll probably see it tomorrow. Not because we move recklessly, but because when direction is clear, the path from idea to shipped feature gets very short.

We don't run sprints. We don't estimate story points. We don't schedule grooming sessions. We write briefs, refine them together, and ship. The time we used to spend on coordination, we now spend on customers and strategy. That's the tradeoff we optimized for.

If there's something you want to see in Hamster, come tell us. We build with the people who use what we ship. That's the fastest way we know to build the right thing.