---
title: "Build Agent Context"
slug: "build-agent-context"
tags: ["unqorkai", "build-agent"]
status: "new"
updated: 2026-11-13T17:07:41Z
published: 2026-11-13T17:07:41Z
canonical: "docs.unqork.io/build-agent-context"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.unqork.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Build Agent Context

Build Agent context is the information that the [Build Agent](/unqorkai/docs/build-agent-overview) uses while it plans and builds. Two kinds of context exist, and each works differently. This article compares them and helps Creators decide where information belongs. A detailed article covers each kind.

## Types of Context

Chat context holds items that Creators add to a single task. Context Documents hold what the agent keeps for the whole workspace.

| Feature | Chat Context | Context Documents |
| --- | --- | --- |
| Scope | Chat context belongs to one task. | The documents belong to the workspace. |
| Contents | Modules, applications, Smart Components, and selections that Creators add to the task. | Entries that the agent writes, such as how the workspace's applications are designed. |
| Lifetime | Chat context resets when a new task begins. | The documents persist until a Creator deletes them. |
| Shared With | Only the Creator who owns the task. | Every Creator and every task in the workspace. |
| Managed In | The **Context** list above the prompt field on the **Active Task** tab. | The **Context** tab in the Build Agent panel. |
| Details | [Chat Context](/unqorkai/docs/chat-context) | [Context Documents](/unqorkai/docs/context-documents) |

Conversation history does not carry between [tasks](/unqorkai/docs/tasks-and-plans). Context Documents do, so the agent begins each new task with the workspace's shared knowledge.

## How Context Works

The agent has a limited working space for each task. Three things share it: the skills that the agent loads, the Context Documents, and the conversation. Chat context items count as part of the conversation.

At the beginning of a task, the agent loads the workspace overview from the Context Documents. As the task runs, the agent adds the items in chat context to the conversation and opens other entries when the work needs them. Each message adds to the conversation.

When the working space is nearly full, the agent summarizes earlier messages so that the task can continue. The context gauge in the prompt box displays how full the space is. For what each row means, see [Context Usage Gauge](/unqorkai/docs/build-agent-overview#context-usage-gauge). For how Context Documents count toward the total, see [Context Usage](/unqorkai/docs/context-documents#context-usage).

## Choosing Where Information Belongs

Add an item to chat context when the current task needs it. For example, add a module that the agent must read before it builds. The item leaves chat context when the task ends.

Record information in Context Documents when every task in the workspace needs it. Examples include how an application is designed and the conventions that the team follows. Creators can ask the agent to record information in the chat, or edit an entry directly.

---

**Changelog**

| Date | Change |
| --- | --- |
| 2026-11-03 | Replaced "like" with "such as" in the Types of Context table. |
| 2026-10-26 | Added How Context Works, which explains the working space and links to the context gauge. |
| 2026-10-23 | Added links to related articles. |
| 2026-10-23 | Reworked as a general article that compares chat context and Context Documents. Added Chat Context and Context Documents articles. |

Also known as Unqork Users, or Designer Users; is anyone who is inside the Unqork platform.

Scope is a tool that limits an application's access to a user's account. An application can request one or more scopes, this information is then presented to the user in the consent screen, and the access token issued to the application will be limited to the scopes granted.