Enable human input in the right area of OpenDevin, like file edit and terminal command execution.

[assertion]

What problem or use case are you trying to solve?
Right now, if OpenDevin write sth wrong in the file, like typo/grammar error, or provide some configuration content, I can't modify and provide it for OpenDevin.
And sometimes I'm pretty sure what to do, but OpenDevin just fails many times to solve some problem by executing some command, I want to execute the command for OpenDevin.

Describe the UX of the solution you'd like
I think we can make file area and terminal area inputable, when we pause OpenDevin. Then human do something for him, and resume to execute.

Do you have thoughts on the technical implementation?
We need to record what human do, like file content diff, terminal executed, and tell OpenDevin when resume him. Maybe just put the detail things human did to the chat message.

Describe alternatives you've considered

Additional context
I found some discussion about integrating a webide inside, but I don't think we need it to accomplish this at the early stage.

[PierrunoYT]

Im trying to add a option to edit the code in the code editor and save it since yesterday.

[PierrunoYT]

@assertion I think it's already possible to run commands inside the terminal right?

[assertion]

@assertion I think it's already possible to run commands inside the terminal right?

Yes, we can do it by login to the container, but I think it's more user-friendly if we can do it on the frontend page @PierrunoYT

[enyst]

@assertion You may want to check this out #2493, it should work already for the terminal. 😄

[mamoodi]

@assertion since the terminal part already works and we have this issue for editing the files in the UI: #855

Can this be closed as duplicate?

[assertion]

@assertion since the terminal part already works and we have this issue for editing the files in the UI: #855

Can this be closed as duplicate?

@mamoodi I'm not sure whether another part of this issue (enabling file edit by human) is planned or recorded in other issue? If so, we can link them and mark current one closed.

[tobitege]

Fixed with #2646
Closing this one.