Contextual knowledge
Also called In-context knowledge
Facts the model has because they are in the context window right now, as opposed to facts it remembers from training.
Contextual knowledge is what the model knows from the current request: the files the agent has read, the docs you pasted, the error output, the instructions in your project file. It is the counterpart to parametric knowledge. Anything in the context window can override what the model would otherwise assume, which is the whole reason coding agents read files before editing them instead of writing from memory.
It is also the more reliable of the two, as long as it is actually there and still accurate. Models generally trust the context over their training when the two conflict, so a pasted changelog beats a stale habit. The failures come when people assume something is in context and it is not (the agent never opened that file), or when it was in context but has since changed on disk (you edited it after the read).
Make contextual knowledge deliberate. Point the agent at the specific files that define the truth for this task, refresh them after big changes, and prefer primary sources over your own summary of them. When an answer seems to ignore your codebase, ask what it read; the honest reply is often 'nothing yet'.
- Claude Code
@path/to/fileloads a file into context explicitly; a Read tool call does the same thing on the agent's own initiative. - CursorFiles open in the editor and anything attached via
@are the request's contextual knowledge.
“Why did it get the config right this time and wrong yesterday?”
“Yesterday it worked from memory. Today you pasted the actual config, so it had contextual knowledge instead of a guess.”
Course 01 puts every one of these terms to work: you install Claude Code, run the loop, and ship a real project — permission modes, compaction, hooks and all.
Start Course 01 →