Context Pointer
Penunjuk Konteks
A mention in one document that points to another, so the agent can pull it in only when the task calls for it.
A context pointer is a mention inside one document that points to another: see the API guide, check the schema file, the details are in the runbook. Instead of pasting the content in, the document points at it and lets the agent decide whether to load it.
It is the mechanism that makes large bodies of guidance fit in a small context. The agent reads a short index, and the index tells it where the detail lives. When the task touches that area, the agent follows the pointer and loads the real thing; when it does not, the detail never enters the context at all.
The requirement is that the pointer has to be resolvable. A pointer to a file that does not exist, or to a document whose title has drifted from what the pointer says, sends the agent chasing a dead end and costs a turn. A good pointer names its target precisely enough that the agent can load it in one step, and it stays accurate as the documents change.
Related terms
Progressive Disclosure
Show the model only the detail it needs right now, and load more when it asks.
Skill
A teachable capability bundled as a unit, kept out of the context window until a pointer pulls it in.
Context Engineering
Deciding what goes into the model's context, and what stays out.
Context Window
Everything the model sees on one request. Finite, and it decides what fits.
AGENTS.md
A file in the environment that the harness loads into the context at session start: the project's standing brief to the agent.
Want this working inside your team?
It starts with one conversation about your workflow.