> For the complete documentation index, see [llms.txt](https://docs.terrakube.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.terrakube.io/2.34.0/run-terraform/workspaces/overview.md).
# Overview
The workspace overview page provides you a summary of the current workspace state.
### Managing Workspace Tags
The right panel of the overview page shows the workspace's tags as chips. A key/value tag shows its key and its value, and a key-only tag shows just its key. Hover a chip to see the tag as `key = value`.
If you can manage the workspace, click **Edit tags** to open the tag editor. Each row of the editor is one tag, with a key and a value:
* **Add a tag**: click **Add tag**, then select an existing tag key or type a new key name, and optionally type a value. Leave the value empty to add a key-only tag. A new key name is also added to the organization's [tag keys](/2.34.0/set-up/organizations/tags.md).
* **Change a value**: edit the value of an existing row. Clear it to turn the tag into a key-only tag.
* **Remove a tag**: click the delete icon next to the row.
Click **Save** to send the removals, value changes and new tags at once, or **Cancel** to discard them.
{% hint style="info" %}
A workspace holds one value per key, so the key of a saved tag can't be edited. To use a different key, remove the row and add a new one.
{% endhint %}
Tags can also be set from the Terraform CLI with the `tags` attribute of the `cloud` block. See [CLI-driven Workflow](/2.34.0/run-terraform/workspaces/cli-driven-workflow.md#selecting-workspaces-with-tags).
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.terrakube.io/2.34.0/run-terraform/workspaces/overview.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
