Shadowing Practice: Context Engineering for AI Agents: 4 Failure Modes to Avoid - Learn English Speaking with Video

Kies een oefenmodus

Elke modus opent een volledig scherm oefenruimte.

116 zinnen
Als zinnen te kort of te lang zijn, klik op Bewerken om ze aan te passen.
1
context windows have grown from well a few thousand tokens to well a lot bigger like a million
2
or more and that's room for more stuff more instructions tool results docs you name it
3
so if we think about ai agents
4
and we give them access to this big old context window well
5
they should probably be getting better at long -running tasks shouldn't they?
6
I mean the more context the better job they can do.
7
Well a recent study looked at 18 frontier models
8
and it turned out that they all got less reliable as the context window got bigger.
9
Researchers have taken to giving this thing a name and that is context rot.
10
The more tokens in the window the less reliably the model uses any of them.
11
And this is the problem that context engineering is there to solve.
12
Context engineering is deciding what actually goes into this context window at each step of an agent's run.
13
Now there are many ways an agent's context can go wrong and I'm going to cover four of them.
14
The four failure modes that you can encounter when working with these big context windows.
15
And because I'm feeling nice I'll also suggest how to fix each one.
16
And the funny thing about those fixes is they involve deliberately throwing away information.
17
So how does an agent get better by holding less context?
18
Well to answer that we should first take a look at what's actually filling up these giant context windows.
19
So let's say an AI agent was given the job to migrate an aging code base over to a new database driver.
20
So I'm talking about here we are building a migration AI agent.
21
Now at the beginning of the context window the first thing most likely in here is the system prompt.
22
That's the standing instructions for how the agent operates in general.
23
Now the agent task itself
24
that will also be stored in here as well just as a prompt on its own
25
and it might not be very big it might only be a couple of lines.
26
Then many agent harnesses also pull in a bunch of project instructions.
27
Now these are things like an agents .md file explaining how this particular project is built.
28
Then after that we might have some tool definitions, a description of every tool the agent can call.
29
And from here on in the context window turns into a bit of a running log
30
so we're going to have a message history here this is every step the the agent has taken
31
and after let's say an hour of running well
32
this could get pretty big that's going to be a lot of steps
33
and then the biggest band is probably the tool results
34
that we store here which is things like file contents
35
and test output and error logs and schema dumps
36
so the job description the prompt is a few lines near the front
37
and pretty much everything else is the stuff
38
that the agent kind of piles up along the way oh
39
and buried in this as well there happens to be a note
40
this is a note the agent wrote itself it says
41
that the new driver retries failed connections automatically
42
so the old retry code can be deleted
43
so the note just basically says hey don't bother with writing any retry code why do i mention
44
that we'll come back to
45
that anyway why is a full context window a problem well
46
a model doesn't look things up in its context the way
47
a database looks up a row every token in the window
48
is competing for a finite amount of attention essentially an attention budget.
49
And to me, this is kind of the crux of it.
50
The window might hold a million tokens, but the attention spread across those tokens is finite.
51
Now, what about those failure modes?
52
Let's start with the first one.
53
Number one, that is context poisoning.
54
So I cryptically mentioned the agent wrote itself a note about the new driver retrying failed connections automatically.
55
Well it turns out that that note is completely wrong.
56
The agent shouldn't have done this.
57
It basically skim the driver's documentation, it misread it, and then it's written down a false conclusion.
58
And that's all poisoning is.
59
A mistake gets into this context window somewhere and then gets treated as fact because to the AI model,
60
its own notes, they look like the ground truth.
61
So file after file, our agent has been deleting perfectly good retry code.
62
Next, number two, that is context distraction.
63
This is where the sheer size of the history starts steering the agent.
64
Now a language model at its heart is just a pattern continuation machine
65
and when the context holds at say an hour of an agent's own past actions, that history becomes pretty much the strongest pattern around,
66
stronger than the reasoning it picked up in training.
67
So instead of asking what the job needs next the model
68
might drift into doing more of what it has already done
69
in this message history agents in this state can get stuck just kind of going over old ground
70
what about number three that is context confusion
71
and this one comes from the tools our agent here is wired into quite a lot of stuff
72
there's probably some amount of version control here
73
it might be access to a database console maybe it also is logging tickets into a ticketing system
74
and each of these tool definitions is in the window whether it actually gets used
75
or not and having more of them makes choosing the right tool a bit harder
76
and in one benchmark a model failed a task
77
when it was offered 46 tools but it then passed the very same task
78
when it was only offered 19 tools
79
that is tool sprawl work okay number four that is context clash
80
which is when the window contains information that disagrees with itself
81
so take that note with the bad information at some point our agent is going to see
82
that no retries are happening and it's going to figure out
83
that that note was wrong and it will probably make a note of
84
that into its message history as well
85
but the problem then is we now have both versions sitting in the window
86
that are presenting conflicting information so these are four different ways a context window can go bad
87
all right so what about some potential fixes well for poisoning one of the fixes is to validate.
88
Before a conclusion gets written down into this context window, check it against something real.
89
So one quick connection test and our agent would never have written this no retry code note.
90
What about distraction?
91
Well, the fix there is really too compact.
92
When the history gets really, really long, the agent can summarize it,
93
which is to say it throws the full log away and starts again from the summary,
94
a shortened version of what was in this message history in the window.
95
Now compaction is lossy.
96
A summary of a summary can start to drift like a photocopy of a photocopy.
97
So consider moving as much out of the context window as possible and put them into permanent files instead.
98
Detailed information can be retained in those files, and then it can be pulled into the context window only when it's actually needed.
99
All right, what about context confusion?
100
Well, that is a curation problem, so the fix is to curate.
101
The agent doesn't need 46 tools for database migration, so just give it the handful that the job calls for,
102
and then it can always go and fetch others
103
if it actually needs them then finally context clash well the fix there can be to prune so
104
when information gets superseded just delete the old version rather than leaving both in the window
105
we could have deleted this guy entirely or go further
106
and start a fresh window just restating the current corrected state of the job
107
and leave the poison stuff behind so
108
if a false conclusion gets saved that's poisoning so you can validate
109
if the history has taken over that's distraction so compact
110
if the agent has more tools than the task needs that's confusion
111
so curate and if the context disagrees with itself that's a clash and the fix is prune.
112
And all four fixes work by throwing something away.
113
An agent can get better at long tasks by holding less.
114
Now I'd love to know how you keep an agent's context lean.
115
Do you have your own context engineering fixes?
116
Let me know in the comments.

