AigentFlow Desktop is in pre-release. This documentation reflects the current build and will change before general availability.
Getting started
Your first project
Two ways to bring work into AigentFlow. Point it at a folder you already have, or walk the wizard and let it build the project up with you.
Adding a folder you already have
The fastest route. + Add Project opens a folder picker and registers the folder as a project. No wizard, no questions. Use it when you already know the codebase and just want a session on it.
The wizard
+ New Project opens an eight-stage wizard. It works for a new idea and for a repository that already exists, and it ends with a project that has written down what it is, what it needs and how it will get there.
| Stage | What happens |
|---|---|
| Initiate | Pick a project type and name it. New projects only |
| Qualify | A short conversation that turns your description into a brief, and proposes a team |
| Discover | Questions tailored to the project type. For an existing repository it reads the manifests and README first and offers you what it inferred |
| Map | An agent reads the high-signal files and writes a map of the codebase |
| Research | Builds the working context for the project |
| Require | Extracts numbered requirements, each with how to verify it |
| Plan | Turns the requirements into phases and tasks |
| Ready | The plan is approved and the project is set up |
An existing project starts at Qualify rather than Initiate. If it has no source code in it, the Map stage is dropped, so a freshly scaffolded project never sees it.
There is no skip. Each stage unlocks its Continue button when what it needs is there. If you come back to a half-finished project, the wizard looks at what has already been written and resumes at the right stage.
What you end up with
The wizard writes real files into the project, not database rows. You can read them, edit them and commit them.
CLAUDE.md project instructions the agent reads .aigentflow/ PROJECT.md what this project is STATE.md where the work has got to DISCOVERY.md what was established up front CODEBASE_MAP.md the shape of an existing codebase CONTEXT.md the working context DECISIONS.md what was decided, and why REQUIREMENTS.md numbered requirements with verification ROADMAP.md phases and tasks ARCHITECTURE.md how it is put together
Requirements are yours to edit at any point. Ticking one off moves it to an out-of-scope list rather than deleting it, and every edit rewrites the file immediately.
Researching a project you already added
A project added straight from the folder picker can still be taken through the research stages later, from the Research button on the project. It opens in its own tab, so a long research run does not tie up the session you are working in.