Skip to content
Viberia Docs

HQ

HQ is the building that lands automatically when you create a project — it holds the project’s settings and houses the Dean who coordinates everything else inside the territory.

At a glance

Section titled “At a glance”
  • Default agents: Dean
  • Best for: Project setup, renaming, folder linkage, project-wide skills and MCP, deletion
  • Skills it ships with: None building-specific — the Dean can invoke any skill enabled at the project or user level
  • Place from: Auto-placed when you create a new project (not in the Building Type Drawer)

How It Works

Section titled “How It Works”

HQ is the only building Viberia creates for you. When you click New Project in the HudShelf, the new territory rises out of the land and an HQ drops onto it. Every other building is something you place yourself; HQ is given.

Two things live in HQ. The first is settings — the Building Window for HQ is the place to rename the project, link or change its folder_path, manage the skills and MCP servers that should be available to every agent inside the project, and (at the bottom, with confirmation) delete the project. The second is the Dean, a per-project coordinator who takes work from you or from the Chief of Staff and routes it to the right building inside the territory.

You can think of HQ as the project’s front door. When you don’t know where in a project to send a question, send it to the Dean. When you want to change something about the project itself, open HQ.

HQ cannot be deleted. Removing the project — from HQ’s own settings — is the only way to remove it.

Default agents

Section titled “Default agents”
  • Dean. The Dean is the per-project coordinator. They know what buildings exist in the project, which agents staff them, and what each is working on. Talk to the Dean when you want to delegate a task without picking the building yourself (“draft a PRD for X” — the Dean knows CodeForge has a Planner), when you want a status check across the whole project, or when you’re not sure who in the project owns a piece of work. The Dean does not write code or run loops directly; they hand work off and report back.

Configuration

Section titled “Configuration”

HQ’s Building Window exposes the project’s Project Settings panel in addition to the usual building-level controls:

  • Project name — rename the territory. The label above the land updates.
  • folder_path — link the project to a folder on your computer, change which folder it points at, or unlink. Every agent in the project treats this as its working directory.
  • Additional directories — extra directories agents in this project are allowed to read or write into beyond folder_path.
  • Project-wide skills — slash commands available to every agent stationed in the project. Layered on top of user-level skills from Settings.
  • Project-wide MCP servers — MCP servers available to every agent in the project. Layered on top of user-level MCP from Settings.
  • Delete project — at the bottom of the settings panel, with a confirmation step. Deleting removes the project from Viberia; it does not touch the on-disk folder.

HQ also exposes the standard building controls — the Dean’s prompt, model, additional directories specific to the Dean, and the Dean’s own skills/MCP — through the agent settings inside the Building Window.

Typical workflow

Section titled “Typical workflow”
  1. Click New Project in the HudShelf. Give it a name and (optionally) point it at a folder on disk.
  2. Viberia drops HQ on the new territory. Click HQ to open its window.
  3. Confirm the folder_path is correct and add any additional directories the project’s agents will need access to.
  4. Add any project-wide skills or MCP servers you want every agent in this project to inherit (for example, the linear MCP server if this is a project tracked in Linear).
  5. Close HQ and place the other buildings you need — CodeForge for engineering, KnowledgeBase for docs, and so on.
  6. When you have work for the project but don’t want to pick a specific building, message the Dean from HQ.

Limitations

Section titled “Limitations”
  • HQ is auto-placed and cannot be deleted on its own; removing the project removes HQ along with it.
  • Settings made in HQ apply only to this project. To set defaults that span every project, use the global Settings dialog (gear icon in the HudShelf).
  • The Dean delegates, but does not implement. For actual code, documents, or research output you’ll need the agents in the project’s other buildings.
  • Changing folder_path does not move any files on disk. It only changes which folder Viberia’s agents treat as the working directory.
Section titled “Related”