---
title: "CI and checks"
description: "How the agent investigates CI failures, and where checks show up in a thread"
canonical_url: "https://hoplite.sh/docs/ci"
markdown_url: "https://hoplite.sh/docs/ci.md"
---

# CI and checks
URL: /docs/ci
LLM index: /llms.txt
Description: How the agent investigates CI failures, and where checks show up in a thread
Related: /docs/github, /docs/agent/tools, /docs/threads/run

# CI and checks

The agent can investigate your CI directly: it lists CI runs, inspects a run and its jobs, and reads a bounded log tail from a failed job. You don't need to paste logs into the thread.

## Where checks appear

A PR's status checks show in the [PR rail](/docs/github#the-pr-rail) alongside its reviews and unresolved comments. Hoplite tracks checks via webhooks, so when a check fails, that state is waiting for the agent on its next run.

## What the agent can do

For Actions investigation, the agent can list workflow runs, inspect a run, list its jobs, and read a bounded failed-job log tail — without an authenticated `gh` fallback. The GitHub App credential stays in Hoplite's trusted worker and is never exposed to the sandbox or forwarded to GitHub's signed log-download URL. The underlying tools are listed under [Source control](/docs/agent/tools#source-control).

## Ask the agent to fix a failing check

Point the agent at the failure and let it pull the logs itself:

```text
The lint check on this PR is failing. Look at the failed job's logs,
find the cause, and fix it.
```

The agent fetches the failed job's log tail, diagnoses it, and makes the fix in the sandbox like any other [run](/docs/threads/run).

## Sitemap

See the full [sitemap](/docs/sitemap.md) for all pages.
Well-known sitemap: [/docs/.well-known/sitemap.md](/docs/.well-known/sitemap.md).