Quickstart

This walkthrough takes you from a new account to a live, deployed project. You’ll need a Cloudflare account — the free tier is fine, and you can create one from inside step 2 without leaving the flow. A GitHub account is optional; step 3 explains what you get by connecting one and what you give up by skipping it.

1. Sign in

Open the console and sign in. Typillar uses your email to identify you; the accounts that do the real work are connected in the next steps.

If you sign up with an email and password, you’ll confirm your address from a verification link first. Signing in with GitHub or Google skips that step. Either way, you land in a personal organization — invite people later to turn it into a shared one.

2. Connect Cloudflare

Typillar builds onto your Cloudflare account, so it needs permission to create and deploy resources there. From the console, choose Connect Cloudflare and authorize the connection.

Don’t have a Cloudflare account yet? Don’t go make one first. Choose Connect Cloudflare anyway: the screen it opens has a Sign up link under the login form that carries the connection with it, so signing up there drops you back in the console already connected.

This is what lets Typillar run Workers, create databases, and publish your project to a live URL. It’s the one connection Typillar requires.

Cloudflare permissions are granted incrementally — the first connect covers deploying and running the agent’s model, and later, the first time a feature needs a database, file storage, email or a custom domain, you’ll be sent back to Cloudflare’s screen to grant that one permission. That second screen is expected, not a problem. For the exact scopes, see Permissions & access.

3. Connect GitHub — or skip it

Once Cloudflare is connected, the console offers Connect GitHub. Authorize it and every change an agent makes lands in a private repository you own, as a normal commit — so your source of truth is a repo you control.

It’s genuinely optional, and there’s a Skip for now button. What skipping costs you: the repo is the version store. Without it, a project has no version history and nothing to Restore to. (Deployments can still be rolled back — that happens on Cloudflare.) You can connect GitHub later from Settings → Connections, and history accumulates from that point on.

The GitHub grant is account-wide, not per-repository — see Connect GitHub for what that means and how to bound it.

4. Pick a model (or take the default)

Typillar generates code with a model, and that model runs on your side, not ours — it’s reached through the Cloudflare connection you just made, so there’s no key to paste and nothing to enable.

The model selector sits next to the composer. Leave it alone and you build with the default, @cf/openai/gpt-oss-120b, on your Workers AI allowance. Or pick another from the catalog — including Claude, GPT or Gemini, billed to credits on your own Cloudflare account.

5. Type your first idea

In the console, describe what you want in one sentence. For your first project, keep it small and concrete:

A landing page for my newsletter with an email signup box.

You can also paste or drop in a screenshot or a PDF — a mockup to match, a spec to read from — if the model you’re on reads it.

The agent turns this into a tracked ticket and starts building it right away — you don’t have to approve anything first.

6. Answer if it asks

As it builds, the agent may ask you a question when a decision is genuinely yours to make — where the confirmation email should come from, say. Answer in the thread and it picks up right where it paused. If nothing needs deciding, it just builds.

7. Ship it

You get a preview to click through, and — if GitHub is connected — the source is committed to your repo as it’s built. When you’re happy, say deploy it (or click Ship): you’ll get a live URL and an entry in the project history, with roll back available from the start.

You’re up

That’s the whole loop: type → build → ship. From here:

• Learn the model in What you own.
• Add to your project in Your first project.
• Understand reversibility in Deploys & rollback.