The generation flow
By the end of this page you will understand each phase qRaptor goes through to turn your prompt into a working app, and how to iterate on the result.
Prerequisites
- An app generation started (Create an app).
The pipeline
qRaptor follows a fixed pipeline for every app:
Prompt → Requirements → App Graph → Code → Auto-Fix → Iterate
The workspace shows your progress with phase labels as generation runs:
| Phase | Label shown |
|---|---|
| Reasoning over your prompt | Understanding |
| Reviewing requirements | Requirements |
| Planning the app structure | Designing |
| Setting up the data model | Database Setup |
| Writing the app’s code | Coding |
| Reviewing generated code | Reviewing |
| Running quality gates | Quality Gates |
| Merging changes | Merging |
| Building the app | Building |
| Diagnosing a build issue | Diagnosing |
| Applying a fix | Fixing |
| Generation finished | Complete |
Requirements
Before writing any code, qRaptor turns your prompt into a Requirements Specification — a structured breakdown of entities, workflows, and screens it plans to build. This appears under the Requirements sub-tab of App Details.
If your prompt was ambiguous, qRaptor asks clarifying questions inline. Answer them, then:
- Click Approve & Generate to proceed with your answers.
- Click Accept Defaults & Approve to accept qRaptor’s suggested defaults where you haven’t specified.
- Click Reject (a reason is required) to send the requirements back for revision.
Rejecting with a specific reason (e.g. “add a customer-facing order history screen”) produces a better second draft than a generic rejection.
App Graph
Once requirements are approved, qRaptor generates the App Graph — a visual canvas of the app’s structure, with UI, Backend, and Shared nodes. You’ll see progress titles like “qRaptor is Analyzing Requirements”, “qRaptor is Generating App Graph”, “qRaptor is Modeling Data Layer”, and “qRaptor is Building App Graph” while this runs.
The graph is viewable afterward under the Graph sub-tab of App Details — see Review app details.
Code
qRaptor then generates working code from the app graph. You can inspect it in the Code tab (a Monaco-based editor) at any point, including while generation is still running.
Auto-Fix
If a build fails, qRaptor automatically diagnoses and fixes the issue without you needing to intervene:
- Diagnosing — qRaptor analyzes the root cause of the build failure.
- Fixing — qRaptor applies a targeted fix and rebuilds. Chat messages like “Fixing the issues I found…” and a completion summary (e.g. “3 fixes applied”) appear in the chat panel.
Auto-Fix runs automatically — you don’t need to trigger it. It only shows up in the chat log for visibility.
Iterate
The Chat panel on the left side of the workspace is always available, even after your app reaches Preview Ready. Type a request in the Describe changes… box to ask qRaptor for changes — a new fix, a new feature, a UI tweak.
Each round of changes is tracked as a new version (v1, v2, …) in Version History, along with its status (e.g. Success), file count, and credit cost. Version History also totals the credits used across all versions.
You can also embed an existing agent into your app — as a chat widget, a chat page, or a triggered action — from this same chat composer. See Add AI integration.
Reverting to a previous version
Open Version History and revert to any earlier version. Reverting doesn’t create a new version — it moves the Current marker back to the version you picked, and any later version is marked Superseded rather than deleted. The chat log records a “Reverted to v1” marker (or whichever version you picked) at that point.
Superseded versions stay in your history; nothing is lost. Your next follow-up after reverting is what creates the next sequential version — for example, if you revert from v2 to v1, that revert doesn’t consume a version number, but your next requested change becomes v3.
Because a revert is just another version, you can always revert again later if you change your mind — nothing is destroyed.
Common issues
- Generation stuck on Building — Large or complex prompts can take longer to build. If it fails, Auto-Fix will kick in automatically.
- Repeated Auto-Fix loops on the same issue — Describe the problem directly in the chat panel instead of waiting for another automatic pass.
- Requirements keep looping — Reject with a specific, detailed reason rather than a general one.