I actually expected the models to perform better than they did, but I'm a bit of an optimist. It makes sense for the more mature SAST tool to outperform them just based on maturity alone.
Fair enough. To expand on that: you’re right, there is a friction hurdle. But we’re betting that the time-to-truth is more valuable to a recruiter than the 60 seconds it takes to chat with a Rep. If the Rep can verify a candidate’s salary requirements and technical stack in 2 minutes, it saves the recruiter a 30-minute wasted phone screen. That’s the ROI we’re aiming for.
It was probably due to the lack of flow control. Serial doesn't work well when it's one-way. I did something similar to send logs waaaay back in the day, and it would constantly flip bits or send characters out of sequence, etc. I had to transmit very slowly to get it to work stably without any flow control. I want to say that I limited it to 9600 kbps before it started to become reliable.
I did something similar with gemini cli by just wrapping it in tmux and building some extensions.[0]
Eventually that wasnt enough so I ended up forking it and adding REST endpoints to inject commands and read the screen.[1]
Your solution is much cleaner! I'll probably replace mine with it. Thanks for sharing!
[0] https://github.com/stevenAthompson/self-command
[1] https://github.com/stevenAthompson/gemini-cli-remote-control
reply