Skip to main content
Ask Sourcebot gives you the ability to ask complex questions about your codebase in natural language. It uses Sourcebot’s existing code search and navigation tools to allow reasoning models to search your code, follow code nav references, and provide an answer that’s rich with inline citations and navigable code snippets.

Configure language models

Learn how to connect your language model to Sourcebot

Index repos

Learn how to index your repos so you can ask questions about them

Deployment guide

Learn how to self-host Sourcebot in a few simple steps.

Public demo

Try Ask Sourcebot on our public demo instance.

​
Why do we need another AI dev tool?

Existing AI dev tools (Cursor, Claude Code, Copilot) are great at generating code. However, we believe one of the hardest parts of being a software engineer is understanding code. In this domain, these tools fall short:
  • You can only ask questions about the code you have checked out locally
  • You get a wall of text that’s difficult to parse, requiring you to go back and forth through different code snippets in the response
  • The richness of the explanation is limited by the fact that you’re in your IDE
We built Ask Sourcebot to address these problems. With Ask Sourcebot, you can:
  • Ask questions about your teams entire codebase (even on repos you don’t have locally)
  • Easily parse the response with side-by-side citations and code navigation
  • Share answers with your team to spread the knowledge
Being a web app is less convenient than being in your IDE, but it allows Sourcebot to provide responses in a richer UI that isn’t constrained by the IDE. We believe this experience of understanding your codebase is superior, and we hope you find it useful. We’d love to know what you think! Feel free to join the discussion on our GitHub.

​
Troubleshooting

  • Network timeouts: If you are hitting generic “network error” message while the answer is streaming when Sourcebot is deployed in a production environment, it may be due to your load balancer or proxy not being configured to handle long-lived connections. The timeout should be configured to a sufficiently large value (e.g., 5 minutes).