> For the complete documentation index, see [llms.txt](https://kb.packfiles.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.packfiles.io/using-warp/migration-hq/labels.md).
# Labels
Warp’s issue labels, as seen in a list of open issues.
Warp’s issue labels, as seen on an issue’s page.
Warp automatically generates four labels for each issue it creates, which specify:
1. The repository’s **source organization**. In the examples above, the source organization is **joey-ado-testing** in Azure DevOps.
2. The repository’s **source team**. In the examples above, the source team is **first project** in Azure DevOps.
3. The repository’s **source**. In the examples above, the source is Azure DevOps.
4. The repository’s **activity**. In the examples above, the repository is inactive.
In addition to the labels that Warp automatically generates for issues, you can also assign your own labels to any issue.
---
# 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://kb.packfiles.io/using-warp/migration-hq/labels.md?ask=&goal=
```
`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.