Projects and the workspace
Create a Builder project, link its repository, and work in the browser workspace — panels, terminal tabs, modes, live preview and annotations.
A Builder project is one client website: its URL, its brief, its repository and its deployment target. Open one and you get a workspace in the browser — file tree, editor, terminal tabs, live preview, tasks, client requests and project settings in a single tab.
The roster lives at BuilderAll Projects. The workspace is one click in from there.
Before you start
Listing repositories needs the per-tenant GitHub App installed for the workspace, which is an owner action. Terminal sessions, live preview and live git additionally need the Builder terminal service configured for your deployment.
Create a project
Click New project
From All Projects.
Enter the website URL and a brief
The URL field takes a plain host, for example example.com. The brief is
the description the AI reads.
Add goals, constraints and context
Anything the AI should know before it touches this site.
Choose the deployment
GitHub deploy, FTP deploy or Bluehost.
Pick the repository
Search the installation's repositories and choose the owner/repo you want.
GitHub Not Connected means the app has not been installed for the
workspace yet.
FTP settings are configured per website inside that project's settings, not globally.
The roster
| Setting | What it changes | Default |
|---|---|---|
| All status | Filters the roster to Active or Archived projects. | — |
| All deploys | Filters by deployment target or state, for example Bluehost or Deploying. | — |
| Recently updated | Orders the roster by last change. | — |
| Grid view / Table view | Switches the roster layout. | — |
| Deploy | Triggers a deployment for the selected projects. | — |
| Backup | Backs up the selected projects. | — |
| Delete projects | Removes the selected projects. Destructive and not reversible. | — |
Bulk delete does exactly what it says
The toolbar action is labelled Delete projects and it removes every project you have ticked. Check the selection count before you confirm — a roster filter can leave rows selected that you can no longer see.
Inside the workspace
The left activity bar switches panels.
| Panel | What it is |
|---|---|
| Code Editor | The file tree and editor, with tabs |
| Components | Reusable components for the project |
| Images | The project's images, including those the blog writer may use |
| Tasks | Work items for the project |
| Requests | Client requests that need Builder work |
| Feedback | Annotations and feedback collected on the preview |
| Brief | The project brief the AI reads |
| Preview | The live preview of the site |
| Vercel | Hosting state, on projects linked to a Vercel project |
| Prompt Library | Your saved prompts, in reach of the terminal |
| Project Settings | Per-project configuration, including FTP |
| Setting | What it changes | Default |
|---|---|---|
| Zen mode | Hides the surrounding chrome for a distraction-free workspace. | — |
| Side panel | Shows or hides the auxiliary panel. | — |
| Terminal: New Claude tab | Opens a terminal tab running Claude. | — |
| Terminal: New Codex tab | Opens a terminal tab running Codex. | — |
| Workspace: Build (code) | Switches the workspace into build mode. | — |
| Workspace: SEO | Switches the workspace into SEO mode, which is where SEO briefs and batch fix prompts land. | — |
| Preview: Pop out to a window | Opens the live preview in its own window. | — |
| Preview: Annotate a website… | Starts annotation on the previewed page. | — |
| Deploy to Bluehost / Deploy to Vercel | Triggers a deployment for the project's configured host. | — |
Dormant panels are telling you the truth
Terminal, live preview and live git show a dormant state when the terminal service is not configured. They are not broken and there is no setting in the workspace that turns them on. Components (no access) is different — that is your permission, and an owner can grant it.
Live preview and annotations
The preview can be opened full-tab in a sandboxed viewer with reload and annotation tools.
Open the Preview panel
Open the full-tab viewer
Or pop the preview out into its own window.
Annotate the page
Marks you leave come back into the workspace as feedback.
Annotation tools need the preview bridge to connect. Until the previewed page connects, the tools say so rather than silently doing nothing.
The SEO context bundle
When you open a project terminal, a set of SEO context files loads with it, compiled from Zyan's SEO knowledge base and this project's strategy. You can switch it off under Project settingsTerminal AI with the SEO context for Claude control.
Prompts built by the Use with Claude composer carry their own facts, so they do not depend on that bundle being loaded.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| GitHub Not Connected in the repository picker | The GitHub App is not installed for the workspace | An owner installs it on the GitHub tile in Settings → Integrations |
| No repositories listed | The installation does not have access to them | Adjust the installation's repository access on GitHub |
| The terminal tab will not open | The terminal service is not configured for this deployment | Ask your platform operator |
| Annotations are unavailable | The preview bridge has not connected | Wait for the previewed page to connect, or reload the preview |
| The Vercel tab is missing | The project is not linked to a Vercel project | Link it — see GitHub and Vercel |
| Components (no access) | You lack the components permission | Ask an owner to grant it |
| FTP settings are nowhere on the roster | FTP is per website | Open that project's settings |