[BUG] No events for gemini-cli

[ba11b0y]

Describe the bug

I'm using gemini-cli to try out agentsight, but it seems it's not loading any events. My agent is simply doing a bunch of read file operations. I've also checked that all the BPF programs are loaded using bpf prog list

To Reproduce

• Run gemini-cli and agentsight

Expected behavior

Screenshots

Desktop (please complete the following information):

• OS: Ubuntu
• Version: 24.04.1
• Kernel version: 6.8.0-51-generic

Additional context

It seems everything's fine from agentsight logs.

[sudo] password for rahul: 
Creating temporary directory...
Created temporary directory: /tmp/.tmpU3Kcon
Extracted process binary to: /tmp/.tmpU3Kcon/process
Extracted sslsniff binary to: /tmp/.tmpU3Kcon/sslsniff
Trace Monitoring
============================================================
✓ SSL monitoring enabled with 1 HTTP filter patterns
✓ Process monitoring enabled
✓ Logging to file: record.log
============================================================
Starting flexible trace monitoring with 2 runners and 1 global analyzers...
Press Ctrl+C to stop
[2025-09-04T18:06:48Z INFO  agentsight::server::assets]  Extracted frontend assets to: /tmp/agentsight-frontend-84ecc85a-671b-4cee-b0b7-b3894fa73034
 Starting web server on http://127.0.0.1:8080
   Frontend will be available once the server starts
[2025-09-04T18:06:48Z INFO  agentsight::server::web]  Frontend server running on http://127.0.0.1:8080

[yunwei37]

I checked this locally before replying: the gemini CLI on my machine is a Node entrypoint (#!/usr/bin/env node), and when I launched it the process showed up as comm=node, not gemini.

Example from ps on my machine:

node /home/.../bin/gemini -p test

So if AgentSight is filtering on gemini / gemini-cli, it can miss everything. Please try one of these instead:

sudo ./agentsight record -c node --binary-path "$(command -v node)"

or

sudo ./agentsight trace --ssl true --process true --comm node --binary-path "$(command -v node)" --server true

If you have many Node processes on the machine, the next step is to capture the exact target PID while Gemini is running and trace by PID or by the specific Node binary path. If you try the commands above and it is still empty, please paste:

ps -o pid,comm,args -C node

while gemini is running, and we can narrow it down from there.