Search in AI assistant chat history

[lougreenwood]

I have an extensive history of chats with the agent.

However, the search functionality is incredibly limited.

I can search from the list of chats, but searching only filters the list of chats (i.e the titles), there is no visbility into the context of the search results.

So, I go and open a chat, expecting to be able to search.... but nothing.

There is no ability to search within a chat.

So, I'm left with a massive chat history - some chats have very important details in them - and I have no way of surfacing them.

Ideally, what I want is for assistant search to be fully featured and based off of the project search (or even integrated as some kind of sub-filter/view).

I want to be able to search my history, be shown results for each hit with a few lines of context in either direction. I want to be able to open that chat with whatever the g space binding is, and go back using ctrl-o - just like file search results can be navigated.

[amarcin]

Would really love for this feature to be implemented.

[DarrelWirasena]

it would be really nice to have this feature as fast as possible

[Tahinli]

Guys this is what I can offer for now, I hope this is going to help

#54816

[dandv]

@KevinLaveto has just submitted a PR for across-thread search, including within ACP threads (by lazy-loading them), which solves the objection raised by @benbrandt to Tahinli's implementation.

[angristan]

I built https://github.com/angristan/fast-resume for this problem a few months ago (based on the tantivy search engine), and I'm really missing that in zed, it's very hard to find threads 🥲 would be happy to contribute a similar feature

[Tahinli]

It looks amazing!

[angristan]

thanks! so far the risk has been that the storage format used by coding agents is by no mean a stable API meant to be used externally, so it can break at any point. so far I think it happened once for opencode and once for vibe, but other than that it's really nice. also tantivy is rust so it fits zed pretty nicely

[franciskafyi]

Converted this to an issue that we're tracking here: #58676