Settings Overview
Settings is where you configure data sources, organization settings, and personal account preferences. Domain configuration has its own Domains destination in the global application rail.
Opening Settings
| Method | Action |
|---|---|
| Keyboard shortcut | Press Cmd+, (Mac) / Ctrl+, (Windows) |
| Gear icon | Click the gear icon in the navigation rail — Organization settings |
| Account menu | Click your picture in the top-right corner — User settings |
| Deep link | Navigate to ?tab=<section> query parameter |
The gear goes straight to Organization settings. Your own settings — profile, theme, connections, API keys, sessions — open from the account menu.
If Vibedata is running without single sign-on (a local or evaluation install), the sections that only exist to configure sign-in and other people — Users, SSO Providers, Identity providers, and GitHub — are not shown. That deployment has one operator, signed in from the host session, so there is nobody to invite and no provider to register. The welcome checklist says the same, in place of those steps.
Settings Layout
When you enable or disable a setting that saves immediately, a success notification confirms that the change was saved. For settings with a Save button, the notification appears after Save succeeds. While a change is saving, wait for the result before changing it again. If saving fails, the previously saved setting remains in effect and an error explains how to retry. Theme changes and local filters do not show success notifications.
Settings is a two-column layout:
- Left column — The settings navigation with section labels and items.
- Right column — The content panel for the selected section.
Use Hide Organization settings navigation or Hide User settings navigation on the left side of the header to give the selected page more room. Use the corresponding Show control to restore the section list. These buttons work with Enter or Space; Cmd+B (Mac) / Ctrl+B (Windows/Linux) invokes the same control. Hiding navigation keeps your current page and unsaved input; hidden navigation items are skipped when you press Tab. The navigation list and page content scroll independently.
Recovering a settings change
Settings editors protect the configuration you reviewed, including budgets, capacity, providers, LLM profiles, announcements, user access, action confirmation, connections, plugins, marketplaces, and custom automations. If that configuration changes while you are editing or confirming removal, Vibedata keeps your draft or confirmation open. Use the displayed reload action, such as Discard and reload, Reload and review, or Reload connections. A successful reload discards the old draft or selection so you can review the saved settings and submit again. If reload fails, your draft or selection stays open. Background updates do not silently replace your draft, and Vibedata does not automatically resubmit it.
When creating an LLM profile, announcement, provider, stored connection, connector source, marketplace, or custom automation, retrying unchanged input within 24 hours recovers the original completed result. To start a new attempt after resolving an external problem, cancel and reopen the creation form. An older browser tab that asks for a reload must be refreshed before submitting protected changes.
Navigation Structure
The left navigation is divided into two groups:
PROJECT
| Item | Purpose |
|---|---|
| Sources | Connect and manage data sources; configure Git and Fabric defaults |
| Skills | Manage AI knowledge modules that extend the agent's capabilities |
| Plugins | Manage plugin marketplaces, installation, and enablement |
ORG SETTINGS
| Item | Purpose |
|---|---|
| Org settings | Open organization-wide settings such as Data Platforms, Identity providers, and GitHub |
ACCOUNT
| Item | Purpose |
|---|---|
| Profile | Use Account for display name, Appearance for themes, Repository access for GitHub, and Sessions for signed-in sessions |
| Action confirmation | Control when agents pause for approval before running proposed actions |
| Data platforms | Manage personal and shared access for Domain Data Platform and Secret Store requirements |
| MCP servers | Connect and manage the MCP servers available to your account |
Managing Organization MCP Instances
Vibedata Owners manage organization-wide MCP instances from Org settings → MCP catalog. Catalog lists available entries; MCP instances lists instances added to the organization. Click a catalog row to switch to its filtered instances. Both tabs search any part of the name, ignoring case.
The catalog synchronizes at startup. Opening the page does not refresh it. Select Refresh catalog to synchronize manually, and Update instances to update existing instances from the current catalog definitions.
Add an instance
- Click the catalog entry to open its filtered MCP instances list.
- Select Add instance.
- Optionally enter Name to distinguish instances, such as separate workspaces.
- For each field, choose Preconfigured to enter a shared value or User-provided to ask each user for their own. Optional fields can be set to Ignore.
- Complete the required shared values and select Add.
Sensitive fields start masked; use the eye control to show or hide the value being entered. Saved values remain hidden.
Entries that require a shared OAuth app show OAuth setup required in the catalog. Use Configure OAuth in the entry's overflow menu to test and save the app before adding an instance. Entries that permit only one instance disable Add instance once it exists.
Edit an instance
- Click the instance row, or select Configure instance in its overflow menu.
- Change Name or the field choices and values. Leave an unchanged shared value blank to keep it.
- Select Save.
Leaving an edited form asks whether to discard unsaved changes. Choose Keep editing to preserve the draft or Discard changes to leave. Users continue to connect to each instance separately.
Remove an instance
- Select Remove instance in the instance row's overflow menu.
- Review the instance name and the warning that connected users will lose access.
- Select Remove instance to confirm.
Only the selected instance is removed. Sibling instances from the same catalog entry remain available.
Instance states
- No instances yet — There are no instances for the current catalog filter, or no organization instances if no filter is selected.
- Ready — The instance has its required configuration and its runtime reports that it is ready.
- Needs attention — The instance remains defined, but its configuration is incomplete or its runtime has not reported that it is ready.
- No supported MCP catalog entries — The catalog contains no entry Vibedata can configure.
- MCP catalog unavailable — Obot is not responding. Select Retry after it recovers.
Connecting an MCP Server
Open User Settings → MCP servers. Each organization instance appears as a separate row using its instance name. Select Connect on the instance you want to use. A fully preconfigured server that needs no personal authorization appears Connected automatically.
- If the server needs OAuth authorization, Vibedata opens the provider sign-in page.
- If the server needs a header or other value, complete the setup form and select Save. If OAuth is also needed, continue with provider authorization.
- If the server authorizes you with your own token, the setup form asks for it. Vibedata saves it for your account only and opens no authorization page.
- If the authorization page does not open, select Connect OAuth on the server row to resume.
Instances are organization-wide, not per Domain. A server you connect is available in every Intent you open, whichever Domain that Intent belongs to.
Return to Vibedata after authorization. Vibedata refreshes the row when the Settings window regains focus. Use Disconnect to clear the authorization Vibedata saved for you on that server, or Retry when Vibedata cannot read its status. Disconnect appears only when there is a saved authorization to clear.
Applying action-confirmation changes
Action-confirmation changes apply when the next agent session starts. To apply your saved settings immediately to an active Intent you are driving, return to the workspace, Pause the Intent, then open it again.
Navigating Between Sections
Click any item in the left navigation to switch sections. The active section is highlighted with a blue background.
Action confirmation default
Open Org settings → Action confirmation to set the Action confirmation default for users without personal overrides. Choose Risk level, set Run unclassified actions without pausing as needed, and select Save. Changes apply to new agent sessions. Pause and reopen the intent to apply these changes to an active session.
If saving fails, review the error. Discard and reload replaces your unsaved choices with the current default so you can review and retry. Users can configure their own rules as described below.
Action confirmation changes
User Settings → Action confirmation controls when the agent pauses before proposed actions.
Your own actions
Use my own confirmation settings — off by default, so the instance system default applies. Turn it on to choose your own risk level and unclassified-action behavior. Risk level shows three cards, each with its description:
| Risk level | Description on the card |
|---|---|
| Low | Pause on every classified action |
| Medium | Pause on Medium and High (system default) |
| High | Pause only on High |
Run unclassified actions without pausing — when on, actions the agent can't classify run without asking for approval.
Saved risk-level and unclassified-action changes apply when your next agent session starts. Agent sessions that are already active keep the confirmation settings they started with — Pause the Intent, then open it again, to apply them immediately.
Subagent actions
Below your own settings, Subagent actions governs the Subagents you delegate work to — not the risk level above, which applies to what the agent proposes to you directly.
Only allow pre-approved actions — Subagents never ask for approval. When off (default), all actions are allowed except protected runtime paths. When on, actions at or above your risk threshold also need an existing Always-Allow grant, or they’re blocked.
Saving
Both groups share one Save button. It stays greyed out until you change something, and switching a toggle changes nothing on its own until you select Save — leave the screen first and your edits are discarded. Save submits only what you changed and tells you once whether it worked. Like the risk settings, a Subagent-mode change applies when your next agent session starts.
If the system confirmation default changes while your personal confirmation draft is open, Save can report a conflict even when your own override has not changed. Choose Discard and reload, review the inherited settings, and make your changes again. Vibedata does not automatically retry the old draft against the new settings.
Always-allowed actions
Below the Save button, Always-allowed actions lists every action you've always-allowed from an approval request, grouped by kind — Exact command, Command family, or Tool — each with the date it was created. Click the trash icon next to an entry to revoke it. The footer shows "Showing X–Y of Z" with your true total; once you have more than 50 grants, use the Previous page / Next page buttons to move through the list, so nothing is hidden. If your registry grows past the 10,000 grants a single agent session can load, a red warning appears here telling you new agent sessions will fail to start until you revoke some (VD-5254).
Unlike the settings above, always-allow grants apply immediately: creating or revoking a grant takes effect on the very next matching action in any active agent session, with no need to pause and reopen the Intent. Grants apply at any risk level until you remove them.
Returning to the Workspace
Click the back arrow (←) at the top of the left navigation column (above the "Settings" heading) to return to the main workspace (activeView → workspace). You can also press Cmd+, / Ctrl+, again to toggle back.
Quick Reference
| Action | How |
|---|---|
| Open settings | Cmd+, or gear icon |
| Navigate to Domains | Left nav → Domains |
| Navigate to Sources | Left nav → Sources |
| Navigate to Org Settings | Left nav → Org settings |
| Navigate to Skills | Left nav → Skills |
| Navigate to Plugins | Left nav → Plugins |
| Navigate to Profile | Left nav → Profile |
| Manage Domain connections | Left nav → Data platforms |
| Connect an MCP server | Left nav → MCP servers → Connect |
| Open Action confirmation | Left nav → Action confirmation |
| Revoke an always-allow grant | Action confirmation → Always-allowed actions → trash icon |
| Return to workspace | Click ← arrow at top of left nav |