Creating a project
Open Settings → Projects and choose New project. A project needs:- Workspace — the active workspace it belongs to.
- Name — its display name (up to 120 characters).
- Slug — the lowercase, hyphenated identifier used in dashboard URLs (
/org/<org>/ws/<workspace>/prj/<project>/…).
default, prompts, tools, and settings) can’t be used as a slug, because they collide with dashboard routes. Creating a project requires the project:create permission in the target workspace.
A project’s slug is fixed once it’s created. You can rename a project later, but the slug stays the same so existing links and integrations keep working.
Managing a project
Each project row on the Settings → Projects page exposes its actions, gated byproject:update (rename, archive) and project:delete (delete).
- Rename — changes the display name only; the slug is untouched.
- Archive — hides the project and makes its data inaccessible without deleting it. Archiving is reversible: restore the project to bring it back.
- Delete — permanent. The dialog summarizes what will be removed (prompts, tools, API keys) and requires you to type the project’s name to confirm.
Project settings
What a project holds is managed from its own pages in the dashboard:- Chat Prompts and Skills, under Build in the sidebar. See Prompt management and Skills.
- Sessions, under Observe, the page a project opens on. See Sessions.
- Environments, under the project’s Settings → Environments. See Environments.
Next steps
Environments
The named slots a project’s prompts and skills publish to.
Sessions
The coding-agent sessions uploaded to a project.