Unqork documentation is available in two workspaces: UnqorkAI for the latest AI-first platform, and legacy Unqork for previous versions. Use the drop-down near the logo to switch.

This article covers UnqorkAI features. UnqorkAI requires an active AI capabilities agreement. To upgrade from Unqork 9.0 or learn more, contact your Unqork representative.

Context Documents

Prev Next

Context Documents are entries that the Build Agent keeps for a workspace and reads at the beginning of every task. Every Creator in the workspace shares them. This article explains how the agent uses them and how Creators view, edit, and clear them in the Context tab. It also explains how administrators turn the feature on or off. For a comparison with chat context, see Build Agent Context.

How the Build Agent Uses Context Documents

Every workspace has a workspace overview, the first entry in its Context Documents. The agent loads this entry at the beginning of each task. The overview lists the workspace's applications and points to other entries for detail.

The agent opens other entries when the work calls for them. It also creates and updates entries as it works, and it explains each change in the chat. Each Creator can read and edit these entries, so the documents act as a shared store for the whole workspace.

The agent follows the conventions recorded in Context Documents when it builds. A request in the current task takes priority over a recorded convention.

An administrator can turn Context Documents off for an environment or for a single workspace. When the feature is off, the agent does not read or write entries, and the Context tab is hidden. For setup steps, see Administrator Settings.

Context Tab

[docs-interactive-image:{"surface":"build-agent/context","anchors":{"Context":"context-tab","Context Actions":"clearing-context-documents","Workspace Overview":"how-the-build-agent-uses-context-documents","Architecture":"entry-types","Convention":"entry-types","Active work":"entry-types","Reference":"entry-types"}}] Build Agent panel with the Context tab open, listing the workspace overview and one entry of each type: architecture, convention, active work, and reference

The Context tab lists the Context Documents for the current workspace. Select the BookOpen tab icon next to History in the Build Agent panel to open it.

Element Description
Context Opens the list of Context Documents for the workspace. The tab is hidden when an administrator turns the feature off.
Context Actions Opens a menu with the Clear all topics action. Only Creators with Admin permission on the workspace see this menu.
Workspace Overview The first entry in the list. The agent loads it into every task, and it cannot be deleted.
Entry One row for each Context Document. A row displays the title, a type label, and a short summary. Select a row to open the entry.

When the workspace has no entries, the tab explains that the agent creates and maintains them as it works. Creators can also ask the agent to record something in the chat.

Entry Types

Each entry has one of the following types.

Type Use
Architecture Describes how an application is designed, including its modules, how they connect, and why the design choices were made.
Convention Records a standing instruction for how the team builds.
Active work Tracks a goal that takes several tasks, including what is done and what remains.
Reference Points to outside resources, such as tickets or design documents.

When the list grows long, filter buttons display above it. Select All or a type to narrow the list. The workspace overview always displays at the top.

Viewing and Editing an Entry

Select an entry in the Context tab to open it in the center of the Module Builder. The entry displays its title, type label, summary, and the following details line:

  • The source of the last change, which is either the agent or a Creator.
  • The version number.
  • The date of the last change.

Hover over the details line to display the ID of the author.

The entry header has the following actions.

Action Description
Edit Replaces the entry content with a text editor. Enter a short change summary, then select Save. The summary is required. Select Cancel to discard the edit.
History Opens the list of earlier versions.
Delete Removes the entry after a confirmation. The agent stops loading the entry, and earlier versions stay in its history. The workspace overview has no delete action.

Version History

Select History in the entry header to list every saved version. Each row displays the version number, a change summary, the source of the change, and the date.

To review an earlier version:

  1. Select a version in the list. The banner Viewing version N displays above the content.
  2. Select Show changes or Hide changes to mark or unmark the lines that version added.
  3. Select Back to current to return to the latest version.

Content Screening and Edit Conflicts

The platform checks each save for credentials, secrets, and text that reads as a prompt attack. When a save contains this kind of content, the platform rejects it and displays a message. Remove the flagged content and save again. Screening is a safeguard and does not replace care. Creators must not enter sensitive information in an entry.

If another Creator or the agent changes an entry after it is opened, a save displays a message that the entry changed. Reopen the entry to load the latest version, then apply the edit again. Deleting an entry follows the same rule.

Permissions

Context Documents follow workspace permissions.

Permission What Creators Can Do
View Read entries and their history.
Update Edit and delete entries.
Admin Clear all entries.

Context Usage

Context Documents use part of the agent's working space. The Agent context row in the context gauge displays how much. The agent loads the workspace overview and the entry list at the beginning of each task. The row can display a share before the first reply. A larger overview and more entries raise the share and leave less room for the conversation.

Entries that Creators or the agent add or edit change the share for the next task. Deleting entries lowers it. For the other rows and what happens when the working space fills, see Context Usage Gauge.

When the Context Documents grow too large, the agent consolidates entries as it works. Creators can also edit or delete entries.

Clearing Context Documents

Creators with Admin permission on the workspace can delete all entries except the workspace overview.

To clear the Context Documents:

  1. In the Context tab, select EllipsisVertical (ellipsis) to open Context actions.
  2. Select Clear all topics.
  3. Review the confirmation message, which states how many entries the action deletes, then select Confirm. Select Cancel to keep the entries.

Clearing cannot be undone.

Administrator Settings

Designer Administrators control where the Build Agent keeps Context Documents. One switch turns the feature on or off for the environment, and each workspace has its own switch. For the settings page and how the switches combine, see Context Documents Administration.

When Context Documents are off for a workspace, an open entry displays a message. The message states that the feature is turned off and that an administrator can turn it back on in Settings.


Changelog

Date Change
2026-11-03 Replaced "like" with "such as" in the Reference entry type.
2026-10-26 Replaced the Administrator Settings tables with a short summary that links to Context Documents Administration. Named the History action.
2026-10-26 Linked Context Documents Administration from Administrator Settings and See Also.
2026-10-26 Moved the Context tab image to the top of its section, aligned right.
2026-10-26 Replaced the Context Usage Gauge section with Context Usage, which explains how Context Documents count toward the total. Moved the gauge description to the Build Agent article.
2026-10-23 Added links to related articles.
2026-10-23 Created the article from source, split from Build Agent Context. Covers the Context tab, entry types, editing, version history, screening, permissions, context usage, clearing, and the administrator settings page.