> For the complete documentation index, see [llms.txt](https://djthorpe.gitbook.io/go-llm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://djthorpe.gitbook.io/go-llm/workspaces.md).

# Workspaces

{% hint style="info" %}
The Workspace is planned for go-llm 1.7 ([#246](https://github.com/mutablelogic/go-llm/issues/246)). Today, a conversation's files are its resources, which this page describes.
{% endhint %}

## Resources

A resource is a file go-llm keeps, such as an image, a document or audio.

* **Kept once,** by its SHA-256 hash, and referred to as `resource:///<hash>`.
* **A conversation's:** files you attach, or drop into the web UI, or send on Telegram, and files tools make, such as speech, images and transcripts.
* **Streamed** to and from the store, and downloadable in ranges, so long audio and video play as they load.
* **The Files panel** of a conversation lists its resources, plays audio and video, and attaches them to the next message.

```bash
llm resource-create report.pdf
llm ask -a resource:///<hash> "What does this say?"
llm resources
```

## Reading files

The `llm:resource` tool lists a conversation's files, and reads them as Markdown, a part at a time, carrying on where the last part ended. It reads text, HTML, CSV, PDFs, Word, OpenDocument, EPUB, spreadsheets, emails, calendars, subtitles and more, with [go-metadata](https://github.com/mutablelogic/go-metadata).

## Coming in the Workspace

* **Spaces:** a conversation's resources, connectors' MCP resources ([#292](https://github.com/mutablelogic/go-llm/issues/292)), and folders from your own filesystem.
* **Memory and help pages,** as spaces too.
* **Browsing and searching** across them, in the web UI and by the assistant.


---

# 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://djthorpe.gitbook.io/go-llm/workspaces.md?ask=<question>&goal=<user_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.