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

# Current state and past context

> Understand what Termyte gives a supported agent at the start of work.

# Current state comes first

For Claude Code and Codex, Termyte can return context through installed hooks. When a repository has exactly one active Work Thread, the context begins with its current state. Older summaries, observations, and memories follow as supporting material.

This order matters: the current objective and next step should not be overridden by something remembered from an older session.

Historical context is:

* limited to the repository and available file signals;
* packed into a token budget;
* linked to the records it came from;
* allowed to return nothing when the available material is weak or irrelevant.

## Checking old context

Before using stored context that names files, Termyte compares those paths with the current workspace and Git state.

| Result         | Meaning                                                       |
| -------------- | ------------------------------------------------------------- |
| `current`      | The files exist and Git does not report them as changed.      |
| `changed`      | At least one referenced file has changed.                     |
| `stale`        | A referenced file is missing or points outside the workspace. |
| `unverifiable` | The workspace or Git state could not be checked.              |

This check can catch changed or missing files. It cannot prove that every sentence in an old memory is still correct.

OpenCode capture does not currently return automatic context to the agent. Use `termyte task resume` or the MCP tools when moving work into OpenCode.

Use the Viewer to inspect context packets, selected items, and recorded feedback.