Generic & Custom Buildings
GenericBuilding is the user-configured building — a blank slate you can stock with whatever agents you want. The Building Creation Wizard is the seven-step modal that turns one of these into a reusable, named building kind you can place across projects.
At a glance
Section titled “At a glance”- Default agents: None (you configure them)
- Best for: Teams that don’t match any built-in kind — bespoke workflows, niche pipelines, single-purpose helpers, anything outside CodeForge / KnowledgeBase / etc.
- Skills it ships with: None by default — you pick which skills (if any) install when you author the building
- Place from: Building Type Drawer → GenericBuilding (for a one-off), or Building Type Drawer → your custom kind once you’ve saved one through the wizard
How It Works
Section titled “How It Works”A GenericBuilding starts empty. You drop it onto a territory, open its Building Window, and configure agents one by one — name, role, model, prompt, skills, MCP servers, additional directories — the same controls you’d see in any other building.
That’s fine for a one-off. But if you find yourself building the same custom team in three different projects, you want a saved building kind — a template you can place from the Building Type Drawer the same way you place CodeForge or Linear. That’s what the Building Creation Wizard is for. The Wizard walks you through naming, sizing, staffing, theming, and settings, then writes a TOML file describing the building. Once the file is saved, the building shows up in the Building Type Drawer and can be placed into any project.
The wizard supports two UI modes for the resulting building. Standard is what every built-in building uses: an agent list, a prompt section, skills, MCP, directories. Webpage mode replaces the standard panel with an embedded webview pointing at a URL you choose — useful when you want a building to be primarily a window into an external tool (the Linear building is a built-in example of the same pattern). You can pick mode in step 6 of the wizard.
You don’t have to use the wizard. You can also author building kinds by editing TOML files directly. The wizard is friendlier, but the file is the source of truth.
Default agents
Section titled “Default agents”GenericBuilding has no default agents — that’s the whole point. When you place a fresh GenericBuilding, the Building Window opens with an empty agent list and a prompt to add one. You configure:
- A role for each agent (the role name is what appears under their portrait — “Designer,” “PM,” “Customer Support Bot,” anything).
- A model per agent.
- A prompt per agent.
- Optional skills, MCP servers, and additional directories per agent.
When you save a GenericBuilding configuration through the Building Creation Wizard, those agents become the defaults for the new kind — every time you place that kind in a project, you get the same starting roster.
Configuration
Section titled “Configuration”Authoring a custom building via the wizard
Section titled “Authoring a custom building via the wizard”The Building Creation Wizard is a seven-step modal. Open it from the Building Type Drawer’s “Create New” entry, or from any GenericBuilding’s window if you decide partway through that you want to save the configuration as a reusable kind.
| Step | Name | What you do |
|---|---|---|
| 1 | Identity | Name, icon, short description. This is what shows up in the Building Type Drawer. |
| 2 | Size & Layout | How many tiles the building occupies on the map (1×1, 2×2, etc.) and footprint. |
| 3 | Agents | Add each default agent: role, model, prompt, optional skills/MCP. |
| 4 | Visuals | Sprite and color theme for the building. |
| 5 | Additional Settings | Defaults for additional directories, building-level MCP, building-level skills. |
| 6 | UI Mode | Standard (agent list + prompt panel) or Webpage (embedded webview at a URL you supply). |
| 7 | Review (TOML preview) | The wizard shows the generated TOML. Confirm to save. |
For the step-by-step walkthrough, see Building Creation Wizard.
Where the TOML lives
Section titled “Where the TOML lives”The wizard writes the building definition to a TOML file on disk. The exact location depends on whether you scoped the building to the current user or to a project, but the file is plain TOML — you can open it in the Toolbox’s Markdown Editor (or any text editor) and edit it by hand if the wizard didn’t expose a knob you need.
A typical edit-by-hand reason is fine-tuning agent prompts: the wizard’s prompt input is fine for a paragraph, but if you’ve built up a longer system prompt elsewhere, editing the TOML directly is faster than retyping into the modal. After editing, restart Viberia (or use the Settings → Skills → Reload equivalent for buildings) to pick up the change.
Webpage Mode
Section titled “Webpage Mode”If you pick Webpage mode in step 6, the resulting building shows an embedded webview as its main panel. You provide the URL. The agents you configured still exist and still have their own conversations — they’re accessible from a sidebar — but the webview is the primary surface. This is the same pattern the built-in Linear building uses, and it’s the right choice when the building is primarily a window into an external tool (a Notion workspace, a Grafana dashboard, an internal admin panel) and the agents are there to operate against what you’re seeing.
Typical workflow
Section titled “Typical workflow”- Place a GenericBuilding in a project to prototype the team. Add agents, set their prompts and models, install whichever skills and MCP servers they need.
- Use the building for a few days. Figure out what’s actually missing and what’s redundant.
- When the shape is right, open the Building Creation Wizard (from the Building Type Drawer, or from the GenericBuilding’s window).
- Walk through the seven steps. Name the building, set its size and visuals, copy in the agents you’ve been using, pick Standard or Webpage UI mode, and review the TOML.
- Save. The new building kind appears in the Building Type Drawer with the icon you chose.
- Place the saved kind in any project. The default agents come pre-configured; you can still tweak per-instance from the Building Window.
- If you later realize you want to change the defaults, edit the TOML file by hand and reload, or run the Wizard again and overwrite.
Limitations
Section titled “Limitations”- A GenericBuilding without configured agents is not useful — placing one and not staffing it leaves you with an empty room.
- The Wizard writes the building kind; instances of that kind are placed separately. Editing the kind does not retroactively change buildings you’ve already placed (those keep whatever per-instance settings they had at placement time).
- Webpage mode embeds external URLs in a webview. The same caveats as any embedded webview apply: the page needs network access, some sites refuse to load in webviews via
X-Frame-Options, and authentication may need to be re-done inside the webview. - Editing the TOML by hand bypasses the wizard’s validation. If you break the schema, the building will fail to load and you’ll see an error — the fix is to repair the TOML or re-run the wizard to regenerate a clean file.
- Custom buildings are local. They live in files on your machine; there is no built-in sharing of building kinds across users. If you want to share a custom kind with a teammate, share the TOML file itself.
Related
Section titled “Related”- Building Creation Wizard — the seven-step modal in detail.
- Buildings & Agents — what a building is and what an agent is.
- Skills (Slash Commands) — how to pick which skills install with a custom building.
- MCP Servers — how MCP scoping works at the building level.