Projects | Viberglass Docs

A project is your unit of work in Viberglass. Each project is bound to a single source code repository and owns its own tickets, jobs, claws, integrations, and prompt templates.

Creating a project

From the dashboard sidebar, click New Project under the Projects list. The form asks for:

Project Name — what the project is called across the platform.
Ticketing Integration — which external ticketing system, if any, should sync tickets with this project. If you have no integrations configured yet, the dropdown is disabled and Viberglass acts as your sole ticketing system. You can always link an integration later.
SCM Execution — the repository configuration that clankers use when running jobs. This is where you tell Viberglass which repo to clone and which branch is the merge target.
Enable Auto-fix — when on, the platform allows AI to automatically suggest and create PRs for inbound bug reports.

Even if you skip Ticketing Integration, you still need a repository for clankers to clone.

SCM execution settings

When you have a GitHub integration linked (see Integrations), you can fill in:

SCM Integration — pick the GitHub (or other SCM) integration to use.
Source Repository — the repository cloned by clankers when executing jobs, e.g. https://github.com/your-org/your-repo.
Base Branch — the default branch used as merge target and checkout base. Defaults to main.
Pull Request Repository (optional) — override the PR destination repository. Leave empty to push PRs back to the source repo (this is the normal case for non-fork workflows).
Pull Request Base Branch (optional) — override the PR base branch. Leave empty to use the same base branch.
Branch Name Template (optional) — controls how clankers name their fix branches. Available placeholders are {{ ticket }}, {{ original_ticket }}, and {{ clanker }}. The default template is viberator/{{ ticket }}.
Integration Credential (Recommended) — pick a credential previously stored on the integration (for example, the GITHUB_TOKEN secret). The clanker uses this credential when cloning, pushing, and opening PRs. You can manage credentials from the integration's detail page.

If you don't link an SCM integration, the SCM fields stay disabled — the clanker has nowhere to push to, so jobs cannot complete.

Auto-fix

The Enable Auto-fix switch lets Viberglass automatically run the full Research → Planning → Execution chain whenever a new ticket arrives from a webhook. With auto-fix off, tickets stay in open state and require a human to start the workflow.

Auto-fix is most useful for inbound integrations such as GitHub Issues, where you want every labelled bug to be picked up immediately.

Once a project is open, the sidebar switches to a per-project view with Home, Dashboard, Tickets, Claws, Jobs, and Settings.

Settings has three sub-pages: Project, Integrations, and Prompt Templates.

Per-project settings pages

Project

The same form you used to create the project. Deleting a project is permanent — every ticket, job, claw, and document attached to it is removed.

Integrations

This sub-page lists which platform integrations are linked to the project and which one is marked primary for ticketing or SCM. Use it to add a new link or to switch primary integrations. Integrations themselves are configured globally under Platform → Integrations.

Prompt Templates

Every workflow phase is driven by a prompt template. Viberglass ships with sensible defaults, but you can override them per project if you want, for example, your planning agent to follow a particular structure or your research agent to write longer summaries.

The page lists each editable template:

Research Task — used when running ticket research.
Research Revision Task — used when re-running research after you request changes.
Planning (with Research) — planning prompt when a research document is available.
Planning (without Research) — planning prompt when there is no research document (for example, when you start a ticket directly in Planning).
Planning Revision Task — used when re-running planning after you request changes.
Development Task — the prompt used during the Execution phase.
Claw Scheduled Task — the prompt used by scheduled claws.

Click any template to expand it and edit the body. Leave a template unchanged to keep using the system default.