ci-logs

To analyze CI logs using a run hash, you pass the extracted URL hash from ci.aztec-labs.com to a specialized subagent. This delegated workflow processes the protected log data to identify failing steps and errors without requiring direct authenticated web access.

The best way to triage test failures from protected CI runs is to use a delegated log analysis subagent. By providing the CI run hash and a specific test name, the subagent safely downloads and inspects the logs to pinpoint the exact failure cause.

No, you cannot use WebFetch or direct curling to download CI logs. The workflow strictly forbids direct HTTP calls and instead requires delegating the log download via the built-in `yarn ci dlog` command to maintain an authentication-safe environment.

To identify specific failing steps in a continuous integration run, you request a failure-focused log triage using the run's URL hash. The analysis subagent processes the extracted log data to isolate errors and highlight the exact steps that caused the failure.

You do not need an authenticated session to inspect continuous integration logs if you use the delegated subagent workflow. It bypasses the need for direct authentication by utilizing the built-in `yarn ci dlog` flow to securely retrieve the log data.