product

Context from your entire stack (not just your codebase)

CoopAI indexes your codebase and the tools your team already uses, then uses that context in every answer and every line you write.

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

ask

Questions that used to take a Slack archaeology dig

Architecture, owners, blast radius, and the ticket that explains why. One place, across the repo graph and the tools you already use.

/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, using the graph. You review the diff. Nothing rewrites the tree on its own.

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 separate zero-retention path. 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

indexed

Cross-repo context without cloning the monorepo

Lightning Mode indexes a knowledge graph across services so you get context without cloning the monorepo onto every laptop.

Built for teams with interconnected services, where cloning everything isn't practical.

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

Remote knowledge graph: Index via webhooks and jobs: ownership, dependents, and decisions, without a full local clone.
Cross-tool context: Slack, Jira, PRs, and CODEOWNERS sit next to the symbol graph, not in someone's head.
Honest when incomplete: When graph data is missing, Coop says so instead of guessing.

PR #842

merged 12d ago

PROJ-1847

In Progress

#platform-auth

2 threads

Auth RFC v2

Confluence

3 commits · 90d

@marcus · @elena

14 downstream refs

3 packages

auth_middleware.go

internal/auth/ · AuthMiddleware()

pulling context…

0/6 sources · Trace Decision

Stack → Coop → grounded answers

coop - zsh

coop demo --repo yours

See CoopAI on your codebase

Book a demo with our team or install the free VS Code extension from the Marketplace.

Book a demo Install extension

code intelligence from your entire stack