FAQ

General

What is CoopAI?

CoopAI is a VS Code extension that connects your code graph to your company Slack, Jira, and docs — admin-connected for the org, not each developer’s personal accounts — so you can answer hard engineering questions and complete or edit code without cloning entire monorepos. See What is CoopAI?.

How is CoopAI different from GitHub Copilot or Cursor?

CoopAI focuses on understanding existing codebases: ownership, decision history, blast radius, knowledge gaps, plus company Slack and tickets. Inline complete and edit stay in the open file. You review the diff, then you can open a pull request from applied /edits or from any editor change — from the patch card or by typing Create a PR in chat. Nothing rewrites the tree or creates a PR on its own.

Full side-by-side matrices: Compare CoopAI — including vs GitHub Copilot, vs Cursor, vs Claude Code, and vs Sourcegraph Cody. Answer posts: vs Cursor, vs Copilot, vs Claude Code, roundup.

Is CoopAI the same as Cooper AI?

No. CoopAI at coop-ai.dev is VS Code code intelligence. Cooper AI and similarly named agents are different products. See What is CoopAI?.

Is my code used to train models?

No. Your code and prompts are never used to train foundation models. See Security architecture.

Plans

What's included in the free Developer plan?

Full tool connectivity (GitHub, GitLab, Bitbucket, Slack, Jira, Notion, Google Docs) via the admin portal, Deep-Index / Lightning Mode on up to 3 repos org-wide, workspace repos, chat, quick actions, and inline autocomplete. Free accounts include 15 messages per rolling 6-hour usage window, with $1.75 per-window and $7 weekly caps. Solo account only — no team invites.

How do I upgrade to Pro?

Who	Path
New account (no Coop login yet)	Pricing → Start Pro → Stripe checkout → admin portal setup
Existing Free account	Extension → Settings → Plan & Usage → Upgrade to Pro, or Admin portal → Billing → Upgrade to Pro → Stripe. Do not use Pricing Start Pro with the same email (that creates a second checkout conflict).

See Plans & billing.

Do you offer Enterprise self-hosting?

Yes. Contact support@coop-ai.dev. See Enterprise deployment.

Setup

How do I sign in?

Create an account at free signup (email + password or Google), or accept an invite from your org admin. Then sign in in the extension or admin portal:

Surface	Sign-in paths
Extension → Settings → Account	Continue with Google · email (two-step) · Sign in with SSO
Admin portal	Email/password · Google · Organization name + Continue with SSO (Enterprise)
Marketing site (coop-ai.dev/login)	Opens VS Code. Sign in in the extension, not in the browser.

Email in the extension is two steps: enter email → Continue with email → password → Sign in.

Do I need an API key?

No for normal use. Automation API keys (coop_…) are optional — for CI and scripts only. Create them in the admin portal under Settings → API keys if needed.

Who connects Slack and GitHub?

In production mode, org admins connect integrations once in the admin portal. Developers do not paste OAuth tokens.

What is dev mode?

coopAI.devMode: true lets individual developers paste PATs locally for testing. Disable for production orgs.

Features

What are quick actions?

Five built-in actions: Understand Repo, Trace Decision, Find Owner, Blast Radius, Knowledge Gaps. Open Workflows in the chat header to insert /understand, /trace, /owner, /blast, or /gaps into the composer — add a prompt, then send. You can also type those slash commands yourself, or run file-scoped actions from the editor context menu. On Auto, they use Claude Sonnet 4.6.

Understand Repo / /understand is repo-wide only — click Use repo on the repository in the Remote workspace picker. A file chip blocks it. The other actions use a file selection and/or Use repo as documented in the Owner's Manual. See also Model assignments.

Can I choose the LLM provider or model?

Free stays on Auto — Coop picks a model per job. Pro, Pro+, Max, and Enterprise choose OpenAI, Anthropic, or Gemini from the model menu in chat. Autocomplete, intent chips, source previews, and PR notes always stay on Coop’s assigned models. Settings → Preferences → Model & chat explains Auto vs a picked model; it is not a second picker. See Model assignments.

What is Lightning Mode?

Deep-Index builds a searchable code graph on Coop infrastructure for faster cross-repo symbol-graph search. Available on all plans; free orgs are capped at 3 Deep-Indexed repos org-wide. Pro adds unlimited indexing.

What is the L / R chip above the chat composer?

That is the active file context chip — which file Coop is using for chat. L means local disk (workspace, clone, or Cmd+O / Downloads). R means you picked the file in Coop’s remote explorer (codehost). It is not an @ mention. Reloading VS Code does not reopen last session’s file; switching back to a past thread that used a file does. See Active file context chip and Can I use Coop on a local file?.

Can I use Coop on a local file?

Yes. Open the file in VS Code and Coop works as a normal assistant on that file: chat, ghost text, and reviewable edits. You can still ask about Slack, Jira, and the other tools your admin connected. You do not get the repo slash commands (/understand, /blast, /owner, /trace, /gaps). Those stay on an indexed repo you picked with Use repo. You can still work across every repo indexed for your team without cloning them.

Can I share prompts with my team?

Yes. Commit .coop/prompts.json to your repo. See Owner's Manual — Prompt Library.

Can I create a pull request from Coop?

Yes. After you Apply an /edit on a Use-repo file, click Create pull request on the patch card. Or type Create a PR in chat — that works after Apply or after you type in a Use-repo file (no Apply required). On a local file, Create pull request stays disabled after Apply. Confirm the branch, title, and notes, then submit. Cancel or Escape creates nothing. See Create pull request.

Enterprise SSO

Does Coop support SAML single sign-on?

Yes, on the Enterprise plan. Org admins configure SAML in the admin portal under Settings → Single sign-on. Supported IdPs include Okta, Azure AD / Entra ID, and any SAML 2.0 provider with signed assertions. See Single Sign On (SSO).

Where can I sign in with SSO?

Surface	SSO available?
Admin portal (admin.coop-ai.dev/login)	Yes — Organization name + Continue with SSO
VS Code extension → Settings → Account	Yes — Sign in with SSO (browser handoff)
Marketing site (coop-ai.dev/login)	Sends you to the VS Code extension — sign in there (SSO included)

What happens when my org requires SSO?

When an admin enables Require SSO, password and Google sign-in return sso_required at login and on session refresh. Coop immediately revokes existing password and Google sessions and refresh tokens for the org; SAML sessions remain valid. Org API keys for automation still work — admins should revoke keys for offboarded users.

Can I disable SSO after enabling Require SSO?

Turn off Require SSO in Settings → Single sign-on → Sign-in policy first. Disabling SAML while Require SSO is active returns sso_required_active.

Why does Google sign-in fail with email not verified?

Google sign-in requires Google's verified-email flag (email_verified). Unverified Google accounts are rejected with email_not_verified — verify the address in your Google account, then try again.

Does Coop block password login until email is verified?

No. Coop sends a verification link on password signup but does not hard-block password login until verified (standard B2B soft verify).

Support

How do I contact support?

Email support@coop-ai.dev or book a demo.

Where is the install guide?

Owner's Manual — Get Started or Getting started docs.