Skip to content
~/agentops
← all factors
IPREPARE

Context Is Everything

Put only task-relevant context in the window.

Rule

Treat context as production input. Load the smallest packet that lets the agent do the job.

What AgentOps Enforces

  • Start with the task, repo instructions, relevant files, constraints, and validation path.
  • Keep unrelated transcripts, broad docs, stale assumptions, and speculative plans out of the window.
  • Prefer a compact briefing over a raw dump.
  • Refresh context when the task changes instead of dragging the old session forward.

Failure Signal

  • The agent repeats itself or ignores recent instructions.
  • The agent asks for information it already saw.
  • The answer sounds plausible but cannot point to files, commands, or evidence.
  • The session keeps growing because nobody knows what can be removed.

Done Looks Like

The agent can state the task, the boundary, the relevant files, the proof command, and the next action without carrying unrelated history.