Asked often.

No. It authenticates with read-only scopes only — it cannot push, merge, open pull requests, or change a single line. It's an answering machine, not a coding agent.

GitHub first, during the beta. Most mainstream languages are covered; exotic or generated code gets honest "I can't reliably read this" responses instead of guesses.

Then Maulwurf says so. Every answer is built from retrieved evidence with citations; when the evidence isn't there, the item is marked uncertain — never invented.

Citations point to the exact commit and line the answer came from, so you can verify in one click. Treat them like a map: usually right, always checkable, never blindly trusted.

Yes — arguably where it shines. Cross-service questions ("where does the auth token refresh happen?") are exactly what the excavation pipeline is built for.

Only your team. Indexes are isolated per customer, never used to train models, and you can purge everything at any time. See the Security page for details.

You apply as a design partner, we connect your repositories together, and your team starts asking questions — free during the beta. Your feedback shapes what we build next.