App downloaden

Alles wat je nodig hebt om vloeiend te spreken

AI UitspraakScoor elke zin
IPA OefeningBeheers elk geluid
WoordenschatBouw je woordenschat op
WoordenspelLeren terwijl je speelt

Zelfde Kanaal

FOR YOU

Aanbevolen Video

Woordenschat en spreektips bij deze les

Deze spreekles is gebaseerd op de video “Context Engineering for AI Agents: 4 Failure Modes to Avoid”. Deze woorden komen het vaakst terug: context, agent, window, tool, note. Deze video bevat 100 zinnen en 1451 woorden om na te spreken. Het gesproken deel duurt 10:08. De spreker praat in een gelijkmatig tempo van ongeveer 143 woorden per minuut, prettig om te shadowen. 86% van de woorden hoort bij de 3.000 meest gebruikte Engelse woorden; de rest kun je beter vooraf bekijken.

Belangrijke woorden in deze video

15 woorden uit de video die het leren waard zijn, met uitspraak en betekenis:

WoordUitspraakBetekenis
poison zelfstandig naamwoord/ˈpɔɪ.zən/gif, vergif
token zelfstandig naamwoord/ˈtoʊkən/teken
database zelfstandig naamwoord/ˈdeɪtəˌbeɪs/database, databank
delete werkwoord/dɪˈliːt/verwijderen
conclusion zelfstandig naamwoord/kənˈkluːʒən/conclusie, einde
summary zelfstandig naamwoord/ˈsʌm.ə.ɹi/samenvatting, overzicht
confusion zelfstandig naamwoord/kənˈfjuːʒən/verwarring, war
instruction zelfstandig naamwoord/ɪnˈstɹʌkʃən/onderwijs
prompt werkwoord/pɹɑmpt/aansporen, aanmoedigen
distraction zelfstandig naamwoord/dɪsˈtɹæk.ʃən/afleiding
log zelfstandig naamwoord/lɔɡ/boomstam, boomstronk
migration zelfstandig naamwoord/maɪˈɡɹeɪʃ(ə)n/migratie
disagree werkwoord/dɪsəˈɡɹi/niet overeenkomen, niet overeenstemmen
compact bijvoeglijk naamwoord/kəmˈpækt/compact
finite bijvoeglijk naamwoord/ˈfaɪ.naɪt/eindig

