Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
bshzzle
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
by
bshzzle
1y ago
Hey just following up on this - we just shipped support for any model that supports the OpenAI Chat Completions API (1), including Ollama and Llama.cpp. You can checkout the docs here: https://docs.sourcebot.dev/docs/co
2.
▲
by
bshzzle
1y ago
Yea it's a similar idea - DeepWiki has the generated "wiki" part which we think is really cool (and maybe we'll add something similar in the future). The core chat experience is the same idea - we had some UX inspiration
3.
▲
by
bshzzle
1y ago
We went with Zoekt because it is full-featured (it's fast, supports regex, search filters, streamed search, etc.), and is a mature project. Sourcegraph, GitLab, and other large companies use it, so it felt like a safe choice. Overall o
4.
▲
by
bshzzle
1y ago
awesome glad to hear! We are monetizing enterprise features like audit logging and SSO. The core product will remain free and under a FSL license.
5.
▲
by
bshzzle
1y ago
Yea they are currently separate - the MCP server exposes out the same tools that Ask Sourcebot uses, but the actual LLMs call is on the MCP client. It would be interesting to merge them though - maybe have a Exa style MCP tool that lets MCP
6.
▲
by
bshzzle
1y ago
Ah I was just replying to your previous comment - I'm guessing you found this? ;) https://docs.sourcebot.dev/docs/connections/local-repos Thanks for the support!
7.
▲
by
bshzzle
1y ago
You certainly could create an embedding of your code and then hooking it up to OpenWeb UI or equivalent as a chat interface - we've actually spoked to some teams that have rolled their own custom solution like that! From a product POV:
8.
▲
by
bshzzle
1y ago
Running Sourcebot with a self-hosted LLM is something we plan to support and have documented in the golden path very soon, so stay tuned. We are using the Vercel AI SDK which supports Ollama via a community provider, but doesn't V5 yet
9.
▲
by
bshzzle
1y ago
We used Perplexity as a mental mapping since there is some overlap, e.g., LLMs using search and citing its sources, it's a webapp, etc.
10.
▲
Show HN: Sourcebot – Self-hosted Perplexity for your codebase
(github.com)
103 points
by
bshzzle
1y ago
|
29 comments
11.
▲
Sourcebot MCP – Self-Hosted Agentic Code Search for GitHub, Gitlab, and More
(npmjs.com)
3 points
by
bshzzle
1y ago
|
0 comments
12.
▲
I built an AI code review agent in a few hours, here's what I learned
(sourcebot.dev)
3 points
by
bshzzle
1y ago
|
0 comments
13.
▲
Bitbucket search that doesn't suck – Sourcebot, OSS alternative to Sourcegraph
(sourcebot.dev)
8 points
by
bshzzle
1y ago
|
0 comments
14.
▲
Share links in Sourcebot, our open-source code search tool
(sourcebot.dev)
2 points
by
bshzzle
2y ago
|
0 comments
15.
▲
Open-source code-search tool Sourcebot now supports searching multiple branches
(github.com)
3 points
by
bshzzle
2y ago
|
0 comments
16.
▲
Open-source code-search tool Sourcebot now supports Gitea
(github.com)
21 points
by
bshzzle
2y ago
|
2 comments
17.
▲
by
bshzzle
2y ago
I like this idea! Will fix this in a sec.
18.
▲
by
bshzzle
2y ago
Yes - there is a file watcher that should pickup modifications to the configuration file. And you can persist indexes across restarts by mounting a volume to the `/data` directory (e.g., `-v $(pwd):/data`). Indexes are stored in a
19.
▲
by
bshzzle
2y ago
Hey! Yea that is correct - in its current state, it's functionally a UI wrapper on top of the zoekt-webserver api. One of the reasons why we decided to go with a separate app is that we have much more experience with Typescript, React,
20.
▲
by
bshzzle
2y ago
Thanks for the thoughtful question. This is still day 1, so we honestly don't have an answer if we will get to a point where we can monetize - it's too early to tell. However if we do end up going down that road, I don't thin
21.
▲
by
bshzzle
2y ago
No just GitLab and GitHub atm - but please feel free to file an issue for Perforce support.
22.
▲
by
bshzzle
2y ago
Yea exactly - on ingest it clones the repos and will periodically fetch new revisions. Currently we don't support in-place repos, but feel free to file a issue and we'd be happy to take a look.
23.
▲
by
bshzzle
2y ago
Currently, we don't have any plans of monetizing - the main focus for us right now is building something that people want to use :)
24.
▲
by
bshzzle
2y ago
yes definitely - mind opening a issue so we can track it?
25.
▲
by
bshzzle
2y ago
Thanks! Yea we would definitely like to support more code-hosts. If you have a sec, could you open a issue so we can track it?
26.
▲
by
bshzzle
2y ago
I think in the immediate term, we would like to talk to as many people as we can that have this "search across many repos" problem such that we can dial in the core search experience. Looking beyond the immediate, I think there is
27.
▲
by
bshzzle
2y ago
yea it's a fair question - an IDE is often more convenient when you have the code checked-out locally. This becomes a pain when you work in a organization with potentially hundreds of repositories that you need to search across (e.g.,
28.
▲
Show HN: Sourcebot, an open-source Sourcegraph alternative
(github.com)
259 points
by
bshzzle
2y ago
|
59 comments