All Docs/Your settings

Your settings

Your own settings are the You pages in Settings: Profile, Sign-in & security, Replies & voice, Agent setup, Notifications, Privacy & data and Organizations. They belong to you, follow you into every organization you're in, and each setting lives on exactly one page. Open Settings from your avatar in the top-right corner.

Which settings you see

Settings has two groups. You holds the seven personal pages described on this page, and everyone has them.

Organization holds the settings for the organization you're currently working in: Organization, Members, Projects, Billing, Usage & limits, Connections and Analytics. Owners and Admins can change them; Members can see most of them. See Organizations, members and roles and Billing, usage and limits.

If you're a Guest in an organization, you see only the You pages. Guests have no organization settings, no member list and no billing, because a Guest's access is limited to the projects they were added to.

Project settings are separate again: open a project and use Project settings (on a desktop browser). See Projects.

Profile: name, photo, GitHub account, theme and celebrations

Settings → Profile is how you and your work appear to the people you work with.

Name and photo. Your first and last name, and a profile photo shown on your avatar across the app. The photo can be any image up to 5 MB. Use Add a photo or Change photo, or remove it. Without a photo, your avatar is your initials over a color: pick the Avatar color just under your photo, and it's saved straight away.
Your GitHub account. Use Link GitHub account so the code changes and pull requests you make, yourself or through an agent, show under your name. GitHub confirms it's you, and DevSpec keeps no access to your account. This is separate from signing in with GitHub. See Link your GitHub account.
Theme. System, Light or Dark. Your choice is saved to your account, so it follows you to every device you sign in on. You can also change it from the Theme options in your avatar menu; both change the same setting.
Celebrations. Short animations when something worth celebrating happens: Deploy fireworks when a deploy of your project goes live, Task confetti when someone signs off a task, and a Goal celebration when a project reaches a goal. Each has a switch and a Show me button so you can see it first. They're all on to begin with, and your choices follow you to every device. A device set to reduce motion never plays them on its own, whatever the switches say.

Settings → Sign-in & security covers your email addresses, every way you sign in and everywhere you're signed in. Your password and two-factor secrets are held by DevSpec's sign-in provider, not stored by DevSpec. Only the sign-in methods DevSpec offers appear here.

Email addresses. Add an address and confirm it with the six-digit code DevSpec emails to it. Choose which address is primary with Make primary, and remove the others. You always keep at least one, so add a second address before removing the one you sign in with.
Sign-in accounts. Connect or disconnect an account you sign in with, such as GitHub. Disconnecting one doesn't remove your DevSpec account.
Password. Set one, change it (tick Sign out of every other device if you want to), or remove it when a passkey or sign-in account can sign you in instead.
Two-factor. Set up an authenticator app by scanning the code and entering the six digits it shows. Your backup codes are shown once; save them somewhere safe. Generate new codes gives you a fresh set, shown once, which replaces the old one.
Passkeys. Sign in with your face, fingerprint or device PIN instead of a password. Add a passkey on the device you're using, name it, or remove it.
Active devices. Everywhere you're signed in right now, with this device marked. Sign out anything you don't recognize.

When you change a credential and your last check was more than a few minutes ago, DevSpec asks you to Confirm it's you: with your password, a code emailed to you, or a passkey, then your authenticator app if two-factor is on.

Replies & voice: how you're answered

Settings → Replies & voice decides how replies are written for you and how they sound when read aloud.

Response style. Two switches, both off until you turn them on: Conversational replies for short, spoken-style answers (the page shows exactly what it asks for), and Focus on the product, not the code for explanations without code-level detail. Below them, Anything else about how you want to be answered? takes up to 10,000 characters, for example "Give me the trade-off before the recommendation." Your style follows your messages to Dev and to your agents alike. It shapes the reply you read, never what gets written into a task, a brief or a document.
Voice. The voice DevSpec reads replies in, with a preview.
Voice language. The language replies are read aloud in.
Playback. What happens when a message arrives: Silent (nothing plays), Beep (a short chime) or Voice (new messages are read aloud), and how fast replies are read.

The message settings beside the session composer have quick controls for the same saved values. See Voice.

Agent setup: connect your own agent

Your Agent setup page is where you connect Pi, Claude Code or Antigravity CLI, running on your own machine, to DevSpec. It holds:

Connect your agent: pick your agent, create your access token and follow the steps. Your token works across all your projects. Underneath, the tools that have connected as you, and when each was last seen.
Start an agent: the steps to start an agent you have connected.
Access tokens: every token you have made, to show, copy or revoke.
Personal agent rules: instructions about your machine and tools, supplied to your agents. DevSpec’s own guidance arrives with the connection; any optional repository reminder appears in your selected tool’s setup instructions.
Default for new agents: who may talk to agents you connect from now on, for your current organization: Only you, Anyone on the project or Chosen people. Changing it also updates any of your idle agents waiting outside a session that haven't been used yet; agents already in a session or with prior work keep their own setting.

