I changed a password in my .env file, restarted MySQL with Docker Compose, and MySQL rejected the new password with ERROR 1045 (28000): Access denied. The container had the new value, but MySQL was still expecting the old one. This post shows why that happens with the official MySQL image, and how I fixed it without deleting any data.
I typed SELECT 'café' into the mysql client inside the official MySQL Docker container, and the client showed 'caf'. The é never appeared on screen and never reached MySQL, and there was no error at all. The container runs without a locale, so the client only accepts plain ASCII. One extra flag on docker compose exec fixes it.
An agent that you serve with Microsoft Agent Framework's MapAGUIServer answers every request as if it had never met you — until the server has somewhere to keep conversations. That place is a session store. This guide adds one for development, shows the same follow-up question before and after, and explains where the history really ends up.
An AG-UI request carries three IDs: threadId, runId and parentRunId. When the server remembers conversations, a follow-up keeps the first, changes the second, points the third at the turn before — and carries only the new message. This guide shows each request and what the server sends back, from a real agent.
When an app continues a conversation through Microsoft Foundry's Responses API, it often sends only the newest message, and Foundry rebuilds the rest from its stored responses. This guide shows you exactly what Foundry rebuilt: the full input behind any answer, from one Azure CLI command, with no API key.
Some code belongs only on a developer's machine: an in-memory store, a relaxed setting, a debugging aid. ASP.NET Core knows which environment it runs in, and one if around builder.Environment.IsDevelopment() keeps that code out of everywhere else. This guide shows the check, where to put it, and how to try the other branch on your own machine.
I continued a conversation the way many chat clients do — by sending the whole conversation again — and the Microsoft Agent Framework agent read its first question and its own first answer twice. The answer still looked fine, which is what makes this easy to miss. Foundry's stored input showed the duplicates, and sending only the new message fixed it.
I gave a Microsoft Agent Framework agent a session store so it would remember conversations, and every request started failing with a 500: Agent isolation key is required but was not provided by the configured AgentIsolationKeyProvider. I had configured no provider at all. The default store wanted to know who was calling, and my API had no way to tell it.
My Azure CLI query asked for three fields — type, role and text — and --output table printed only two columns. The type column had vanished without a warning. The Azure CLI hides that key in tables on purpose, and renaming it in the query brings it back.
Microsoft's page on ASP.NET Core environments says dotnet run -e Staging sets the environment. I ran it, and my API started in Development anyway, with no error and no warning. -e sets an environment variable, so it needs a name and a value: -e ASPNETCORE_ENVIRONMENT=Staging does what the short form promises.
