Skip to content

← Learning paths / Build and ship your first app

Lesson 1 of 9

Create your first project

A project is where your app lives: its code, its tickets and its live address. You describe what you want, a team of AI agents does the engineering, and Chipp hosts the result.

How a project works

Four steps, from your first sentence to a running app.

Step 1

Create a project

Describe what you want in plain words, or open New project and pick a template. Each project gets its own private code repository, started from the platform template.

Step 2

Open a ticket

A ticket is how you ask for work, like “add a login page”, “fix the bug where checkout fails” or “switch the homepage hero to a video”. Chipp sends each ticket to an agent.

Step 3

The agent does the work

In its own isolated workspace, the agent plans the change, builds it, reviews it, checks it for security problems and writes up what it changed. Follow along in the Tickets view, or close the tab and come back later. Every step is saved.

Step 4

Chipp puts it live

When the agent’s work is merged, Chipp builds your app again and rolls it out at the same live address, with a few seconds of overlap. New projects release every merge by default.

Where things live

Once you have a project, these are the places you will use most.

Questions

Do I need to install anything?

No. There is no editor to install and no build system to set up. The agents work in their own isolated workspace, and Chipp rebuilds and rolls out your app after every merge.

Does my app have to include AI?

No. The AI does the building. It does not have to be part of what you run. A ticket can produce a web app, an API, a scheduled job or a data pipeline with no chatbot inside it.

Can I leave while the agent works?

Yes. Every step is saved, so you can close the tab and come back later to see where the ticket stands.

Is my project’s code private?

Yes. Each project has its own private repository.