Generative UITools4U
A Canvas of Widgets You Order in Plain English
An infinite canvas where an AI agent turns a plain-English request into a live widget wired to your own data.
- DetectChecks for missing connectors before generating
- ResearchAgent pass with search, extract and weather tools, up to 5 steps
- SpecStructured pass returns a Zod-validated ToolSpec
- RenderNative primitives or a Sandpack React sandbox
- RefreshTrigger.dev reruns scheduled tools
Rochester, N.Y. Tools4U is a canvas for tools you make by describing them. Ask for "a card that summarizes my unread emails" and an agent builds that card, drops it into a free slot on an infinite grid and can refresh it on a schedule. Everything you make lives side by side, like a desk covered in sticky notes that actually do things.
Generation runs in two passes with the Vercel AI SDK. The first pass is agentic: the model can search the web with Tavily or Exa, pull pages with Firecrawl or check the weather, for up to 5 steps. The second pass is strict. It has to return a ToolSpec that passes a Zod schema, covering what kind of tool it is, its layout and where its data comes from. Splitting it this way lets the first call wander and keeps the second call honest.
Splitting it this way lets the first call wander and keeps the second call honest.
A ToolSpec renders one of two ways. Simple tools use 8 native primitives I wrote, like MetricCard, ListFeed and ChartBlock. Anything custom runs as React inside a Sandpack sandbox. Before generating, a small pre-pass checks whether the tool needs an integration you haven't connected and asks you to connect it first through Nango OAuth. Edits work the same way: the model gets the existing spec and changes it in place.
Underneath sit Supabase auth, Postgres with row-level security and Realtime, a Trigger.dev job every 5 minutes that refreshes scheduled tools, and your own Anthropic or OpenRouter key, encrypted on the server. The canvas is React Flow, with drag, resize, recolor and skeleton cards while a tool is being made.
It builds clean, but I haven't run it end to end with real keys yet, and per-provider data shaping for the connectors isn't written. It overlaps with SecondScreen on purpose. Both ask what happens when software is something you describe, and this one answers on a big screen instead of a phone.