Creating a draft of future UI

[Notnaton]

Describe the changes you have made:

Reference any relevant issues (e.g. "Fixes #000"):

Pre-Submission Checklist (optional but appreciated):

• [ ] I have included relevant documentation updates (stored in /docs)
• [x] I have read docs/CONTRIBUTING.md
• [x] I have read docs/ROADMAP.md

OS Tests (optional but appreciated):

• [x] Tested on Windows
• [ ] Tested on MacOS
• [ ] Tested on Linux

[Notnaton]

[Notnaton]

Figure out how to get OI to answer to user input requests like python's input(). Do we somehow detect a delay in the output..? Is there some universal flag that TUIs emit when they expect user input? Should we do this semantically with embeddings, then ask OI to review it and respond..? Multi-line input. Probably use textual Placeholder text that gives a compelling example OI request. Probably use textual Everything else textual offers, like could we make it easier to select text? Copy paste in and out? Code editing interface? Let people edit the code OI writes. Could just open it in the user's preferred editor. Simple. https://github.com/KillianLucas/open-interpreter/pull/830#issuecomment-1854989795 Display images in the terminal interface

This is what I want this to cover, you will find this in the roadmap