Harness engineering: come rendere affidabili i workflow con l’AI (senza inseguire l’ennesima buzzword)
Da prompt a contesto fino alla “harness”: un modo pratico per progettare agenti, skill e pipeline...
Tag archive
Da prompt a contesto fino alla “harness”: un modo pratico per progettare agenti, skill e pipeline...
💡 AI Labo Benchmark Series — Experiment E19 (Ranked #4 out of 41 Patterns) This post is part of our...
💡 AI Labo Benchmark Series — Experiment E12 (Ranked #6 out of 41 Patterns) This post is part of our...
💡 AI Labo Benchmark Series — Experiment E21 (Ranked #2 out of 41 Patterns) This post is part of our...

Summary In this article, a "translated term" is a technical term rendered into native...

Prompt engineering gets the words right. Context engineering gets the information right. Here is how to manage what your AI agents see.
You hand an agent a short requirement, it makes ten or twelve tool calls, and the final diff quietly solves the adjacent problem instead of the one you asked for. The window fills with fetched files, command output, and trial edits; recent tokens weigh more than the original brief; and nothing forces the agent to re-check acceptance mid-task. This article names the drift patterns (optimize-the-last-output, summary-takes-over, scope-creep-by-convenience, stale-tool-log, lost-initial-criteria), then gives the cheap anchors: a pinned acceptance block, a periodic restate-and-compare check, pruning stale tool logs, and a written handoff between sessions.
An agent fixes an edge case from a messy real input, then verifies the fix against a tidy synthetic record it wrote itself. The synthetic input parses cleanly, the check goes green, and the bug is declared closed, while the original malformed payload that triggered the incident never gets replayed. This article covers why self-authored inputs grade themselves, the telltale signs in the thread, and the cheap gate of keeping the real failing payload as the permanent regression case instead of inventing a friendlier substitute.
Learn how the State vs. Event Law eliminates agent memory drift and stale code hallucinations across Claude Code and local agent fleets using deterministic
The hottest concept in 2026, evolving from Prompt Engineering to Context Engineering. A deep dive into managing the context window through Write, Select, Compress, and Isolate strategies to solve long-context amnesia, hallucinations, and context poisoning.
When a developer redirects an agent away from an explored approach, the rejected branch often stays in the context window and keeps getting implemented. This piece explains why an agent remembers proposals without remembering their status, what extra abstractions and unrequested tests ship as a result, and how to keep an explicit active-constraint list separate from dropped exploration so a rejected idea stops steering the code.
In a long agent session, the first plausible guess becomes the working model, and later corrections attached at the bottom read as exceptions instead of a rewrite. The session then defends the invented convention, edits against the wrong frame, and misses contradicting evidence. This article explains why long chat history anchors on early assumptions, what breaks when a correction arrives late, and how a compact verified-facts brief, periodic session reset, and re-derivation from source files keep the agent from hardening around a guess.