We just launched Sourcebot V5, our biggest release yet.
Combine multi-repo code analysis with context from Linear, Slack, Notion, and more. All in our redesigned interface that's deployed fully on-prem.
Try it now by running `npx setup-sourcebot`
What we shipped last week (Mar 23 - Mar 29):
- The MCP server now supports glob and list_tree tools, letting MCP clients find files by pattern and browse directory structures in a codebase.
- The file viewer now respects .gitattributes language hints, so files get the correct syntax highlighting when a repo overrides the detected language.
- Search contexts can now be filtered by GitHub and GitLab topics, making it easier to scope searches to a specific group of repos.
- Also: Fixed auto-scroll in ask threads, regex queries with parentheses being split incorrectly, line numbers being accidentally selected alongside code in Safari, and GitLab sync cleaning repos on non-404 API errors.
broke: paying $1K to have someone fix your openclaw deployment
bespoke: using up our YC claude credits to ask Sourcebot for free
just prepend "ask" to the openclaw github repo url
What we shipped this week (Mar 14 - Mar 21):
- Admins can now restrict API key creation and usage to organization owners only.
- MCP search_code now supports filtering by file path using regular expressions.
- Redis TLS is now supported.
- Also: agent max step count raised from 20 to 100, MCP read-only annotations for Cursor Ask mode compatibility, ask_codebase hidden when no LLM providers are configured, and SMTP individual env var support.
broke: answering user questions manually
bespoke: letting your users ask questions directly on your codebase using Sourcebot
just prepend "ask" to any public github repo. available to all public github repos for free
PRs for @sourcebot_dev have 5x'd in the past 2 months
agents used to be our assistants but they're quickly becoming the default mechanism we use to ship code
top bottlenecks we're experiencing:
it may come as a surprise to some but many companies are still using bitbucket
today we shipped bitbucket permission syncing to allow these companies to enforce repo visibility rules in @sourcebot_dev
[Changelog 📓] Account Linking
We've added the ability to link multiple external identity providers to Sourcebot. This allows you to:
- Connect to multiple different code host platforms and sync permissions across all of them.
- Configure SSO with a provider that isn't your code host platform, but still connect to the code host to sync permissions.
[Changelog 📓] Performance & stability improvements
We’ve been heads down solving some deep technical problems in order to make Sourcebot scalable and performant for larger instances. Highlights:
- 41x search time improvement for unbounded queries.
- 10x improvement to web app responsiveness.
- Reduced indexing error rate on 10k+ repositories from 5% to 0% on test deployment.
[Changelog] GitHub & GitLab permission syncing
Code hosts like GitHub & GitLab support configuring access control lists (ACLs) that define what repositories a user can and cannot see. We’ve shipped experimental support for syncing these ACLs with Sourcebot.
Sourcebot (@sourcebot_dev) helps developers and AI agents understand massive codebases.
It's used daily by engineers at some of the largest companies in the world, including NVIDIA, Red Hat, and Arista Networks.
Congrats on the launch, @msukkarieh1 & @bshizzle28!
🧵 [1/n] I hooked up GPT 5 w/ Sourcebot and asked it the open ended question of "How does repository indexing work in Sourcebot?"
Overall, its answer was pretty impressive, and looks to be a improvement on o3.
We just hit the front page of HN again with our recent Ask Sourcebot release! Be sure to check out the post there for a more detailed breakdown of the launch