Input TextBox or chat is now always available

With the latest build i’ve been bumped to the UX is vastly improved from the prior version, where I was now able to confidently enter through commands, refine my ask and ctrl+enter send, send the new command agent provided me via enter, at literally the speed of thought. Which is the ideal and standard we should be striving for.

It hasn’t really come up before but i pose a test case against the next ux changes. Just try and rapid fire ls some /etc/ dir’s letting some through, dynamically change a few of the dirs we want to point the agent at as part of the test. If it feels good to use and to ls some /etc/dirs’ it is good for everything else.

simple prompt sequence can be:
ls -la the sound driver configs of my computer

*let it get a couple in*
tell agent: wait no the video driver configs

and that’s the test. however fast and fluently you can perform this sequence is how good the state of rapid command sequencing is.

hi @koltanl, i was unable to reproduce the issue on Ubuntu.

Could you post a full separate Bug Report with more info including screenshot when the Chat or Input text box is not available. Create Bug Report

The Bug Report form has more fields that are required and help with debugging.

well on the 1.5 series of versions, when the agent is prompting the user to run a command, can you type in the chatbox? I could not. on the 1.6 series I can.

there’s not much more to it

in the 1.5 series the chatbox is grey’d out until i hit stop

1 Like

Ah great, thank you for the feedback and the screenshots.