how_it_works
Index the code. Query the stack. Stay in the file.
VS Code code intelligence that Deep-Indexes your repositories once, pulls company Slack and Jira when you ask, then lets you find owners, check blast radius, complete, and edit — without cloning the monorepo.
// index
01
Index the code
Deep-Index selected repos so you can understand a codebase without cloning.
// query_live
02
Query the stack live
Company Slack, Jira, and docs in VS Code — shared org context, fetched when you ask.
// in_vscode
03
Ask, complete, and edit
Stay in VS Code. Review the diff. Nothing rewrites the tree on its own.
the_split
What we keep vs what we fetch
Only repositories are Deep-Indexed. Company Slack, tickets, and docs are queried live from the admin-connected workspace so Coop does not store a second copy — and does not use each developer’s personal accounts.
Indexed on the server
Your repositories
- Symbol graph — files, symbols, callers, ownership
- Full-text search across Deep-Indexed repos
- Commit, PR, and CODEOWNERS signals
- Inventory facts — file counts, languages, size
The temporary clone is deleted when the index job finishes. Coop does not keep a git mirror on every laptop.
Fetched when you ask
Your company tools
- Company Slack threads
- Company Jira tickets
- Company Confluence, Notion, and Google Docs
- The current file body from the code host
Admin-connected for the org. Live fetch keeps tickets and threads current without copying them into a second index — and without using each developer’s personal accounts.
index
Index the code
An org admin picks the repositories to Deep-Index. Coop clones each repo briefly, builds a searchable map (symbols, callers, ownership, full-text search), then deletes the clone. That is how you get VS Code code intelligence without a permanent local monorepo. File bodies are fetched from GitHub, GitLab, or Bitbucket only when someone actually needs them.
Free: up to 3 Deep-Indexed repos · Pro: unlimited
query_live
Query the stack live
An org admin connects Slack, Jira, Confluence, Notion, and Google Docs once for the company. Those tools are not background-indexed, and they are not each developer’s personal accounts. When a question needs them, Coop fetches from the shared company workspace and places that context next to the code graph. Your conversations are not stored as a standing search index.
- 01Code hosts (GitHub, GitLab, Bitbucket) power Deep-Index, PRs, blame, and CODEOWNERS.
- 02Company collaboration tools (Slack, Jira, Confluence, Notion, Google Docs) are admin-connected once for the org, then fetched live for Trace Decision, Knowledge Gaps, and slash commands — shared team context, not personal accounts.
- 03Setup checklist: Integrations and connect integrations.
in_vscode
Ask, complete, and edit
Pick Use repo on an indexed remote repository, or work from the file you have open. Chat and quick actions answer from the graph plus live tools — including Find Owner (CODEOWNERS), Blast Radius, and Trace Decision. Ghost-text complete as you type. Highlight a block, describe the change, and apply or reject a patch.
Ask
Chat, or five workflows: Understand Repo, Trace Decision, Find Owner, Blast Radius, and Knowledge Gaps. Slash commands include /understand, /trace, /owner, /blast, /gaps, /slack, /jira, and /confluence.
Complete
Ghost text as you type. Tab to accept. Completions start from the open file; on Pro, indexed dependents and ownership can ride along.
Edit
Highlight a block, describe the change, review an inline diff. Apply, retry, or undo. You stay in the file — Coop does not rewrite the tree on its own.
roles
Connect once. The whole org asks from VS Code.
Admins wire the stack in the admin portal. Developers never paste tokens.
Org admin (once)
- Connect GitHub, GitLab, or Bitbucket in the admin portal
- Connect company Slack, Jira, Confluence, Notion, and Google Docs
- Deep-Index the company repos the team should see
- Invite teammates (Pro and Enterprise)
Each developer
- Install the VS Code extension and sign in
- Pick Use repo on an indexed repository
- Ask, complete, and edit with shared company stack context
- No tokens to paste — integrations are org-wide, not personal
Install steps live in the getting started guide and the Owner's Manual.
faq
Straight answers
The loop above is the product. These are the questions it usually raises.
- Do I need a local clone of the repo?
- No. Deep-Index builds a remote map so you can understand a codebase without cloning, then deletes the temporary clone. In VS Code, pick Use repo on the indexed repository. Coop fetches file bodies from the code host when a question or edit needs them.
- Does CoopAI index Slack, Jira, and docs?
- No. Only code repositories are Deep-Indexed. Company Slack, Jira, Confluence, Notion, and Google Docs are queried live at chat time from the admin-connected workspace — shared across the org, not each developer’s personal accounts — so Coop does not keep a standing copy of those tools.
- Who connects GitHub and Slack?
- Org admins connect the company integrations once in the admin portal. Developers sign in to the extension and query that shared org context. They do not paste personal OAuth tokens in production.
- What if graph or ticket context is missing?
- Coop says what is missing instead of guessing. Code-only questions still work if Slack or Jira are not connected. Repo facts such as file counts come from the index — Coop does not estimate them.
- Can I choose the model?
- Not on Developer or Pro. Coop assigns a model per feature (chat, quick actions, edit, autocomplete). Provider keys stay on the Coop server, not in the IDE.
Short definition: What is CoopAI?. Versus other tools: Compare. Architecture and retention: Security. Feature tour: Product.
coop demo --repo yours
See the loop on your codebase
Book a walkthrough, or install the free VS Code extension and Deep-Index a repo.
code intelligence from your entire stack