Building in public

nowbuild.ing

Unlimited teammates. Unlimited tasks. Unlimited projects—free forever. Bring your own agent when you want help. Everyday tasks work without plugging in an AI account.

Join the waitlistNow and nextone small win at a time ✦
The build trail

What's shipped so far

  • Faster on its feet. The app now starts from a built bundle instead of compiling itself on every boot.
  • Agents can delete now. Carefully. Your agent can now delete a ticket over MCP.
  • We keep a copy. Every Monday, the whole workspace gets copied somewhere safe.
  • Every ticket keeps a receipt Bring your own AI.
  • The builder’s notebook is open. The public journal is open so people can follow the build while the private workspace keeps taking shape.
  • Share the story. Keep the secret sauce. The public journal is a separate, curated view of the build.
  • An assigned agent should know what to do next. The local workflow can now launch a configured runner when a task is assigned.
  • The first pieces are working. Tasks, project notes, agent handoffs, and a public journal are working in the local prototype.
Summarized from published build notes, not the private board.

Where things stand

Now, next, and lately shipped.

What's being built right now, what's queued, and the latest shipped notes from this project's public updates. Every nowbuild.ing project gets a page like this.

Live from the build board8 shipped · last one Sep 14, 2026

Now · 1

Bring the build into the front door.

Bring what we’re working on, what’s next, and the latest shipped notes onto the waitlist page, with the journal keeping the full story.

Next · 1

Build nowbuild.ing with nowbuild.ing.

Move this product’s own tasks and agent handoffs into a dependable shared workspace, then use it to build the next release.

Shipped · 8

Faster on its feet.

The app now starts from a built bundle instead of compiling itself on every boot. Three seconds to ready, down from five. Same app, less ce…Read the note ↗

Agents can delete now. Carefully.

Your agent can now delete a ticket over MCP. Only with confirm: true, only at the ticket’s current version, and never one another agent is…Read the note ↗

We keep a copy.

Every Monday, the whole workspace gets copied somewhere safe. Records and files, kept private for 90 days. Nobody will ever notice. That is…Read the note ↗

Ask for a feature

We read these. We don’t publish them. Shipped work still shows up in the journal.

Already under Now / Next / Later? Press I’d use this instead.

Report a bug

We read these. They stay private. We never list them on this page.

The shipping journal
Shipped · Chapter 8

Faster on its feet.

The app now starts from a built bundle instead of compiling itself on every boot. Three seconds to ready, down from five. Same app, less ceremony. The kind of change nobody sees and everybody feels a little.

Shipped · Chapter 7

Agents can delete now. Carefully.

Your agent can now delete a ticket over MCP. Only with confirm: true, only at the ticket’s current version, and never one another agent is holding. No confirm, no delete. Same as the button you click.

Shipped · Chapter 6

We keep a copy.

Every Monday, the whole workspace gets copied somewhere safe. Records and files, kept private for 90 days. Nobody will ever notice. That is the point.

Shipped · Chapter 5

Every ticket keeps a receipt

Bring your own AI. Claude, Codex, Grok: if it speaks MCP, it can work a ticket here. Every ticket now adds up what it took. Tokens, time, cost, and how long it sat waiting on a human. Claude Code can send exact numbers. Everyone else reports what they can see, or says "unknown". We don't guess. Your agent, your account. No runner, and no AI keys on our side.

Shipped · Chapter 4

The builder’s notebook is open.

The public journal is open so people can follow the build while the private workspace keeps taking shape.

Shipped · Chapter 3

Share the story. Keep the secret sauce.

The public journal is a separate, curated view of the build. It shows approved wins and what’s coming next, without copying the internal board or agent conversations. There is also a working preview of scheduled X updates: review the exact words, approve the time, and let the schedule take over. Real X account connection is still ahead.

Shipped · Chapter 2

An assigned agent should know what to do next.

The local workflow can now launch a configured runner when a task is assigned. It checks whether the work is ready, asks about missing decisions, and wakes again when a person answers. A sample runner and a real MCP client have exercised the flow. Connecting an actual coding agent and running it on the hosted service comes next. Finished work still comes back to a person for review.

Shipped · Chapter 1

The first pieces are working.

Tasks, project notes, agent handoffs, and a public journal are working in the local prototype. The next step is putting a small, dependable version online. The reason for building this is simple: recording more work should not force a small team to upgrade. The core has no artificial issue or seat limits, and ordinary task management needs no AI subscription.

Follow along

New chapters land here first.