---
title: "Point a question at the repo. Get a cited answer."
description: "Ara runs an agentic research pass over a codebase or problem, traces the real call paths, and reports findings with a citation behind every claim. Each run also writes back what it learned, so the next one starts smarter."
url: "https://ara.so/use-cases/research"
section: "Use cases"
---

# Point a question at the repo. Get a cited answer.

Ara runs an agentic research pass over a codebase or problem, traces the real call paths, and reports findings with a citation behind every claim. Each run also writes back what it learned, so the next one starts smarter.

## Explore, synthesize, report — with receipts.

### Reads the repo

Ara grep-walks the code, follows imports, and maps the call paths that actually matter.

### Routes the thinking

Deep reasoning gets a frontier model; broad file sweeps get a fast one. You set the budget.

### Reports with citations

Every claim links to the file and line it came from, so you verify instead of trust.

## A question becomes a verified answer.

### Frame the question

Point Ara at a repo, an issue, or an open question. It scopes the search and spins up an isolated workspace.

_Signal_

### Explore the codebase

Ara reads files, traces call paths, and reproduces behavior where it can — read-only, no changes to your branches.

_Reproduce_

### Synthesize the findings

It reconciles what it saw into a report: claims, evidence, open questions, and a recommended next step.

_Review_

### Update repo memory

What Ara learned about this repo gets written back, so the next run starts where this one left off.

_Wiki_

## Ask the question you've been avoiding.

Point Ara at the repo and let it come back with findings, citations, and a next step.