---
title: "#contextengineering articles | Hashnode"
description: "Explore 6 articles tagged #contextengineering on Hashnode. Tutorials, guides, and how-tos from the community."
url: "https://hashnode.com/tag/contextengineering"
---

Tag

# #contextengineering

6 posts · 0 followers

[Powerduck](https://hashnode.com/@powerduck) · [Oct 25](https://hashnode.com/posts/agent-handoff-summary-kept-decision-dropped-why/6ade41bb7124c4bfd7ecc270)

### [The next agent session re-asked a question we already answered, because the handoff kept the decision but dropped why](https://blogs.powerduck.com/agent-handoff-summary-kept-decision-dropped-why?utm_source=hashnode&utm_medium=feed)

We handed a fresh session a summary: use the local queue, no broker. It shipped the broker anyway. The summary had the verdict but none of the rejected alternatives, so it read 'no broker' as a preference, not a settled constraint. A handoff needs the decision, what was ruled out, and why.

4 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-handoff-summary-kept-decision-dropped-why?utm_source=hashnode&utm_medium=feed)

[1](https://hashnode.com/posts/agent-handoff-summary-kept-decision-dropped-why/6ade41bb7124c4bfd7ecc270)

[Powerduck](https://hashnode.com/@powerduck) · [Oct 25](https://hashnode.com/posts/agent-edited-lookalike-function-left-real-caller/6ade6ad886955cf36934bd91)

### [The agent patched the lookalike function from a keyword search, so the failing symbol stayed broken](https://blogs.powerduck.com/agent-edited-lookalike-function-left-real-caller?utm_source=hashnode&utm_medium=feed)

Keyword search returned the normalize family, the agent picked the first match, refactored normalizeEmail, wrote its own green tests, and left the failing normalizePhone path untouched. Pin the traceback symbol, run the original repro before and after, and check callers against the failing request.

4 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-edited-lookalike-function-left-real-caller?utm_source=hashnode&utm_medium=feed)

[Powerduck](https://hashnode.com/@powerduck) · [Oct 25](https://hashnode.com/posts/long-agent-session-anchored-wrong-assumption/6ade4a14de77788c63f76dec)

### [After three hours the agent defended the wrong model it invented, because the session remembered the assumption better than the facts](https://blogs.powerduck.com/long-agent-session-anchored-wrong-assumption?utm_source=hashnode&utm_medium=feed)

Long chat history anchors on the first plausible model the agent invents, and late corrections read as exceptions instead of a rewrite. The session keeps defending the early guess. Keep a verified-facts brief at the top and re-derive from source files rather than trusting session memory.

4 min read · [blogs.powerduck.com](https://blogs.powerduck.com/long-agent-session-anchored-wrong-assumption?utm_source=hashnode&utm_medium=feed)

[Powerduck](https://hashnode.com/@powerduck) · [Oct 25](https://hashnode.com/posts/agent-keeps-honoring-rejected-approach-in-context/6ade2eaab5d5026e40f48aac)

### [The agent kept implementing the approach we already rejected because it never left the context window](https://blogs.powerduck.com/agent-keeps-honoring-rejected-approach-in-context?utm_source=hashnode&utm_medium=feed)

We told the agent to drop the in-memory cache and read from source each time. The draft still shipped an eviction helper, a routing layer, and a cache-miss test nobody requested. A redirect removes the idea from the plan but not the window, so explored options keep acting as active requirements.

4 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-keeps-honoring-rejected-approach-in-context?utm_source=hashnode&utm_medium=feed)

[1](https://hashnode.com/posts/agent-keeps-honoring-rejected-approach-in-context/6ade2eaab5d5026e40f48aac)

[Powerduck](https://hashnode.com/@powerduck) · [Oct 23](https://hashnode.com/posts/agent-drifts-from-requirement-as-context-fills/6adbdf5ecfeadc0b2b086b0f)

### [The agent drifts from your requirement while the context fills up](https://blogs.powerduck.com/agent-drifts-from-requirement-as-context-fills?utm_source=hashnode&utm_medium=feed)

You asked for one behavior; twelve tool calls later it optimized the last output instead of the acceptance criteria. Context fills with intermediate logs, recent tokens dominate, and the original brief gets buried. Here is how drift happens and the cheap anchors that keep a task on rail.

4 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-drifts-from-requirement-as-context-fills?utm_source=hashnode&utm_medium=feed)

[Powerduck](https://hashnode.com/@powerduck) · [Oct 22](https://hashnode.com/posts/agent-tested-the-case-it-invented/6ada71a9129dd07f7458e5f7)

### [The agent wrote its own test input, watched it pass, and called the edge case closed](https://blogs.powerduck.com/agent-tested-the-case-it-invented?utm_source=hashnode&utm_medium=feed)

The bug came from a malformed record nobody typed by hand. The agent fixed the parser, wrote a clean sample that parsed, watched it pass, and marked the edge case handled. It never replayed the record that started the thread. A check you authored yourself grades itself.

5 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-tested-the-case-it-invented?utm_source=hashnode&utm_medium=feed)

[Powerduck](https://hashnode.com/@powerduck) · [Oct 22](https://hashnode.com/posts/agent-argues-against-a-stale-file-snapshot/6ada63d85a4874b5b6b2db5b)

### [The agent argued against a file it had not re-read in twenty turns](https://blogs.powerduck.com/agent-argues-against-a-stale-file-snapshot?utm_source=hashnode&utm_medium=feed)

The agent reads a file once and keeps that buffer across a long session. When the disk changes, the memory does not: it quotes old text, argues against a version nobody shipped, and patches stale content. The gate: invalidate the cache and re-read before editing.

5 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-argues-against-a-stale-file-snapshot?utm_source=hashnode&utm_medium=feed)

[1](https://hashnode.com/posts/agent-argues-against-a-stale-file-snapshot/6ada63d85a4874b5b6b2db5b)

[Powerduck](https://hashnode.com/@powerduck) · [Oct 21](https://hashnode.com/posts/tool-switch-loses-the-closed-decision/6ad9202bd2daa56e9db58a57)

### [Every Tool Switch Makes the Agent Re-Litigate a Decision You Already Closed](https://blogs.powerduck.com/tool-switch-loses-the-closed-decision?utm_source=hashnode&utm_medium=feed)

An hour earlier we had chosen the retry queue over a direct write. Switching editors to run the migration, the fresh session saw no recorded decision and calmly proposed the direct write again. Forty minutes later, the closed decision had been reopened and compromised.

5 min read · [blogs.powerduck.com](https://blogs.powerduck.com/tool-switch-loses-the-closed-decision?utm_source=hashnode&utm_medium=feed)

[Powerduck](https://hashnode.com/@powerduck) · [Oct 20](https://hashnode.com/posts/agent-needs-hard-stop-not-more-context/6ad7147d341851b46e898b38)

### [Your Agent Doesn't Need More Context — It Needs a Hard Stop](https://blogs.powerduck.com/agent-needs-hard-stop-not-more-context?utm_source=hashnode&utm_medium=feed)

Adding another paragraph to AGENTS.md rarely fixes the output. What actually fixes it is a one-sentence exit criterion and a command the agent must re-run before declaring done.

4 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-needs-hard-stop-not-more-context?utm_source=hashnode&utm_medium=feed)

[Powerduck](https://hashnode.com/@powerduck) · [Oct 15](https://hashnode.com/posts/agent-config-flag-avoiding-decision/6ad12f70ea4cb0c94a936ebe)

### [When your agent adds a config flag, it's avoiding a product decision](https://blogs.powerduck.com/agent-config-flag-avoiding-decision?utm_source=hashnode&utm_medium=feed)

Agents default to 'make it configurable' because training data rewards flexibility. Every flag they add is a branch nobody tests and a decision nobody made. The cheap counter-move is to force a default first.

4 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-config-flag-avoiding-decision?utm_source=hashnode&utm_medium=feed)