Phrasal verbs die je zult horen

WoordUitspraakBetekenis
turn out werkwoorduitvallen, resulteren
figure out werkwoorduitvogelen, er achter komen
fill up werkwoordopvullen, vollopen
look up werkwoord/ˌlʊk ˈʌp/opkijken
pile up werkwoordstapelen
take over werkwoordovernemen
throw away werkwoordweggooien
write down werkwoordopschrijven, neerschrijven

Grammatica in deze video

De structuren die de spreker het meest gebruikt, met de exacte woorden uit de video:

StructuurIn de video
Lijdende vorm be + voltooid deelwoord — het gaat om wat er gebeurt, niet om wie het doetwas given · be stored · is built
Present perfect have/has + voltooid deelwoord — iets uit het verleden dat nu nog telthave grown · have taken · has taken

Uitspraak om op te letten

De spreker gebruikt 12 samentrekkingen en verkorte vormen, zoals doesn't, gonna, I'm. Spreek ze kort uit, zoals je ze hoort.

  • De klanken “sh” en “zh”: conclusion /kənˈkluːʒən/, confusion /kənˈfjuːʒən/, instruction /ɪnˈstɹʌkʃən/, clash /ˈklæʃ/, distraction /dɪsˈtɹæk.ʃən/
  • Lange woorden — let op de klemtoon: essentially /ɪˈsɛnʃəli/, deliberately /dɪˈlɪb.(ə.)ɹət.li/, documentation /ˌdɑkjəmɛnˈteɪʃən/, continuation /kənˌtɪnjʊˈeɪʃ(ə)n/, photocopy /ˈfəʊtəˌkɒpi/

Klanken die Nederlandstaligen lastig vinden:

  • Stemhebbende eindmedeklinker — /b/, /d/, /g/, /z/, /v/ niet verscherpen: log /lɔɡ/, solve /sɒlv/, involve /ɪnˈvɑlv/, bind /ˈbaɪ̯nd/, misread /mɪsˈɹiːd/
  • /æ/ — opener dan de Nederlandse “e”: clash /ˈklæʃ/, distraction /dɪsˈtɹæk.ʃən/, compact /kəmˈpækt/, handful /ˈhæn(d)fʊl/, validate /ˈvæl.ɪ.deɪt/
  • /g/ — een harde plofklank, geen Nederlandse “g”: log /lɔɡ/, migration /maɪˈɡɹeɪʃ(ə)n/, disagree /dɪsəˈɡɹi/, migrate /maɪˈɡɹeɪt/

Zo oefen je met deze video

  1. Luister de hele video één keer zonder te spreken en noteer de woorden die je niet kent.
  2. Spreek zin voor zin na op normale snelheid en herhaal elke zin tot je ritme gelijk is aan dat van de spreker.
  3. Neem jezelf op en vergelijk met het origineel; let daarbij op woorden als poison, token, database.

Wat is de Shadowing-techniek?

Shadowing is een wetenschappelijk onderbouwde taalleermethode die oorspronkelijk is ontwikkeld voor professionele tolkentraining en gepopulariseerd door polyglot Dr. Alexander Arguelles. De methode is eenvoudig maar krachtig: je luistert naar native Engelse audio en herhaalt het onmiddellijk hardop — als een schaduw die de spreker volgt met slechts 1–2 seconden vertraging. In tegenstelling tot passief luisteren of grammaticadrills, dwingt shadowing je hersenen en mondspieren om echte spraakpatronen tegelijkertijd te verwerken en te reproduceren. Onderzoek toont aan dat het de uitspraaknauwkeurigheid, intonatie, ritme, verbonden spraak, luisterbegrip en spreekvaardigheid aanzienlijk verbetert — waardoor het een van de meest effectieve methoden is voor IELTS Speaking-voorbereiding en echte Engelse communicatie.

Shadowing-techniek: lees de volledige stap-voor-stap-gids →