-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Autonomous Coding Agent #105
Comments
It would be great to conduct an experiment with these autonomous agents. |
@pavlovcik For example, the robot can solve simple issue like minor bug. |
From what I understand, they already did all the hard work of making it smart. You just need to "connect the wires" basically set it up for use in our org/repos. Not sure the best way to implement, probably as CI in a single repo to start. Later should be integrated into our UbiquiBot so that it can run across all of our repos. |
Got it. First, I'll try to connect the SWE-Agent as originally designed to address the issues in our GitHub repo. |
/start |
Tips:
|
/wallet 0x712913366F98aa0A5E77EfddA05BaC65C52ae9bD |
+ Successfully registered wallet address |
@0x4007 Can you give me more details on this , like which tasks exactly should be included to use with the coding agent ? And once issues are fixed with the coding agent , should there be a pr raised for the changes made by the coding agent ? |
I have sort of loose expectations for this. It's mostly a research project to set this up and get it working. In order for it to be indisputably set up correctly, perhaps we can run this as part of our CI on new issues created. So when a new issue is filed, it can open a pull request right away. This could be very useful for contributors to start work from! |
Meaning that the autonomous coding agent understands the issue filed , does the code changes that it understands and then make a pull request in the repo ? is that what we are looking to do ?(and set it up as a CI to auto capture and run whenever a new issue is created ?) @0x4007 |
Yes it seems that the open source project did the heavy lifting, you just need to invoke it from a GitHub Action (with an issue created listener.) And possibly need to feed the relevant GitHub data in as a parameter of sorts. Then ideally we should have a pull request output. We might even be able to break that apart into separate tasks, but the purpose of this task is to see if that tool actually works as advertised. Connecting all the wires end-to-end can potentially be handled iteratively if they are too large of projects. At minimum output in the logs the results of the program. |
I would suggest to review GitHub Copilot Workspace Tools similar to SWE agent |
@0x4007 these tools require docker build and deploy and then creating a conda env which is not possible to create inside github action environment https://github.com/harjaapdhillon16/code-rover |
Anything is possible in a GitHub action environment. It's a Linux box. You can do it. |
https://github.com/harjaapdhillon16/code-rover @0x4007 someone else can continue on this , I developed it to the point where I have developed the docker image , but I have tried nearly everything I am not able to create an environment where I can execute this. |
/help |
Available Commands
|
/stop |
+ You have been unassigned from the task |
/start |
Tips:
|
/stop |
+ You have been unassigned from the task |
Available Commands
|
1 similar comment
Available Commands
|
/start |
! Please set your wallet address with the /wallet command first and try again. |
! No wallet address found |
- error: missing required argument 'address' |
@gentlementlegen three messages is unnecessarily verbose |
@0x4007 Only the first one is relevant and should have been displayed. I think this has been addressed in a PR within |
We can work with Cline instead. I also think this should be a plugin that can run when issues are filed. |
https://github.com/nus-apr/auto-code-rover
https://x.com/abhikroychoudh1/status/1777494000611852515
This might be worth setting up as an experiment first, and then a github action that responds to new issues being opened, with an event dispatcher so that we can run when specifications are modified and finalized.
Finally we can make it a plugin for our kernel as part of a future task.
I imagine it will do well with the simpler, and tighter scoped tasks!
The text was updated successfully, but these errors were encountered: