Skip to main content
Vibely ships opinionated defaults so you can build right away — but almost every default is yours to change. This section is the map of what you can customize, and where.

​
Three scopes

Your customizations live at one of three levels. Picking the right scope decides who sees the change and where it follows you.

Account

Personal to you. Follows you across every workspace.

Workspace

Shared across everyone in the workspace. Admin-only to edit.

Project

Lives in the project repo. Travels with git clone.
SettingScopeWhere to change it
Theme (light / dark / system)AccountTop-right avatar → Appearance
Pinned model (optional)AccountModel picker in the chat composer
Custom instructionsAccountSettings → Customize Vibely
Notification channelsAccountSettings → Notifications
Generation-complete soundAccountSettings → Account
Workspace name, avatarWorkspaceSettings → Workspace (admin)
Auto-accept workspace invitesAccountSettings → Account
Design tokens, theme.cssProjectEdit in code, or prompt the agent

​
What you’ll find here

Appearance

Light, dark, and system theme — how it persists and where it follows you.

Custom instructions

Persistent context the agent reads on every turn — persona, stack preferences, tone.

Notifications

Email, push, in-chat — what fires what, and how to mute the noise.

Workspace

Workspace name, avatar, public username, and invite behavior.

​
A reasonable starting point

If you’ve just signed up and want to set things up the way most people prefer, do these four in order:
  1. Pick a theme — Top-right avatar → Appearance → Dark / Light / System. See Appearance.
  2. Write 3–5 lines of custom instructions — your stack, your tone, anything you’d otherwise type into every prompt. See Custom instructions.
  3. Mute the notification channels you don’t need — most people turn off the weekly digest. See Notifications.
  4. If you’re on a team, set the workspace avatar and name so builds are easy to identify. See Workspace.
Total time: under five minutes.

​
What you can’t customize (yet)

Honest list, so you don’t go hunting:
  • Editor preferences — Vibely uses sensible Monaco defaults; per-user font size, Vim mode, and tab width aren’t exposed.
  • Keyboard shortcuts — ⌘K opens project search. There’s no rebinding UI; if you need one, tell us.
  • Accent colour — primary is fixed to Vibely terracotta. Theme tokens inside a generated project are fully editable in code.
  • Per-project model pinning — pinning is account-wide. You can still override per turn from the composer on any project.
If any of these are blockers, file a request — the gaps are a roadmap, not a stance.