Skip to main content

Contexts

A context in architxt is a short descriptive label you attach to a document. It is injected directly into the LLM prompt, so it actively shapes how facts are extracted. The same sentence can mean something very different depending on context: “the project was terminated” in a performance review context versus a product roadmap context produces different memories.

Providing context consistently is one of the highest-leverage things you can do to improve memory quality.

A context is simply a description string, such as Customer Domain, Technical Architecture, or Q3 Planning. Documents can have one context each (or none). Contexts are managed on the Contexts page and applied from the Documents page.

Creating and managing contexts​

Open the Contexts page from the main navigation. The page lists every context with its Context ID, Description, Documents count, Generated By source, and creation time.

You can:

  • Click Add to create a context. Only a description is required.
  • Click Import to paste a CSV of context descriptions. The optional header is context_description; one context per row.
  • Select one or more contexts and click Delete. Deleting a context removes it from any documents that use it; the documents themselves stay in architxt.
  • Search by description or generated-by source.

Click a context row to open Context Details. From there you can edit the description. If the context is assigned to any documents that have already been pushed to Hindsight, the dialog warns you that renaming it may cause a mismatch on the next sync.

Applying contexts to documents​

Contexts are assigned from the Documents page:

  1. Select one or more documents.
  2. Click the Context button.
  3. The Manage Context dialog shows:
    • On All Documents — the context currently shared by every selected document.
    • On Some Documents — contexts that apply to only a subset.
    • Marked for Removal — contexts that will be removed when you save.
    • Available to Add — contexts not currently on any selected document.

A document can only have one active context at a time. Choosing a new context replaces the previous one for all selected documents. Set the selection to empty to clear the context entirely.

You can also set a context at upload time. In the Upload dialog, choose a context from the shared batch settings and every uploaded document will receive it automatically.

Where contexts are used​

The context description is included when architxt pushes a document to a Hindsight memory bank as the Hindsight context field. Hindsight uses that field to group and scope extracted memories.

For details on how the context field is consumed during retention, see the Hindsight API documentation on retain context parameters.

How contexts fit into architxt​

   Contexts
      │
      ▼
  Documents ──────► Hindsight Memory Bank
      │
      ▼
Contextual Graph / Mental Models / Reflect

Contexts sit above individual documents. They are not part of the document text, but they travel with the document into Hindsight, influence how memories are grouped, and help keep related documents aligned in the contextual graph, mental models, and Reflect workflows.

Summary​

Contexts are lightweight labels for documents. Create them once, apply them to many documents, and they become part of the metadata Hindsight uses when retaining and organizing memories.