Skip to main content
Your profile holds settings that belong to you, not your organization. Open Profile from the dashboard account menu. Settings that everyone shares are under Organization settings. Setting up your profile is step 7 of the setup checklist. If Sessions says “Sessions need organization access”, sign in through your organization to see them.

Integrations

Profile → Integrations has two lists: Connected apps for your subscriptions and Ask Obss, and MCP connections for your MCP server sign-ins.
Profile Integrations tab with Connected apps rows for GitHub, personal subscriptions, Ask Obss, and Ask Obss in Slack.Profile Integrations tab with Connected apps rows for GitHub, personal subscriptions, Ask Obss, and Ask Obss in Slack.

Connected apps

Each subscription has its own plan rules:
  • GitHub: needs a paid Copilot plan (Pro, Pro+, Business, or Enterprise).
  • OpenAI (ChatGPT Subscription): needs a paid ChatGPT plan (Plus, Pro, Business, Enterprise, or Edu). Runs count toward the plan’s Codex usage limits.
  • Anthropic (Claude Subscription): needs a paid Claude plan (Pro or Max). Runs count toward the usage limits that Claude and Claude Code share.
  • Nous Portal: runs count toward your Nous Portal account’s usage.
The Ask Obss row shows only when Ask Obss is set up for your organization.

Connect a subscription

  1. On Profile → Integrations, select Connect on the row.
  2. Sign in and approve Obss. For ChatGPT and Nous Portal, enter the code that Obss shows. For Claude, approve access in Claude, then paste the authorization code into Obss.
  3. Turn on the agent under Manage → Agents.
Personal integrations are private, so each member connects their own, and a run uses the account of the person who starts it. On Model providers, they carry the Private to you tag. Cursor has no personal integration. It uses an organization Cursor API key.

Disconnect an integration

Select Disconnect on a connected row and confirm. New runs that need the connection stop in every project in this organization. Past experiments don’t change, and Obss doesn’t delete your provider account. From the CLI or the plugin, send disconnect_personal_connection to obss project ai delete or delete_project_ai. You can connect again later, but only in the dashboard, because that’s where you sign in. To stop Ask Obss from using your account in this organization, select Disconnect on the Ask Obss row, or use the CLI or the plugin. Disconnect Ask Obss explains what changes.

MCP connections

MCP connections lists your sign-ins to MCP servers that your treatments use, such as a server that needs an OAuth sign-in. When a connection needs it, sign in again from its row. Browse MCP servers opens the project’s MCP servers. To check a connection without showing its secrets, use obss mcp accounts inspect or inspect_mcp_account. You can sign in only in the dashboard.

API keys

Create a personal API key to run the CLI where you can’t sign in, such as a CI job or an agent’s machine. The CLI reads it from OBSS_API_KEY.
Profile API keys tab with the note about OBSS_API_KEY, a create button, and the list of personal API keys.Profile API keys tab with the note about OBSS_API_KEY, a create button, and the list of personal API keys.
  1. Open Profile → API keys.
  2. Create a key and copy it.
  3. Store it as a secret named OBSS_API_KEY in your CI, or wherever the CLI runs.
You create keys only in the dashboard. If the tab says “API keys aren’t turned on for your role”, ask an organization admin. A key acts as you in this organization until you revoke it, so treat it like a password. When you no longer need a key, or it might have leaked, revoke it on the same tab.

Delete your account

Open Profile → Danger zone, select Delete account, and enter your email to confirm.
Deleting your account permanently removes it and your membership in every organization you belong to. You can’t undo it.

From the CLI and the plugin

Next steps