Show HN: OpenAI dev assistant GUI with local code interpreter | Hacker News Reader

Show HN: OpenAI dev assistant GUI with local code interpreter

github.com

67 pointsmdev2321 comments

Is there any reasonable way yet to allow ChatGPT to access the full contents of a GitHub repo and ask questions about it? I tried some months ago and hit a brick wall, not sure if anything's changed.

Tried now. I downloaded a whole repo for a Phoenix Project (so more than 1 file) and uploaded it to ChatGPT as a zip file. It works but answers are not perfect but I guess a python/javascript project should work better since it has more training data on those languages.

Aider might be what you are looking for

https://github.com/paul-gauthier/aider

thats the end goal for this type of tool. right now you just guide the bot into the repo and ask it to read individual files

I built a local developer-mode plugin that gives ChatGPT access to a local directory [0] -- it's pretty basic in terms of functionality (just simple bridge to access/read files) but I've found a surprising amount of value from it [1]!

[0] https://github.com/samrawal/chatgpt-localfiles

[1] https://samrawal.substack.com/p/example-driven-development

https://cursor.sh does a good job for me

you can give it a github link but the context size isnt big enough for large projects to be inserted directly.

maybe using the VScode plugin for phind

I wish there was a way to see exactly what its planning on doing before it does it when you say something like "save it to my desktop".

I was looking for something like this today! Thank you for building this

How is it different/better than Open-Interpreter?

web UI so it can best hosted on a server

cosine.sh was discussed here not long ago iirc

I’m convinced that the best way to do this is actually to have a local daemon that exposes itself as a regular ChatGPT plug-in with the necessary features. That way, we can use the regular ChatGPT GUI, but it can still access whatever we like. This should work since IIUC all ChatGPT plug-in API calls happen on the client computer already.

They do, chatGPT returns a list of tools it wants (this the right term?) to call and the arguments to call it with.

Up to the developer to map the args to the function and give the result back in the message history.

You misunderstood me. I’m saying instead of being a GUI, this could be a ChatGPT plug-in. That way the developer can focus on providing a smart API that does what the user wants, and not wasting time writing a GUI.

Why is writing a better UI a waste of time?

Plugins use webhooks; tools work the way you describe.

Neat! Nice that you made a somewhat proper UI for it.

Many tools like this, so many that I started keeping a list: https://github.com/ErikBjare/are-copilots-local-yet

I also built my own terminal based tool "gptme" (also with code interpreter abilities, and can run as a GitHub bot) that I use daily, instead of ChatGPT: https://github.com/ErikBjare/gptme

nice! i'll add a PR for DODA

On your list I'm not sure I understand what the "Editor Extension"/"Tool" distinction is. Both continue and rift are under "Tools", but they are VSCode extensions.

Reply on news.ycombinator.com