Projects and History
Projects, conversations, and history
DeplAI keeps generated applications in **conversations** under DeplAI Agent. The rest of the workspace organizes **projects** around connected GitHub repositories or ZIP uploads.
DeplAI keeps generated applications in conversations under DeplAI Agent. The rest of the workspace organizes projects around connected GitHub repositories or ZIP uploads.
Conversations and builds
| Concept | Meaning |
|---|---|
| Conversation | One product thread: request, answers, builds, versions |
| Build | One attempt to create, retry, fix, or modify the application |
| Application version | Saved source snapshot from a build or repair |
| Preview | Temporary running application for a version |
| Checks | Validation DeplAI ran for that version |
| Activity | Operational progress in Logs |
Select a previous build to inspect its files and checks. Starting Modify uses a Ready version; it does not delete older builds.
Projects
A project in the workspace picker is a connected repository or uploaded ZIP used by Security Agent, Deploy, UI/UX customizer, and related services. Application-builder conversations are listed under DeplAI Agent rather than as those repository projects.
Organization membership, when you use it, scopes who can access shared workspace resources. Generated application versions are associated with the conversation and the signed-in account (and organization context when billing and access require it).
Temporary environments versus saved source
Application builds run in isolated temporary environments. Those environments are disposable.
Saved application source is stored separately from temporary build environments. After a temporary build finishes or a preview stops, saved versions remain for inspect and download.
Application builds do not receive production deployment credentials.
Related: Your workspace | Application versions | Security and data