Your first project
In short
Create a project from the projects list, give it your existing code or a written description as input, and open it — each project is an isolated workspace with its own repository, wallet draw, and stage.
A project is one application. It owns a repository, a stage, an architecture, and its own history of AI actions. Everything else in Sapilon hangs off it.
Create it
From the projects list, create a project and give it a name. Sapilon assigns a short project key — you will see it in URLs and in the name of the Git repository it provisions.
Give it something to read
The single biggest lever on quality is what you hand the agent at the start:
- An existing codebase — the usual case for modernization. Sapilon verifies it first and estimates up front how much of it can be rebuilt automatically.
- A prototype from a prompt-to-app tool. Export it and attach it.
- Documents — specs, screenshots, a database dump, an old requirements file. Attach them as artifacts; they become context the agent keeps rather than facts you retype.
- A written description, if you are starting from nothing.
Vague inputs produce a vague first pass, and the first pass is what everything else is built on. Spend the extra twenty minutes here.
Open the studio
Opening a project launches the project workspace — the studio — where the code tree, the agent, tasks, artifacts, and the dashboard live. The projects list stays the cross-project view: create, open, archive.
What happens on day one
The project starts in Design. Nothing is deployed, nothing costs AWS money yet, and the agent works against mocked data while the shape of the app is settled.
Next: The four stages · Your first Ask