tracce

Troubleshooting

Resolve missing file events, agent discovery issues, and interrupted sessions.

No file events appear

  1. Confirm your terminal has Full Disk Access.
  2. Restart the terminal after changing the permission.
  3. Start a new trace and accept the sudo prompt for eslogger.

If you decline the prompt, tracce intentionally falls back to process, network, and agent-intent signals only.

tracce cannot find an agent

Make sure Claude Code or Codex is already running, then narrow discovery explicitly:

tracce attach --agent codex
tracce attach --agent claude
tracce attach <pid>

The dashboard is in the wrong terminal

The traced agent owns its terminal. Run tracce view in a second terminal to open the dashboard.

A session was interrupted

Repair ownership on session files with:

tracce fix-perms

Then list and replay the session:

tracce list
tracce view <session-id-prefix>

A flag pattern does not match

Patterns match the complete string. Add * on both sides for a contains match:

{ "warning": ["*sudo*", "*.env*"] }

Reload the patterns by reopening or switching the session.

On this page