Troubleshooting

​

Install recipe fails

• Confirm you can reach https://install.corporatelabs.ai/install.sh
• Re-copy the recipe from the console (token may be wrong or revoked)
• Check OS/arch: Linux and macOS are supported via published binaries

​

clabs not found after install

• Ensure the installer put the binary on your PATH, or call the absolute path it printed
• Open a new shell so PATH updates apply
• On Linux with systemd, confirm ExecStart points at the installed binary (systemd guide)

​

Events not appearing in the console

1. Installation not revoked
2. Config present under ~/.config/clabs/
3. A sensor is actually running (discover, intercept, or CI via github.sh)
4. Wait a few seconds and refresh Events
5. Filter cleared (installation / type / asset filters can hide rows)

​

Intercept shows nothing

• Confirm you have permission to capture on the interface
• Check the process is still running and not exiting on error
• See Intercept for mode-specific notes

​

Wrong machine in the feed

• Each machine needs its own installation and recipe
• Do not reuse one install token across unrelated hosts if you want clean per-machine filters

​

Asset filter empty

• Set CLABS_ASSET_ID or -asset-id before the sensor emits events
• Events recorded without an asset id will not match an asset filter

​

Still stuck?

Open the console, confirm the installation status, and re-run the Install recipe on a clean shell. If CI is involved, check the workflow log for github.sh / clabs errors (GitHub Actions).