Using tmux to monitor Grok Bot troubleshooting via SSH connections

I’ve been making a lot of progress recently using Grok Bot to troubleshoot and resolve Librem 5 issues that have been plaguing me for months.

I was leery of giving it full root terminal access via SSH however. The solution I devised was the following.

  • Give the virtual linux machine running Grok Bot passwordless SSH login to the L5 using SSH keys.
  • Instruct Grok Bot to run everything in a tmux session called l5work.
  • Log every command to ~/l5work.log on the phone so it can be reviewed afterward.
  • Open my own SSH session to the L5 and attach tmux to the shared session so I can monitor the activity in real time.
  • Disable Grok Bot SSH key when done

The only issue with this is that it may have sent off data you don’t want sent off, and just reviewing the logs may be too late. If you don’t mind it grabbing any arbitrary file off your phone, then it doesn’t matter.

One way to work around it is to just have it give you commands to run, which you then paste the the terminal, then feed it the output. This way you know in advance what it wants and the results it gets. It’s way more tedious though.

Good point about the data exfiltration concerns and I agree 100%.

I don’t have any sensitive data on the phone at this point but it would be something to keep in mind for people that do.

Where I found it quite helpful was live troubleshooting of Gnome Calls SIP registration and calling issues.

Have you considered publishing a human-cleaned-up version of your log, that lists what a human could do on a Librem 5 to achieve the same benefits, for example if someone wants the value of your fixes without the potential risk of an agent having access to their device?

They can even do something like “write a brief summary of the fix” or “write a bash script that implements these fixes”.

No but wouldn’t be a bad idea. I’m trying to post fixes as I solve my punchlist problems with a link to relevant forum thread under the SOLVED text.

This scenario is a bit different than just a list of bash commands I can post. Grok Bot did a lot of Gnome Calls app launches with the debug option enabled to diagnose the problem. Then it used that diagnostic info to recompile the Gnome Calls app with several patches and backports included. I made that package and the fix summary info available here.

sorry about that linked to a DM, it’s been made public and the link fixed.

Another approach may be to

  • disk image your phone
  • blow the contents of the phone away and reflash from scratch
  • get AI to fix everything you want fixed, capturing what it is doing
  • restore the original disk image
  • manually do what AI previously did