This thread has convinced me that Aider/Cursor need to do more marketing.
Maybe. But maybe some like the more disconnected way of coding with ai.
Why? It's just moving more of the grunt work of shuffling things around to the human?
Show HN: Transform your codebase into a single Markdown doc for feeding into AI
101–110 of 172 posts
Re: Show HN: Transform your codebase into a single Markdown doc for feeding into AI
#102Wouldn't it be wonderful to have a tool where you interact with AI interactively through the codebase via IDE / vim / emacs tree? Say, you open your codebase and start with prompts and AI+tool navigates to a function or a place where it needs to and modifies stuff while chatting to you about it? Or you jump to somewhere, highlight where you are to scope down the focus of it (while it still retains all of the code in…
I tried various solutions but I still haven’t found a chat tool that allows me to navigate a large monorepo. I’d like to be able to say "open the file where there is the function to do ", but current tools don’t understand that.
This works fine in Cursor. As far as I know, you can't say "open the file..." but you can say "where is the function to do " and it'll include a link to the file in it's response and then you can click to open it.
Re: Show HN: Transform your codebase into a single Markdown doc for feeding into AI
#103Re: Show HN: Transform your codebase into a single Markdown doc for feeding into AI
#104Does anyone know of tools that go the other direction? i.e. taking a technical writeup (scientific paper, architecture docs, or similar) and emitting a candidate codebase.
Yes, I often use one LLM to generate a PRD and the include it in the codebase, then ask Cursor agent to implement some part of the system using the PRD as a reference. It can't emit an entire codebase in one-shot (unless it's trivial project like "build me a flappy bird clone") but you can use it as scaffolding to manage implementing a whole project in chunks.
Re: Show HN: Transform your codebase into a single Markdown doc for feeding into AI
#105See the script I created that does something similar with a few improvements for large projects: https://paste.mozilla.org/9rD95yAy I would like to be able to create sets of files that I can easily send to the clipboard in this kind of format. The files could correspond to the ones relevant to a particular feature, etc. They don't always fall under the same subtree of the source code, and the entire source code is to…
Link says snippet deleted.
I made a better one that lets you add the files/paths and refresh and copy to the clipboard:
Re: Show HN: Transform your codebase into a single Markdown doc for feeding into AI
#106This is great, but I’m pretty sure this is trivial using Emacs and org mode. You could then use pandoc to convert org to markdown
It's trivial using a number of approaches, eg. a simple bash or python script. But I think there's still a fair amount of value in building a common tool for these sorts of things. Everyone that builds their own one off solution will inevitably encounter more and more of the edge cases (oh I need to honor .gitignore... oh, I need to be able to override .gitignore and include some ignored things... oh I need to deal with huge files... etc) and with a common tool the tool can collect the ways of dealing with all of these edge cases.
Now no one will need something that can handle all of the edge cases, but whatever edge cases they need to be handled will already be handled. The overall time and frustration saved this way can be huge.
Re: Show HN: Transform your codebase into a single Markdown doc for feeding into AI
#107how does this compare to code2prompt or files2prompt ?
any benchmarks on which one works better for LLMs ?
Re: Show HN: Transform your codebase into a single Markdown doc for feeding into AI
#108Another alternative is Gitingest
[0]. What are the differences?
Re: Show HN: Transform your codebase into a single Markdown doc for feeding into AI
#109Unfortunate naming, given that CodeWeavers is already a company making a Windows "emulator" for Linux and macOS. [1] [1] https://www.codeweavers.com/
CodeWeavers are actually making wine, not just some "emulator". They then distribute this along with some QOL tools as a commercial product called CrossOver.
Re: Show HN: Transform your codebase into a single Markdown doc for feeding into AI
#110CodeWeavers is a software company that focuses on Wine development and sells a proprietary version of Wine called CrossOver for running Windows applications on macOS, ChromeOS and Linux.
https://en.wikipedia.org/wiki/CodeWeavers
Trademark is active. It's an Ⓡ not just a ™, registered not just trademarked. To keep it, they have to demonstrate they defend it.
https://www.trademarkia.com/codeweavers-76546826
While this project drops the final "s", you don't get to launch an OS called "Window". The test is a fuzzy match based on likelihood of confusion.