GUIDE

How Bitbytec works

You stay in the chat you already use. The Mac is the gate. Nothing is written until you accept.

A laptop on a sunlit desk, screen filled with blocks of cyan, amber, violet and green, colourful houses outside. — The planning stays in the chat already open on your computer.

Describe it in the chat you already use.

Open ChatGPT, Claude, or Grok. Say what you want made: a phone app, a page, a small API, or a tool for your team. That chat can search, ask a follow-up, and turn the idea into a blueprint.

Bitbytec does not replace that chat, and it does not sell you a model. The planner is the assistant you already talk to. The Mac app has to be open, because the blueprint is delivered to this computer, not to a shared account in the cloud.

The blueprint waits until you accept.

A hand reaching toward three glowing cards on a wooden desk in daylight. — Accept is a real choice on the Mac. Decline, or ten quiet minutes, and the plan stops.

The blueprint shows the title, the summary, and the screens it intends to make. You accept or you decline. If you do nothing for ten minutes, the offer expires and nothing is written.

Accept is the only start. The chat cannot quietly begin a build. If the plan changes after you accepted, the Mac refuses it, because the words you approved no longer match.

Your coding agent builds.

A laptop and a phone on a white desk, both showing the same sunrise. — After you accept, the agent already on your Mac writes the project. You watch the preview.

The builder is one you already have: Claude Code, Codex, Cursor, or Grok. Bitbytec finds it. If more than one is installed, it uses the one you prefer. If none is installed, it tells you how to get one. It does not install a coding agent for you.

On accept it writes a starter in a folder under your home directory, then asks that agent to keep building the same pack. An app starts as Flutter. A website starts as a page. A backend starts as a small server. A team tool starts as one page with a short readme.

You watch a preview, not an editor.

Two laptops on a pastel table, joined by a ribbon of green and violet light. — The chat and the Mac stay on this computer. There is no shared Bitbytec login between them.

The front of the app is the desk: what was understood, what you approved, what is building, and a preview when a real screen exists. Studio, the fuller editor, stays one click away if you want it. It is not the front door.

Next: what Accept is asking, or how to connect the chat.