product

Context from your entire stack (not just your codebase)

token_validator.tsauth_routes.go

CoopAI

1import { validateSession } from './auth';

3export async function validateSession(payload: JwtPayload) {

4 // Validates signature before route handlers

5 if (!payload?.signature || !payload?.exp) {

6 throw new AuthError('empty_or_unsigned_payload');

7 }

8 return validate(payload);

Plays prompt → context → outcome · advances when complete · hover to pause

works with your models

Anthropic
OpenAI
Google
Fireworks.ai

indexed

Cross-repo context without cloning the monorepo

Lightning Mode Deep-Indexes a knowledge graph across services so you can understand the codebase without cloning the monorepo onto every laptop.

Built for teams with interconnected services — VS Code code intelligence where cloning everything isn't practical, and blast radius spans more than one repo.

Free: up to 3 Deep-Indexed repos · Pro: unlimited

Remote knowledge graph: Understand a codebase without cloning: ownership, dependents, and decisions stay on Coop infrastructure — file bodies fetch from the code host when you need them.
Cross-tool context: Company Slack and Jira in VS Code sit next to PRs and CODEOWNERS — shared org context your admin connected — so you can find a code owner and see blast radius before you merge.
Context you can verify: Trace answers back to code and team sources, with a clear view of what supports each recommendation. Review the evidence before you change the code.

REMOTE REPOSITORIES. CONNECTED CONTEXT.

YOUR CODE HOSTS

GitHub

GitLab

Bitbucket

Repositories stay remote.

DEEP-INDEX

One searchable map.

Symbols & dependentsOwners & history

payments / retry.ts

“If I change this retry policy, which services need an update?”

export function retryPayment() { return withRetry(payment, policy);}

Trace dependents across repos.

File bodies fetched on demand.

Shared repository context, in your editor.No monorepo clone on every laptop.

ask

Questions that used to take a Slack archaeology dig

Architecture, find a code owner, blast radius of a change, and the ticket that explains why — with company Slack and Jira in VS Code, across the repo graph.

/understandUnderstand Repo

I'm onboarding to coop-backend: where does webhook ingestion start, and how do events flow into the job queue vs GraphCache? What are the 5 files I should read first?

fromSymbol graphGitHubCODEOWNERS

// response

Start at webhook ingress → queue → GraphCache · 5-file read order

/traceTrace Decision

Why did we add zero-retention headers on auth_middleware.go? Pull the Slack thread, Jira ticket, and the design note that led to this pattern.

fromSlackJiraGitHubConfluence

// response

#platform-auth · PROJ-1847 · Auth RFC v2: pattern chosen for incident #inc-auth-992

/ownerFind Owner

Who owns services/billing/invoice_handler.go? CODEOWNERS says @platform-payments but blame shows @marcus: who should review a change to idempotency keys?

fromCODEOWNERSGitHubSlack

// response

Jessica Dawson · 90% blame · loop in @marcus_vance for auth routing

/blastBlast Radius

If I refactor TokenValidator.validate() in internal/auth/token_validator.ts, what breaks downstream across api-gateway and workers/webhook-processor?

fromSymbol graphGitHubSlack

// response

23 dependents · 6 repos · signature changes break api-gateway + webhook-processor

/gapsKnowledge Gaps

Before I ship changes to GraphConsistencyManager.applyEvent(), what am I missing: any Slack threads or Jira on webhook dedupe?

fromSlackJiraGitHubSymbol graph

// response

Undocumented dedupe path · last Slack thread 40d ago · no Jira for edge retries

/slackAsk Slack

Summarize the #billing-auth threads about empty-payload handling and link them to the commits that shipped the fix.

fromSlackGitHub

// response

3 threads · Sep empty-payload discussion · tied to PR #842

/jiraAsk Jira

Can you fix this bug by looking at PLATFORM-2847: null check missing in the webhook auth path?

fromJiraGitHubSymbol graphSlack

// response

Add null guard before validate() · match api-gateway PR #891 pattern

/editEdit selection

Select the refresh-token branch in oauth_refresh.ts and match rejection semantics from token_validator.ts: throw AuthError('empty_or_unsigned_payload').

fromSymbol graphGitHub

// response

Inline diff ready · AuthError guard matched · Tab to accept

/understandUnderstand Repo

I'm onboarding to coop-backend: where does webhook ingestion start, and how do events flow into the job queue vs GraphCache? What are the 5 files I should read first?

fromSymbol graphGitHubCODEOWNERS

// response

Start at webhook ingress → queue → GraphCache · 5-file read order

/understand·swipe or tap a commandauto-advances · hover to pause

change

Write and edit like a teammate who's already in the repo

Complete and edit in the open file with repository context. Review the diff and choose what to apply.

Complete
Ghost text that pulls dependents, ownership, and team AuthError patterns.
Edit
Highlight → describe → reviewable inline diff → accept / retry / undo.
Implement
Ticket-driven fixes that match real types, middleware, and linked Jira/Slack decisions.

Inline complete uses a dedicated route with provider request controls. Autocomplete docs · Edit mode

token_validator.tssession_store.go

Inline complete

1import { AuthError } from './errors';

3export async function validateSession(payload: JwtPayload) {

4 // Validates signature before route handlers

5 if (!payload?.signature

// graph · 3 callers · AuthError pattern

Want the loop, not the feature tour? Index → query live → stay in the file.

How CoopAI works →What is CoopAI? →Compare CoopAI →Security →

See CoopAI on your codebase

Install the extension, or spend 20 minutes on your actual repo with the founder.

Book a 20-minute demo on your repo Install the free VS Code extension

code intelligence from your entire stack