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

# SuperContext

A fresh chat shouldn't start cold. **SuperContext** makes the agent gather relevant background *before* it reads your first message — automatically, on every new thread, without you asking and without waiting on a tool call.

Most agents start a conversation blank and only fetch context if the model decides to call a "look things up" tool. That adds a round-trip, costs tokens, and depends on the model choosing well. SuperContext flips it: the harness itself prepares context up front, deterministically, so the very first reply already knows the relevant memories, files, and connected data.

***

## How it works

On the **first turn of a new thread**, if SuperContext is enabled, the harness:

1. Spawns a read-only `context_scout` sub-agent.
2. The scout sweeps your available data — the [Memory Tree](/openhuman/features/obsidian-wiki/memory-tree.md), workspace files, and connected integrations — and assembles a bounded **context bundle**.
3. The bundle is validated, then prepended to your message under a `Prepared context (super context)` header before the orchestrator model ever sees the turn.
4. The model answers your message already grounded in that context.

```
New thread, first message
        │
        ▼
┌──────────────────────────────┐
│  Harness gate (deterministic) │
│  super_context_enabled?       │
└───────────────┬──────────────┘
                │ yes
                ▼
        context_scout (read-only)
        sweeps memory + files + data
                │
                ▼
        [context_bundle] … [/context_bundle]
                │  validated & extracted
                ▼
   Prepended to your message → orchestrator
```

Because the scout is **read-only**, it can never take an action on a fresh thread — it only reads and summarizes. And because it runs in the harness rather than as an optional tool, the redundant `agent_prepare_context` tool is suppressed for that turn, so the agent doesn't do the work twice.

***

## Safety and robustness

The scout returns its findings wrapped in `[context_bundle] … [/context_bundle]` tags. Only the bracketed envelope is ever injected — any surrounding prose the model emits ("sure, here's what I found…") is stripped out. If the bundle is missing, malformed (unterminated, reversed, or duplicated tags), or empty, the turn proceeds **gracefully without augmentation** rather than injecting garbage. A cold start is always preferable to a broken one.

***

## Turning it on or off

SuperContext is **on by default**.

* **From the composer.** A **Super Context** toggle appears below the chat input on a fresh thread. The flag is read when a thread is constructed, so toggling it affects **newly started threads**, not the one you're already in.
* **Config.** `context.super_context_enabled` (boolean, default `true`).
* **Environment.** `OPENHUMAN_SUPER_CONTEXT` (or `OPENHUMAN_CONTEXT_SUPER_CONTEXT_ENABLED`).
* **RPC.** `get_super_context_enabled()` reads the flag; `set_super_context_enabled(value)` sets and persists it.

***

## See also

* [Memory Tree](/openhuman/features/obsidian-wiki/memory-tree.md) — the primary source the scout reads from.
* [Auto-fetch from Integrations](/openhuman/features/obsidian-wiki/auto-fetch.md) — keeps that source fresh between conversations.
* [Subconscious Loop](/openhuman/features/subconscious.md) — the other side of "keeps thinking when you've stopped typing."


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://tinyhumans.gitbook.io/openhuman/features/super-context.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.