Dashboard

The Dashboard is the home screen for the open project. It shows where the project stands, connects your coding agent, and holds the project's team, enforcement, and settings controls.

Where to find it

Select Dashboard at the top of the sidebar, or press Ctrl+1. The panel has 5 tabs: Overview, Agents, Team, Enforcement, and Settings.

The Dashboard keeps your last tab while the app is open. Opening or switching to a different project always lands on Overview, so you see that project's setup prompts first.

If no project is open, the Dashboard shows no tabs. It shows a Welcome to Vibeless message and an Open Projects button, which takes you to the Projects tab of the Account panel. Create or import a project there.

Overview

Overview is the status page for the project. The cards appear in this order.

Agent not connected banner

A new project shows a red Agent not connected banner until you connect an agent. An agent is the AI coding tool (Claude Code, Cursor, Codex) that reads your project through MCP.

Select Connect Agent to open the setup wizard. The wizard also opens on its own the first time you view the project's Overview in an app session. If you close it, it does not reopen until you restart the app, but the banner stays. The banner clears when you finish the wizard (with Done or I'll do it later) or when you install Claude Code, Codex, or Cursor from the Agents tab.

Get Started

The Get Started card appears while the project has no context nodes. A context node is one entry in the spec map that agents read (a spec, a rule, or a standard). See Context Editor and Search. The card offers 2 ways to fill the map:

• Import from Repository opens the import flow for an existing codebase (see Importing an existing project).
• Set Up Manually opens the setup wizard.

General

The General card shows the project Name and Goal. To rename the project, select the pencil icon, type the new name, and press Enter or select the check mark. Press Escape to cancel. The goal is read-only here.

Phase Progress

Phase Progress shows the share of phases marked complete as a percentage bar. A phase is a stage of work that groups tickets. The card names the first active phase it finds, or the first phase if none is active. Several phases can be active at once; the card shows one. Select View Phases to open the Phase Planner.

Agent Adapter

Agent Adapter names the agent profile Vibeless formats its MCP responses for, with its context size in tokens and its multi-step reliability rating. Every new project starts on the generic MCP profile. Until you confirm an agent, the card shows a warning icon and Default — not confirmed. Select Configure Agent to open the setup wizard.

Credits

Credits shows how many credits you have used against your plan's budget, as a bar and as "used / budget credits used". Credits pay for LLM features. If you are signed out, the card shows Not authenticated. The free plan has no LLM features, so nothing on it draws from this budget.

Recent Activity

Recent Activity lists the 5 most recent changes to the project, with the change type, the item and field changed, and the time. Select View all to open the Version History tab of the Logs panel.

Agents

The Agents tab is where you install Vibeless into your agent and control what agents do in this project. Connecting agents covers each card in full.

• Connected agents lists the supported agents and installs or removes Vibeless for each one. Vibeless writes the MCP configuration and hook commands into the agent's settings files, and uninstall removes only those entries. Rotate token issues a new MCP token for the project.
• Hooks lists the project's hooks, with Add Hook and Install hooks to .claude.
• Reports has one option, Enable semi-formal certificates on Review. When on, the agent writes a structured report each time it moves a ticket to Review. It is off by default because it uses extra agent tokens.
• Agent-artifact paths lists repo paths the scanner, file watcher, git monitor, and manual sync ignore. Changes under these paths never reach the Drift Log. Some paths are built in and locked; you can add your own.

Team

The Team tab shows how this project is shared with your organization. Organization and team sync covers sharing, roles, and sync in full.

What you see depends on your account and the project:

• No active organization. The tab is empty.
• An organization without a team plan. The tab shows an upgrade prompt.
• A team plan, project not shared. A line reads "Not shared with your organization", with a link to Share it from Organization → Projects. You share projects from the Organization panel, not from this tab.
• A shared project. A line names the teams it is shared with and your access (maintainer, editor, or viewer). Below it, the line shows the repo folder this computer uses for the project. Select Change to point the project at a different local folder. This does not re-run setup.

Team Sync card

Shared projects also show the Team Sync card, with 3 rows:

