[Feature Request/Question] Add some default semantic search/parsing capability #1759

Closed
opened 2026-02-16 17:32:31 -05:00 by yindo · 5 comments
Owner

Originally created by @logan-markewich on GitHub (Sep 18, 2025).

Originally assigned to: @thdxr on GitHub.

I maintain a small set of tools to help coding agents better interact with files in the CLI
https://github.com/run-llama/semtools

It provides two main commands

  1. search -- line-by-line semantic search using static embeddings (very fast). Think of it like a fuzzy grep/BM25 tool for keyword search
  2. parse -- likely less in alignment with opencode in its current state, but uses LlamaParse to parse documents into markdown. It has a very bash-pipe friendly format (basically making it possible to grep a PDF)

I've been using these a ton with Claude-Code, and it helps a ton with saving tokens and speeding up search for files.

If opencode is... open to it 😉 Happy to make a PR to integrate as new default CLI commands or discuss further!

Originally created by @logan-markewich on GitHub (Sep 18, 2025). Originally assigned to: @thdxr on GitHub. I maintain a small set of tools to help coding agents better interact with files in the CLI https://github.com/run-llama/semtools It provides two main commands 1. `search` -- line-by-line semantic search using static embeddings (very fast). Think of it like a fuzzy grep/BM25 tool for keyword search 2. `parse` -- likely less in alignment with opencode in its current state, but uses LlamaParse to parse documents into markdown. It has a very bash-pipe friendly format (basically making it possible to `grep` a PDF) I've been using these a ton with Claude-Code, and it helps a ton with saving tokens and speeding up search for files. If `opencode` is... open to it 😉 Happy to make a PR to integrate as new default CLI commands or discuss further!
yindo closed this issue 2026-02-16 17:32:31 -05:00
Author
Owner

@rekram1-node commented on GitHub (Sep 18, 2025):

Are you asking for them to be first party supported?

You should be able to integrate these on your end using the new user defined tools support: https://opencode.ai/docs/custom-tools/

@rekram1-node commented on GitHub (Sep 18, 2025): Are you asking for them to be first party supported? You should be able to integrate these on your end using the new user defined tools support: https://opencode.ai/docs/custom-tools/
Author
Owner

@logan-markewich commented on GitHub (Sep 18, 2025):

@rekram1-node more so asking about first party support, i.e. https://github.com/sst/opencode/tree/dev/packages/opencode/src/tool

@logan-markewich commented on GitHub (Sep 18, 2025): @rekram1-node more so asking about first party support, i.e. https://github.com/sst/opencode/tree/dev/packages/opencode/src/tool
Author
Owner

@rekram1-node commented on GitHub (Sep 18, 2025):

@logan-markewich decisions like that are up to @thdxr

I would say the team seems pretty hesitant to add new dependencies and from what I saw some people may need rust and cargo installed to use those tools which could be a deal breaker

But decision isn't up to me ultimately just wanted to state that, maybe that isn't the case for your tool but it seems like the readme says as much

@rekram1-node commented on GitHub (Sep 18, 2025): @logan-markewich decisions like that are up to @thdxr I would say the team seems pretty hesitant to add new dependencies and from what I saw some people may need `rust` and `cargo` installed to use those tools which could be a deal breaker But decision isn't up to me ultimately just wanted to state that, maybe that isn't the case for your tool but it seems like the readme says as much
Author
Owner

@logan-markewich commented on GitHub (Sep 18, 2025):

Cargo/rust shouldn't be a requirement, we are distributing via npm now, and can easily scale up the available platforms we build for (for now it covers nearly everything)

You can see the current list of assets/binaries on the latest release
https://github.com/run-llama/semtools/releases/tag/v1.3.0

@logan-markewich commented on GitHub (Sep 18, 2025): Cargo/rust shouldn't be a requirement, we are distributing via npm now, and can easily scale up the available platforms we build for (for now it covers nearly everything) You can see the current list of assets/binaries on the latest release https://github.com/run-llama/semtools/releases/tag/v1.3.0
Author
Owner

@rekram1-node commented on GitHub (Dec 27, 2025):

[automated] Closing due to 90+ days of inactivity. Feel free to reopen if you still need this!

@rekram1-node commented on GitHub (Dec 27, 2025): [automated] Closing due to 90+ days of inactivity. Feel free to reopen if you still need this!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#1759