Profile Settings
When revoking a personal API key, review the key's last-used and expiry details before selecting Revoke. Usage can change the key while the dialog is open. If revocation fails because the review is stale, close the dialog, reload, and review the key again before retrying.
The Profile panel lets you set your display name, change the application color theme, manage repository authorization, and manage your signed-in sessions.
Open it from the account menu — your picture (or initials) in the top-right corner of the header bar — under User settings. Your picture comes from the identity provider you signed in with; when it attests none, Vibedata shows your initials.
What's on This Screen
The Profile panel has four tabs, each with its own address, so you can link to one, reload it, and move between them with the browser's Back and Forward buttons:
- Account — The default tab, with Display name and your read-only email.
- Appearance — Color mode cards with previews, plus independent Light theme and Dark theme pickers.
- Repository access — Your GitHub repository authorization.
- Sessions — Active signed-in sessions and controls to revoke sessions or sign out elsewhere.
Switching tabs is a move to another page, so if you have typed a display name without saving it, Vibedata asks whether to discard it first — the same question you get when you leave Profile. Choose Save before switching to keep the change. Returning from GitHub authorization opens Repository access, whether the authorization succeeded or was refused.
Your account identity appears in the account menu.
Changing your display name
On Account, under Display name, type the name you want Vibedata to show. The field starts pre-filled with the name your identity provider attested, so you edit it only to override that default. Save is enabled only once the name differs from the saved value, so leaving the section without editing asks nothing. If you switch tabs, leave Profile for another settings page, go back, or close the browser tab with an unsaved change, Vibedata asks whether to discard it first; Keep editing keeps your text.
Your sign-in email and your roles are shown read-only here; Vibedata does not edit them on this screen.
If someone else changes your profile while you are editing, saving is refused rather than overwriting the newer value. The draft you typed stays on screen, with Discard and reload to pull the latest value; if a save fails for another reason, your draft is kept so you can retry.
How to change your appearance
- Open User settings → Profile from the account menu.
- Select the Appearance tab and choose Light, Auto, or Dark in Color mode.
- Choose a theme in Light theme and Dark theme. Each list contains only themes for that mode, with the Vibedata theme first. The Light and Dark cards preview their matching picks; Auto shows both side by side. Changing a pick updates its card previews immediately, even when that mode is not in use. There are no additional previews below the pickers.
| Control | What it does |
|---|---|
| Light | Uses your Light theme pick regardless of the operating system. |
| Auto | Uses the matching pick as your operating system switches between light and dark. |
| Dark | Uses your Dark theme pick regardless of the operating system. |
The default is Auto, with Vibedata Light and Vibedata Dark. Choose the two themes independently; changing the inactive pick does not switch modes.
Changes apply immediately and save automatically to your Vibedata account; there is no appearance Save button. They affect only you. A later page load starts in your saved theme without briefly showing the default, including on another signed-in browser. Other already-open tabs and devices keep their appearance until their next page load; changes are not synchronized live.
What you'll see
- While the theme list loads, Vibedata keeps the page's starting appearance.
- If no additional themes are available, the pickers offer Vibedata Light and Vibedata Dark. If a saved theme is unavailable, Vibedata silently uses the Vibedata theme for that mode and attempts to save that fallback.
- Saving appearance… means your change is being saved. Unable to save your appearance. Choose a theme to try again. means the save failed; the affected choice returns to its saved value unless you have already made a newer choice. Choose again to retry.
Editors follow light or dark mode with Vibedata's syntax colours, not each theme's own editor colours. Chat code blocks remain dark. dbt docs switch between light and inverted dark presentation rather than matching the theme's exact colours.
Managing your sessions
On the Sessions tab, a table lists each Device with its IP address, when it Signed in, and when its session Expires. Your current session carries a Current badge and has no Revoke button. Choose Revoke beside another device to end that session.
Vibedata checks the selected device's details before revoking its session. Changes to other devices, including a new sign-in, do not block this action. If the selected session changes before revocation completes, Vibedata refuses the stale request. Choose Reload sessions, review the refreshed devices, then choose Revoke again if you still want to end that session. Reloading does not retry the revocation. Other revocation failures also offer Reload sessions.
Under Other sessions, Sign out everywhere except here ends all other sessions and keeps your current session signed in. Anyone using those sessions must sign in again.
GitHub Connection
- Open User settings → Profile → Repository access.
- Choose Connect GitHub to authorize your account at GitHub.
- When you return, the row shows your GitHub identity with Validate and Disconnect.
If Vibedata cannot use your saved GitHub connection, the GitHub row shows Reconnection required alongside Re-authenticate and Disconnect. Validate is absent in this state. Choose Re-authenticate and complete the GitHub authorization to connect again. This can mean expired credentials, revoked access, or another unusable saved credential; it does not necessarily mean you revoked access at GitHub.
Choose Disconnect, review Disconnect GitHub?, and select Disconnect to remove the Vibedata connection. This does not revoke your grant at GitHub.
When repository access uses the operator's GitHub CLI session, this section shows that shared source inline, including its availability, identity when reported, and operator guidance. Use Check connection when available. It has no personal Connect, Reconnect, or Disconnect action and needs no separate list or detail page.
Signing in through a GitHub identity provider does not grant repository access. The GitHub commit provider authorization is separate from your Vibedata sign-in.
API keys
Open User settings → API keys to create personal access tokens for scripts or CI jobs that act as you.
- Select New API key.
- Enter Key name and select Create.
- Copy the revealed key before dismissing it; the secret is shown only once.
Use Revoke on a key you no longer need, then confirm its removal. No API keys yet means none are configured. A failed load offers Retry.
Usage
Open User settings → Usage to review your own consumption. Budget standing opens first — since budgets have no per-person scope of their own, it reads the Organization's configured budget: On track, Near limit, or Exhausted, with spend to date, burn rate, and the projected month-end total, plus either the remaining headroom or how far spend is over the limit. With no Organization budget configured it instead reads No monthly budget set — spend is unlimited. Either state offers a Set a limit (or, once exhausted, Raise the limit) link to Capacity settings' Budgets tab.
Choose Last 7 days, Last 30 days, or Last 90 days — the page opens on the last 7 days, and every section except Budget standing follows that choice. The Intent ledger lists your own Intents with recorded spend in the window, sortable by Cost, Turns, or Last active, and paged; it is open by default and collapses to a count of those Intents.
Cost by LLM profile is collapsed by default and says while collapsed which profile leads and by how much of the window's spend. Expand it for one row per profile: the model it mostly ran, the sessions and turns it took, the tokens it consumed and how those divided between new input, output, cache and reasoning, and what it cost. Read any attribution notice before interpreting the totals. There is no refresh control: the page reads a durable ledger that is always current. A failed load offers Retry. For instance-wide consumption, administrators use Org settings Usage analytics.
Memory
Open User settings → Memory to review the durable facts the agent remembers for you. These records are private: only you can see them. Select a record to open its details, and use Delete record there to remove it after confirming. Use Refresh to reload the list. A failed load offers Retry; when the store holds more records than the list shows, a notice says so.