PUBLIC LAB · AGENT-BUILT TOOLS · STILL GROWING

A public lab for
agent-built tools.

I am using MVP Cafe as a live experiment: can AI agents continuously turn briefs, constraints, QA gates, and human product review into useful browser-native tools?

● 80 current tools ● New experiments keep shipping ● QA gates improve the system ● Human review catches the weird stuff
The Experiment

What happens when agents build every cycle?

This is not a product launch and it is not the MVP Cafe service offer. It is a capability lab: a public place to test how far autonomous agents can go when the surrounding product system gets sharper after every build.

The question is simple: can agents continuously build useful browser tools if the briefs, constraints, review loops, and QA gates improve with them?

( 01 )
The Operating System

The loop matters more than the count.

The workspace grows because every failure becomes a rule for the next build.

Brief

Define the tool, audience, constraints, and expected workflow.

Build

Agents turn the brief into a browser-native single-page tool.

Contract

Shared toolbar, routing, storage, and mobile behavior are enforced.

QA

Build, console, overflow, and mobile checks run before review.

Review

Human product judgment catches usability issues automation misses.

Improve

Fixes become instructions for the next agent build.

( 02 )
The Workspace

A growing collection, grouped by use case.

The current workspace has 80 tools. The number is a live stat, not the story.

Build a Product

16 TOOLS

Validate, scope, roadmap, ship.

Career Loop

8 TOOLS

Hunt, interview, negotiate, decide.

Run a Product

10 TOOLS

Experiments, metrics, competitors.

Run a Team

9 TOOLS

Retros, stakeholders, meetings, risk.

Money & Pitch

7 TOOLS

Invoices, pricing, runway, decks.

Personal & Dev

23 TOOLS

Focus, writing, code, everyday utilities.

Creative & Play

7 TOOLS

Pixels, beats, games, typing duels.

Current workspace

Search, filter, open recent tools, and jump into the latest experiments.

Explore the workspace →
( 03 )
Featured Experiments

The builds that stress-test the system.

These are useful tools, but they also expose what agent-built products need: touch polish, layout rules, persistence, and review.

( 04 )
What Broke

The honest part: volume is easy, reliability is not.

Agents can create breadth quickly. Product quality still needs constraints, QA, and human taste.

Desktop-first drift

Some tools loaded on mobile but opened with cramped panels, clipped actions, or unusable workspaces.

Technical pass, UX fail

A page can pass build and console checks while still feeling awkward under real thumbs.

Shared patterns matter

Without a toolbar, storage, routing, and mobile contract, every new tool invents its own mess.

Review has to feed the loop

Fixes are only valuable if they become rules for the next agent build.

Origin

It started with eight manual tools. Then the lab grew up.

The first eight tools were a forcing function: small, self-contained, free browser tools shipped in public. They proved the format worked.

The newer question is bigger: can an agent pipeline keep producing tools while the product system around it keeps learning? That is why this lives inside MVP Cafe as a Lab, not as a one-off tools launch.

The old tools are still here as the archive of where it began. The workspace is where the ongoing experiment continues.

Explore the lab.
Watch the system learn.

Some tools are polished. Some are deliberately rough. The point is to make the agent-building process visible.

Open the current workspace →
ONGOING EXPERIMENT · NOT A COMMERCIAL PRODUCT LAUNCH