> For the complete documentation index, see [llms.txt](https://gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.com/docs/gitbook-agent/automatic-docs-improvements.md).

# Automatic docs improvements

{% hint style="warning" %}
**This feature is currently in early access.**

We’re slowly rolling out access. Stay tuned for more progress on the features below.
{% endhint %}

GitBook Agent can identify issues in your documentation — such as content gaps, outdated pages, and incorrect information — and suggest and implement improvements.

## What can GitBook Agent detect?

* **Content gaps** occur when GitBook sees users asking questions about your product that the docs struggle to answer, such as:
  * a customer asking a question to your support team that they couldn’t find on the docs.
  * an API endpoint missing complete documentation.
* **Outdated content** is detected when the content on your page has been superseded by content found in an external source, such as:
  * an SDK update that changed the signature of a function.
  * a paid feature that moved to the free tier, where the docs haven’t been updated.
* **Incorrect content** is flagged when the content on the docs site is explicitly wrong, such as:
  * a guide pointing to APIs that do not exist anymore, or where the feature has been sunsetted.
  * external sources such as your marketing website disagreeing with the documentation.

## How identification works

{% stepper %}
{% step %}

#### Connect sources

GitBook Agent works best when it’s connected to external sources like your support ticketing system, public forums, or marketing website. Some sources require an additional API key or authentication before setup is complete. [Learn more about our connections.](/docs/ai-and-search/connections.md)
{% endstep %}

{% step %}

#### GitBook Agent generates findings

GitBook regularly reviews your sources and generates findings based on the results. These findings are automatically pushed into your triage queue. [Learn more about how we ingest data.](/docs/ai-and-search/connections.md)
{% endstep %}

{% step %}

#### Review your triage queue

Open the **Triage** queue to start fixing issues. Each finding includes a summary of the issue, the topic it belongs to, supporting evidence, and links to the pages GitBook used as context.
{% endstep %}

{% step %}

#### Fix or archive

Some findings can be fixed automatically by GitBook Agent. When that option is available, you can create [change requests](/docs/collaboration/change-requests.md) directly from the finding. You can also archive findings you don’t want to keep in your active list.
{% endstep %}
{% endstepper %}

To request access to GitBook Agent’s automatic documentation improvement features, open your site’s **Settings**.

<figure><img src="/files/CeiKuQRDk8RPElOVfkzm" alt=""><figcaption></figcaption></figure>

## Triage

The **Triage** view shows the **findings** GitBook Agent has detected for your site. You can filter the list by **Topic** and **Severity** to focus on the findings you want to review first.

Each row shows the finding title and when GitBook identified it. Clicking a finding opens its full detail view.

### Triage details

When you open an item in Triage, you can review its details and summary. This includes **Status**, **Severity**, **Type**, and **Topic**, followed by a description of the issue and why GitBook flagged it.

Some findings also include linked evidence pages so you can review the source material behind the finding. Each row shows the finding title and when GitBook identified it. Selecting a finding opens its full detail view.

### Automatic fixes

When a finding supports automatic fixes, GitBook shows a **Create change request** action so the GitBook Agent can generate a proposed fix for your team to review. To skip the suggestion, archive the finding instead. GitBook won’t re-open findings that you’ve archived.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://gitbook.com/docs/gitbook-agent/automatic-docs-improvements.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.