• Status: Synced, Syncing, Offline, Update required, or "Access revoked — retrying every 5 minutes". When the status is Offline or revoked, a Reconnect button appears. When the status is Update required, the button reads Update the app to reconnect and is disabled until you update.
• Last synced seq: the position of the last change this computer received.
• Pending: local changes waiting to upload.

Sync Conflicts card

Sync Conflicts lists changes that did not apply cleanly. With none, it reads "No sync conflicts." Actions depend on the kind of conflict:

Only a maintainer sees the action buttons. Other roles see the rows read-only. Conflicts are recorded on this computer only, so other devices do not see them.

Enforcement

The Enforcement tab turns your written rules into checks Vibeless can run against code. It has 2 cards.

What an enforcement proposal is

Your constraints, non-goals, phases, decisions, and spec documents are written in prose. A constraint is a rule the code must follow. A non-goal is something the project must not do. A decision is a recorded choice, and it can list things it forbids. To check code against these, Vibeless needs machine-readable fields:

• a code pattern (and optional severity) for a constraint
• path globs for a non-goal or a phase
• forbids for a decision
• governed path globs for a spec document

An enforcement proposal is a suggested value for one of these fields. The Vibeless server derives proposals with an LLM, and nothing is written until you accept it.

Where proposals come from

Proposals are created in 3 ways:

• After you apply items from a repository import, Vibeless re-derives proposals in the background.
• When you export a project from Vibe Coder, Vibeless derives proposals for the new project.
• When you select Derive Enforcement on the Spec Enforcement card.

Each run replaces the current set of pending proposals. Derivation is an LLM feature, so it needs a paid plan and uses credits from your budget.

Review and accept proposals

1. Open Dashboard, then the Enforcement tab.
2. Check the badges on the Spec Enforcement card, such as "Constraints 3/5" (enforceable out of total). Highlighted badges have gaps.
3. Select Derive Enforcement if you want a fresh set. A message reports how many proposals were derived.
4. In Enforcement Proposals, read each proposal. Proposals are grouped under Constraints, Non-Goals, Phases, Decisions, and Spec Documents. Each row shows the original text, the suggested pattern, globs, or forbids, and the reason.
5. Select the check mark to accept a proposal, or the X to reject it.

Accepting writes the value to the item the same way an edit in the app would. Rows marked not machine-enforceable or malformed payload can only be rejected. If the item's text changed after the proposal was derived, accepting fails; derive again to get a current proposal. A spec document that already has file mappings is left unchanged, and the message reads "already mapped".

Why agents cannot write these fields

Agents read enforcement fields but never write them. The agent is the thing being governed. An agent that has drifted from the plan would tend to propose loose globs and narrow patterns that let its own work pass. So the fields come from server-side derivation plus your review, and the enforcement routes are not available to agents through MCP.

Settings

• Repository shows the connected folder path, the scan status, and when it was last scanned. Select Manage Import to open the import flow. With no repository, select Connect Repository.
• Workspace names the workspace the project belongs to, or None. The app cannot add a project to a workspace, and a new project never joins one (see Workspaces and linked projects).
• Linked Projects lists other projects in the same workspace linked to this one. Each row shows a shortened project id, the link direction, and who created it. The coupling level controls what context is shared across the link. Choose awareness, dependency, read, or governance from the menu, or select the trash icon to remove the link.
• Isolation has a Discoverable option. It is not available yet and shows Coming soon.
• Diagnostics has Export diagnostic logs. The app asks where to save a .zip of application logs for troubleshooting. No project data is included.
• Danger Zone deletes the project.

Delete a project

1. In Danger Zone, select Delete Project.
2. Read the confirmation and select Delete Project again.

Deleting permanently removes the project and its data: context nodes, file mappings, phases, tickets, decision logs, hooks, and import history. It cannot be undone. The app then closes the project and opens the Projects tab of the Account panel.

If something looks wrong

• The Agent not connected banner stays after setup. Select Connect Agent and finish the wizard, or install your agent from the Agents tab.
• The Credits card says Not authenticated. Sign in from the Account panel.
• The Team tab is empty. You have no active organization. See Organization and team sync.
• Sync Conflicts shows rows but no buttons. You are not a maintainer of this project. A maintainer signed in on this computer can resolve them.