Create an Arena project
EnterpriseCreate an Arena project in the dashboard and open it in the project editor.
Prerequisites
Section titled “Prerequisites”enterprise.enabled=truein your Helm values. See Install a license.- Editor access to the workspace.
- For a template start, at least one template registry. See Create template sources.
Open the new-project page
Section titled “Open the new-project page”- In the sidebar, choose Projects.
- Click New project.
The page lists templates under Start something new, and three other starts under Or start without one.
Start from a template
Section titled “Start from a template”- Find a template. Narrow the grid with the Tags filter or Search templates…, then click its card.
- On the Values step, set Project name and the template’s variables, then continue to Review.
- On the Review step, browse the files the template will write. Nothing is created yet.
- Click Create project.
If the grid shows No templates yet, add a registry under Settings > Registries.
Start from a blank project
Section titled “Start from a blank project”- Click the Blank project card.
- Enter a Project name and, optionally, a Description.
- Click Create project.
The project starts with empty prompts/, providers/, scenarios/ and tools/ folders and a config.arena.yaml with no prompts, providers or scenarios.
Start from a git repository
Section titled “Start from a git repository”Click the Link a repository card. See Work on an external repository for the Connection and the branch workflow.
Start with the AI builder
Section titled “Start with the AI builder”Click Generate with AI. It needs the builder installed in the workspace. See Generate a project with the builder.
Verify
Section titled “Verify”After Create project, the dashboard opens the project in the editor with its files in the tree.
Troubleshooting
Section titled “Troubleshooting”A toast reports the project as created but unpublished
Section titled “A toast reports the project as created but unpublished”The toast title is Project created, not yet published. The new project’s files did not reach the project’s main branch. The files are in your working clone. Commit and sync them from the Source control tab in the editor.