Projects
A project is one application you are building in Workbench. This page covers creating and opening projects and finding your way around one.
Creating a project
From the Projects area you create a new project by giving it a name and a description, and choosing its type:
- Conversational — build the application through a chat with the assistant. The quickest way to get started. See Building Conversationally .
- Mushin — build the application as a versioned, neuro-symbolic specification. The deliberate way to build something larger. See The Neuro-Symbolic Approach .
The type shapes how the project’s editors and explorer behave, so choose the way of working that fits the job. You can also edit a project’s name and description later.
Opening a project
Opening a project loads it into the Workbench. Because a project is version-controlled, you open it at a branch — usually the main line of development. Opening resets the workspace to that project and rebuilds the Explorer around it.
The project explorer
The Explorer shows your open project as a tree. What you see depends on the project type, but generally includes:
- The project itself at the root
- The BrainChain pipeline that orchestrates generation
- Branches, each expanding to its commits — the version history
- The design streams where the work happens (for a Mushin project, organized by feature, each with its own blackboard)
- Once you have generated the application, an Applications section showing the generated data model (tables, fields, and relationships) and pages
The Explorer is your map of the project: its history on one side, its design in the middle, and its generated shape once it exists.
Branches and history
Every project is versioned. A branch is a line of development, and each change is captured as a commit — an immutable snapshot you can review or return to. Working on branches lets you develop a change in isolation and keep a full history of how the application’s design evolved. Branch and commit management is covered in Design Streams & Version Control .
Related pages
- Building Conversationally — the conversational project type
- The Neuro-Symbolic Approach — the Mushin project type
- Design Streams & Version Control — branches, commits, and history