Copart, Member Mobile
A code assistant with no write access
I built an internal assistant for questions about our code, Datadog and Crashlytics.
- Role
- Built the platform
- Result
- Answers engineers’ questions without changing any of its sources.
- Built with
- Google ADK
- Gemini
- MCP
- Graphify
- Vector search
- SourcesQuestions go to the codebase, Datadog or Crashlytics.
- SearchVector search and a code graph built with Graphify.
- OpenOther tools read it through MCP servers.
- No write accessFixes go through a separate, human-approved service that opens draft pull requests.
A question
- Codebase
- Datadog
- Crashlytics
An answer
A fix
A person approves
Draft pull request
It cannot change anything.
Problem
The code assistant at Copart needed a firm boundary between answering questions and changing code. It must have no write access.
What I built
I built the internal assistant on Google ADK and Gemini. It directs questions to the codebase, Datadog or Crashlytics, using search and a code graph built with Graphify. Other tools can read it through MCP servers, a standard way for assistants to read data. Fixes go through a separate, human-approved service that opens draft pull requests.
Result
The code assistant can answer engineers’ questions without changing any of its sources. I’m now adding routing that chooses how to answer based on confidence.
I’ve kept this to what my resume says. Ask me for more detail when we talk.