This message was deleted.
# proj-agent-canvas
d
This message was deleted.
f
Ya, the scope of ID and provider is a good start. And reduces the threat vector, per your point Robert.
Openhands has tried to push to random repos when it had limit access credentials. Would be good to have both a best practices in repo setup and some controls to make sure it keeps the work in a specific repo. Doesn't run delete all your stuff from a repo.md or other hidden command.
w
it's hard to put strong guardrails around the LLM though. Prompt injection is incredibly hard to control for
f
I haven't looked at the infra yet. But if we treat the container in a way is a clean room. We can reduce the impact of prompt injection. Ie. If I copy over an external repo, and the default is that the container is not connected to anything, the user is in a good starting space.
Also it could be used to test/check that repo for vulnerabilities. I think my SecOps friends would love that.
w
the problem is you need e.g. GitHub credentials in there
You could maybe have a button to pull in those credentials post hoc
f
Also, the Github credentials you can scope them down. I'm not running Openhands with god mode in my repos.
Have to head out. Will create a few notes later.
👍 2
c
Yeah, given these discussions, i think maybe
<http://app.all-hands.dev/start?repo=All-Hands-AI/OpenHands|app.all-hands.dev/start?repo=All-Hands-AI/OpenHands>
would be good enough for now? Just open the repo but don't do anything else, and leave the option to the user. But yeah.. if there's a malicious
repo.md
😅
Is there a way to control this from Github ID config? Or i guess a more fundamental way to fix that is to have some sort of security analyzer actually working..
w
I think we should punt on this until we figure out how to do it securely
➕ 1
c
We could maybe add to the docs a note about choosing a limited scope for the token
w
This badge would only work in OH Cloud, where we choose the scope for you. And we need e.g. scope to push to repos
definitely good to scope tokens as tightly as possible, but we need pretty wide permissions