Workspace Defaults and Preferences

Workspace defaults and preferences is the VibeControls concept for deciding, once, how new work starts across a workspace. Instead of choosing an agent, a terminal session type and a vibe type every time someone opens a session or creates a project, the settings page stores sensible defaults for the whole team, along with the agent behavior most people never need to touch.

Teams that share a fleet otherwise drift apart: one person starts sessions in one terminal multiplexer, another binds projects to a different machine, and heartbeat and reconnect behavior varies from box to box. Central defaults make new sessions and vibes predictable, while the design still leaves room for per-vibe overrides where a project needs them.

The illustration shows Settings with Save and More buttons in the header and a banner explaining its purpose. A list on the left divides settings into Notifications for alert preferences, Workspace for agent, session and vibe defaults, Code Editor for the default IDE and per-vibe overrides, and Advanced for logging, telemetry and secrets. The Workspace section is open. Its General Defaults card sets the default agent, shown as a coding agent on a named machine, the default session type, the default vibe type, and switches for auto-starting sessions and automatic git sync. An Agent tuning card sets the heartbeat interval in seconds, the maximum sessions per agent, an auto-reconnect switch and a box for default environment variables written as key and value pairs.

These defaults are designed to feed the rest of the product. The heartbeat interval shapes how quickly the health page notices a quiet agent, the session cap limits how much work one agent takes on, and the default agent and session type decide what happens when someone starts a session from the overview or from a vibe. Notification preferences and webhooks, on neighboring settings pages, decide who hears about it.