You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The push guard keeps to a time budget of 20 seconds. A push could wait many minutes
while the leak check read every raw log again, until the remote closed the
connection and the push failed. Past the budget, the leak check matches what the
cache holds, says so, and saves what it read, so the next push goes on from there;
the check of secret formats always runs in full. llmpro check brings the cache up
to date.
The leak cache is kept across releases. It was dropped at every upgrade, so the first
check after one read every raw log again. It is dropped only when the rules for what
is collected change. The first check after upgrading to 0.1.2 still reads them once.
The MCP check tool reads raw logs for 20 seconds at most and is stopped after 60, so
the assistant is no longer left waiting for every other answer. Its result carries late, the raw logs not read in full in the time.
The Claude Code hook before each Bash call keeps to one budget of 8 seconds for both
of its gitpro calls. It could take 16, and Claude Code stops it at 10.
The sync's no-op cache is kept across releases unless the redaction code changed,
and is written readable by you only (it was readable by others). The first sync after
upgrading to 0.1.2 still redacts every file once.
Added
llmpro check --budget SECONDS reads raw logs for the leak check only this long and
checks the rest against the cache; the output says how many were not read in full.