And I think we should build it out in small steps that make sense individually.
I will add code to allow “branching” from any point in chat in to a new chat an d propose to merge my PR.
I will add “uploading” of files and direectories that will work as new chat message if not one beats me to it.
That will enable us to do git import next, should be done along with oatuh/jwt login
From there we can investigate syncing message chat and files states. We should reuse git efficency at snapshoting file system state. AND we can add something like .chatHistory folder to store in git chat state itself along with commands. This will sync git/file/chat. There are some pros and cons to that. We can get to them when we cross that bridge.
There are efficiency problems and bugs in how it all works, it can be addressed as paralle efforts, like work you are doing codacus with improving and fixing action runner.
I checked your PR, looks interesting, I need to test it. May be in the evening, need to go now.
Y’all are awesome, just had to say so. This is a great example of convo toward true solution. I’m always open for any PR review needed that comes out of this
You’re doing amazing work.