Search -- Thoughts?

[ThePrimeagen]

I have created a new function, search

the premise is that you want to debug / search through the project and find out where something is happening, it will give you back a list of positions and add them to a quickfix list with a note, that way you can debug even faster.

I would love to hear some thoughts and if there was something better

[CadenFinley]

Maybe have it be able to compile the project for errors, parse debugger info, or do memory profiles for more info

[CadenFinley]

I would have to imagine this would be a marginal increase.

[harshv5094]

I think that depends on the price per token of the llm we're using

[Techie5879]

Just throwing this out here (maybe helpful or maybe not) - I have a similar "Agent" setup on my opencode with a "Deep-dive" prompt basically that instructs it to heavily parallelize search with faster smaller subagents to heavily look through repo context and return back with func_names, file_name, line nos.

Found doing that to be really useful. For the debug mode/memory profiling - I would more so think of it as like a skill - and I have implemented it similar to how cursor does so far - instructing the agent to spin up a local server, add wrapping around points of interest using a syntax very similar to cursor debug mode #agent:region debug-<id>, and this setup has been working well for me so far for memory profiling/debugging race conditions/runtime behavior.

[ThePrimeagen]

@Techie5879 share prompt?

[Techie5879]

@ThePrimeagen https://gist.github.com/Techie5879/222d43b7479a95226900e53d03a2abfe

Deep dive is a bit stupid rn - see comment why.
Also rn the way it outputs line numbers usually is <func_name>:<line_number> and its not clickable/jumpable. I do not know what I can do to make this jumpable - there probably exists a solution for this to pipe it to a nice tool to make the links clickable. Just have been working on other stuff (and I am yet to start using vim btw so I will be doing that when I cancel my cursor sub and switch over to nvim + 99 + opencode fully)

Debug is nice but I have been removing adding stuff slowly its a wip

[garma-a]

wow i really love this project and i think this is great idea you can make a shortcut where i can trigger analysis for potential bugs i have or describe the problem and in the background it read all my files and give me where i should look and why to be able to fix these bugs so i can use my quick list fast navigation for the syntax errors also logical errors and bugs

[wanghailiang888]

hello！I am a programming novice, currently self-learning AI large model programming to develop my own cash register and supply chain system for chain supermarkets. Thank you for your message.

[garma-a]

welcome !!

[wanghailiang888]

感谢

…

---Original--- From: "Aritra ***@***.***&gt; Date: Tue, Feb 10, 2026 15:27 PM To: ***@***.***&gt;; Cc: ***@***.******@***.***&gt;; Subject: Re: [ThePrimeagen/99] Search -- Thoughts? (Discussion #107) @ThePrimeagen https://gist.github.com/Techie5879/222d43b7479a95226900e53d03a2abfe Deep dive is a bit stupid rn - see comment why. Debug is nice but I have been removing adding stuff slowly its a wip — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***&gt;

[sekacorn]

My Opinion: I think that’s a good idea. We shouldn’t just capture the location; we should also include manual navigation paths showing how to get there. That way, people like me can still learn the process step by step. It would make the experience seamless and give users the ability to backtrack when needed.

[ThePrimeagen]

This isn't a project for people trying to learn. I am fully stoked you are learning, but this is intentionally built for people who want to use AI while remaining autonomous. It's for tradcoders if you will

[sekacorn]

Oh I see now,your focus is mainly experience or seni0r devs in general. I respect. I was simply looking out juniors who may come
to try out the project as test. But I think there’s another problem we can’t ignore: the pipeline of future engineers.
If we don’t invest in beginners now because companies are not, we risk weakening the entire industry later
because every senior engineer started as a junior looking at the screen for 3 hours not seeing the missing semi colon, yet
companies are hiring fewer juniors because of cost, and fewer people are stepping in to mentor or build tools for them.
Most of the attention goes to developers who already know what they’re doing.

[sekacorn]

While, AI is enabling people with no technical background to ship software. That isn’t inherently bad,
but if they’re building systems they don’t truly understand ,
and no one is creating tools to guide them we could end up with fragile software ecosystems that no one
can maintain long-term.
We also can’t keep defaulting to "just ask GPT to explain it if it breaks." People in general to take the easiest path, and
without structure or learning support, that leads to shallow understanding and false self confidence they can take to an interview.

This isn’t just about "vibe coders." It’s about stewardship.
If experienced engineers don’t help shape the next wave with better
tools and learning paths, the
industry risks drifting toward a future where critical
systems exist without deep understanding behind them. Because Companies are not investing they just want Senior dev with like 10000 yrs of exp

In my view, the real issue isn’t people using AI without technical
skills it’s the lack of tools that help
them actually learn while building, instead of throwing the "it fixes an issue as it what it did" no one of these
vibe coders is excited to pick up a book.

[Techie5879]

What is happening here lmao is this all just AI generated?

[sekacorn]

Its Ai summarised to make as coherent to The prime as I can

[ThePrimeagen]

I love search, I'm going to keep it