Introduction
Learn how Estelle helps your team understand its code, delegate changes, review pull requests, test apps, and watch production.
View as MarkdownEstelle is made by Fate Labs.
Estelle gives your engineering team one place to ask questions about its code, hand changes to coding agents, and review the results. You choose which repositories Estelle indexes. It uses those repositories, your documents, and your recorded sessions to answer with sources and to carry work forward.
A typical change starts in Agent mode, runs in a Silo, and comes back as a pull request. You can follow the work in Orchestra, read Prism's review, and decide whether to merge.
#Start with one repository
- Create your account and index a repository. Use GitHub or the CLI.
- Ask a question in Ask mode and open the file and line citations in the answer.
- Give Agent mode a small, testable change. Approve the proposed work, then review the pull request it opens.
- Connect a supported native host or another MCP client if you want your local coding sessions to use Estelle too.
#Choose the right part of Estelle
| Product | Use it when you want to |
|---|---|
| Agent mode | Discuss and approve work, such as a code change, a scan, a test, or an automation. |
| Orchestra | Follow a build, send context to its agent, or stop work that is going in the wrong direction. |
| Silos | Run coding agents and their tools in cloud computers instead of on your laptop. |
| Prism | Review a pull request against the indexed repository and put findings on the relevant lines. |
| Twice | Test user journeys in a running staging or preview app and inspect each failure. |
| Security | Scan a repository for security problems and read the evidence and coverage for each scan. |
| Estelle CI | Run your build and test jobs in Silos and report their results as GitHub checks. |
| Monitoring | Collect production errors, logs, metrics, traces, and uptime results in one place. |
| On-call | Turn Monitoring signals into incidents, investigations, and alerts for your team. |
| Atlas | Generate a cited, readable guide to an indexed repository. |
| Intake | Upload company documents and ask questions with citations to the original lines. |
| Automations | Run reports, triage, or repository work on a schedule or when an event happens. |
| Sessions | Read coding-agent sessions from your machine and from Estelle's Silos. |
#Ask for an answer or approve an action
The dashboard's Estelle page has two modes:
- Ask answers questions from indexed code, saved decisions, and sessions. It does not start work. Use it to locate code, understand behavior, or revisit a decision.
- Agent can look things up and propose an action. Read the proposal, then choose Allow once, Always allow when that option is offered, Change it, or Refuse it. Nothing runs until you approve it.
For a code change, the usual path is:
- Describe the behavior you want and name the repository.
- Approve the proposal.
- Follow the coding agent's work in Orchestra.
- Open the pull request and read its diff, checks, and Prism review.
- Merge it yourself when you are satisfied.
#Work where you already work
- Dashboard: open app.fatelabs.ca for Ask, Agent, and every product above.
- Claude Code, Codex, Kimi Code, Grok Build and Cursor: install the native plugin to add Estelle's tools and report acknowledged session entries to the dashboard.
- Terminal: use the
estelleCLI to sign in, index a checkout, configure MCP clients, and diagnose a connection. - Other MCP clients: connect to
https://api.fatelabs.ca/mcpwith browser sign-in or an API key.
See Install Estelle for the exact setup commands.
#Read answers and refusals carefully
Estelle can answer only from the information available to it. Keep the index current as your repositories change.
- A citation identifies evidence behind an answer. Open it when the answer matters.
- Not swept, not indexed, or could not verify means Estelle lacks evidence. It does not prove that code is missing or that code is safe.
- A stale index describes an older version of the repository. Re-index before relying on the answer.