This post (perhaps soon to be a wiki) will outline all of the things you can and cannot do in terminal mode.
First up, though, how do you activate terminal mode?
Terminal mode can be activated in settings via a toggle switch, or by asking r1 to activate terminal mode via the ptt button. After this is done, rotate your device clockwise so that the scroll wheel is on the bottom.
Let’s get started…
What can you do?
[Ask r1 questions via text]
Seems obvious enough, but just as you can ask questions via the ptt button, you can type them here.
[Set timers]
Type your timer request to r1, and it will open the timer view with your timer. NOTE: r1 will occasionally speak out loud your timer initiation even in terminal mode.
[Set alarms]
Type your alarm request to r1, and it will open the alarm view with your alarm. NOTE: r1 will occasionally speak out loud your anlarm initiation even in terminal mode.
[Adjust Brightness]
Tell r1 to change brightness via text
[Adjust Volume]
Despite terminal mode being silenced, you can still adjust volume by asking r1.
[Toggle Bluetooth]
You can turn Bluetooth on and off via text request. Vague questions will open settings.
[Deactivate Terminal Mode]
You can actually crash the terminal mode by turning it off via request while using it
[Use a keyboard]
Plug in any USB-C compatible keyboard to the top of the device, and start typing away. You can even hit return to submit your query.
What can you NOT do?
[Use vision mode]
Vision mode is different than terminal and standard mode, and requires you to exit terminal mode to use it. Vision mode activation will exit terminal mode, and speak the answer aloud.
[Start Translation Mode]
You will need to exit terminal mode to do this.
[Start the Meeting Assistant]
You will need to exit terminal mode to do this.
[Access memory]
r1 has no memory retention from the rabbit hole in terminal mode.
[Run system diagnostics]
Terminal mode is not a Kernel, and only changes input from voice to text. (Plus disabling a few features)