# ExplainGitHub API

## ExplainGitHub API lets you build repo-aware AI features

Use repository context to power codebase chat, developer copilots, support tools, and internal workflows.

### Customer-facing developer products

Add “ask this repository”, PR summaries, issue copilots, or codebase chat directly into your product experience.

### Internal engineering and support tools

Help engineering, support, QA, or ops teams get answers from private repositories without manually searching code and docs.

### Docs, onboarding, and automation

Power docs assistants, developer onboarding flows, CI helpers, or internal automation that needs repository context.

### Instantly Understand Any GitHub Repository

Save hours of code review time with our official browser extension

[Add to Browser](https://microsoftedge.microsoft.com/addons/detail/explaingithub-%E2%80%93-turn-hour/mopfjhaboemmacmpeckofbiaokhpbike)

ExplainGitHub API is now live. Read the launch and technical walkthrough.

[Read more](/content/blog/ExplainGitHub-API/index.html)

# Smarter Chat

By ExplainGitHub Team•Dec 2, 2025•2 minutes read

## Smarter Chat — More signal, less noise

We’ve tuned ExplainGitHub’s chat to be sharper and more helpful out of the box. Answers are more grounded in the code, and follow‑ups stay on track.

## What’s improved

- Better retrieval: more relevant files pulled into context
- Clearer citations: file paths and functions called out explicitly
- Tighter answers: fewer tangents, more actionable steps

## Try prompts like

- “Where is pagination implemented for issues? Cite functions and files.”
- “Trace OAuth login → callback → token storage with file paths.”
- “List tests that cover `AuthService.refreshToken` and summarize assertions.”

## Coming next

- Inline diffs in answers for common refactors
- Deeper test coverage suggestions based on cited code