> 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/user-guide/workspaces/terraform-state.md).
# Terraform State
Each Terrakube workspace has its own separate state data, used for jobs within that workspace. In Terrakube you can see the Terraform state in the standard [JSON format](#json-state) provided by the Terraform cli or you can see a [Visual State](#visual-state), this is a diagram created by Terrakube to represent the resources inside the JSON state.
### JSON State
Go to the workspace and click the **States** tab and then click in the specific state you want to see.
You will see the state in JSON format
You can click the **Download** button to get a copy of the JSON state file
### Visual State
Inside the **states** page, click the **diagram** tab and you will see the visual state for your terraform state.
The visual state will also show some information if you click each element like the following:
### Resources
All the resources can be shown in the overview page inside the workspace:
If you click the resources you can check the information about each resouce like the folloing
---
# 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/user-guide/workspaces/terraform-state.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.
