Token Efficient Execution

Save tokens by tightening the work loop, not only the answer style.

Core Principle

The biggest waste usually comes from repeated exploration, repeated explanation, and oversized context reloads. Fix the loop first.

Execution Rules

• Read targeted files, not whole trees.
• Search exact symbols, error text, route names, or config keys before broad terms.
• Do not reread the same file unless it changed or a new hypothesis makes it relevant.
• Prefer narrow patches over file rewrites.
• Avoid long “plan recap” messages after every small step.
• Keep intermediary updates to one or two sentences unless the user asked for a plan.
• Reuse gathered evidence instead of re-deriving it.
• Stop low-value parallel exploration once a clear winning path appears.