Skip to main content
All use cases

Use case

Build the internal tool nobody has time to build

Describe the spreadsheet your team has outgrown. An agent turns it into a real app while you watch, and asks before it does anything you can't take back.

Why internal tools are a good first app

Internal tools are the software every team needs and no roadmap has room for: the approvals tracker, the inventory sheet with too many tabs, the dashboard someone rebuilds in a slide deck every Monday. The requirements are clear to the people who use them, which is exactly what makes them easy to describe in a sentence or two.

Trackers

Escalations, hiring pipelines, vendor renewals — a table, filters, a detail view and a status field.

Admin panels

Forms over your data with validation, so edits stop happening in a shared spreadsheet.

Dashboards

Charts over the numbers you already collect, without waiting on a BI request.

Calculators

Pricing, quoting and capacity tools that encode the rules someone keeps in their head.

How it works

  1. Describe the tool in plain language. The agent scaffolds a real React and TypeScript project.
  2. Every file it writes hot-reloads into a live preview beside the chat, so you see the tool take shape and correct it as it goes.
  3. Shell commands, deletions and deploys pause for your review — from the builder or from your phone.
  4. Publish to a live URL, or push to GitHub and hand the code to your engineers.

Why the approval gate matters for team software

A tool your team relies on is a tool you can't afford to have quietly broken. Every turn the agent takes is committed as a version you can roll back in one click, and nothing that leaves the sandbox happens without someone saying yes. You get the speed of an agent without handing it the keys.

Do I need to know how to code?

No. You describe what you want and review what the agent proposes. The full source is beside the chat if you or an engineer want to read it.

Can engineers take it over later?

Yes. It is an ordinary React and TypeScript project. Push it to GitHub and work on it like any other codebase.

What does the agent ask permission for?

On the default Guarded level, it edits files freely but stops before running a command, deleting a file or doing anything that leaves the sandbox.