Repositories, databases, logs and deployments attach to a project, not to you: add them from the project's Integrations. See Connect your agent and Rules and instructions.

Notifications: choose what reaches you

Settings → Notifications decides which notifications reach your notification bell and which also arrive by email.

Product updates controls occasional emails from the DevSpec team when major features or improvements ship.
Activity updates is one switch for progress and FYI notifications across everything: successful deploys, passing tests, verified items and comments. Things that need you (mentions, replies, assignments, reviews and failures) are never affected.
Categories lists each kind of notification with an In-app and an Email switch. Show details opens finer choices inside a category, such as deployment failures on and successes off. A choice you make on a category or its finer rows wins over Activity updates.

Critical billing alerts always stay on in-app. Two emails can't be switched off at all: warnings before an unused account is closed, and the one-time notice when you haven't been active for a year.

For every category, what's on by default, the bell and the Notifications page, see Notifications and messages.

Privacy & data

Settings → Privacy & data is where you control what DevSpec keeps about you, take a copy of it, and close your account.

Voice recordings: when you speak a message in a session, DevSpec always keeps the written words. Save my voice in messages controls whether your voice audio is attached too, so people in the room can play it back (the composer's message settings have the same switch). It's off by default, and voice notes you send in 1:1 Messages always include your voice. All voice recordings are kept for 48 hours and then automatically deleted—only the written message stays.
Optional measurement: Page performance and Website and signup measurement are separate choices for this browser, both off unless available and explicitly allowed. Performance uses page-load and responsiveness measurements with coarse page categories, not raw project/session addresses. Website/signup measurement uses a fixed 30-day browser observation; temporary correlation is deleted within 24 hours afterward, and aggregate totals are kept for 24 months. It does not create a permanent visitor-to-account history or include your messages. Use Save choices to confirm a change, or Turn off optional measurement to withdraw. The same Privacy choices page works without signing in. Other devices keep separate choices, and these controls never subscribe you to product-update emails. Essential sign-in, security, billing and work remain available when measurement is off.
Export your data: ask for a copy of what's yours, a zip with your profile and preferences, your memberships, every message you wrote and the room it was in, your Scratchpad notes, your notifications, your usage and payments, and the files you uploaded. DevSpec prepares it in the background, tells you when it's ready, and the download works for 7 days. An organization's Owner can export everything the organization owns; see Organizations, members and roles.
Close your account: Close my account removes your sign-in, your saved connections and tokens, your preferences, your Scratchpad notes and your notifications, and takes you out of every organization you're in. Messages and work you contributed to your teams stay, shown as "Former member". You confirm by typing CLOSE, and it can't be undone.

If you're the only owner of an organization that has other people in it, transfer ownership first; the dialog tells you which organization. A workspace that only you own, with nobody else in it, is deleted with your account, and the dialog names it. Deleting it removes its projects and files. Any money left in it is lost and not refunded, and the dialog shows how much before you confirm, so spend what you need first.

What happens to an account that isn't used

DevSpec closes accounts that go unused for a long time, with warning, and never closes one that a paying team depends on.

After two years without using DevSpec, an account is scheduled to close in 30 days, and you're emailed 30 days, 7 days and 1 day before. Coming back and using DevSpec at any point cancels it.
Accounts in an organization that has money in its balance are exempt. They're never scheduled for closing, however long they go unused.
If you're the only owner of an organization, DevSpec doesn't close your account automatically. It emails you instead and leaves the account open, because what happens to an organization is a person's decision.
After one year without using DevSpec, if you belong to an organization that has money in its balance, you get a one-time reminder email.

These emails can't be switched off in Settings → Notifications, because they protect your account.

Organizations: switch, set your job title or leave

Settings → Organizations lists every organization you belong to, with your role in each, what that role lets you do, and your own Dev & voice allowance there. This is your personal list; the settings for one organization are under Settings → Organization.

Switch to it makes that organization the one you're working in. The organization you're in now is marked Current.
Organization settings (for Owners, Admins and Members) opens that organization's settings page—switching to that organization first if it isn't the one you're currently in.
Job title is yours in that one organization, and optional. It's shown next to your name to the people you work with there, on member lists and in a session's people list. When you join another organization, DevSpec asks for it once; Not now is fine.
Leave removes you from the organization straight away. You lose access to every project in it, and any agent you run on those projects is disconnected. An Owner or Admin can invite you back. This is also where a Guest leaves an organization.
The organization's only Owner can't leave. Transfer ownership to someone else first, or delete the organization, from its Settings → Organization page.
Create an organization starts a new organization, with its own members and its own balance. It starts at $0 until someone adds funds.

What each role means at the bottom of the page explains every organization and project role. See Organizations, members and roles.