Blog

After an MSIX update, Claude Desktop on Windows reads claude_desktop_config.json from a virtualized path while Edit Config opens the old %APPDATA% one. Edit the file under AppData\Local\Packages\Claude_pzs8sxrjxfjjc and restart.

AnimationController, TextEditingController, and ScrollController hold resources that Dart's GC cannot reclaim until you dispose them. Here is the correct pattern, the ordering rules, and how to catch leaks before they ship.

A request can fail with no connectivity, a timeout, a DNS failure, a 500, or malformed JSON, and each needs a different response. Here is how to catch the right exceptions, classify them, retry safely, and show a UI a user can act on.

When you Include two sibling collections, EF Core 11 returns the cross product and your row count explodes. Here is how AsSplitQuery fixes it, how to turn it on globally, and the consistency and ordering gotchas to watch for.

Anthropic shipped Opus 4.8 on May 28, 2026 with Dynamic Workflows, a research preview in Claude Code that writes a JavaScript orchestration script to run tens to hundreds of subagents in parallel, capped at 1,000 per run.

GitHub MCP tools show up but every call returns empty or 'Bad credentials'? The token is unset. Put the PAT in the env block, verify with curl, done.

Calling Task.Run from a controller loses work on shutdown, swallows exceptions, and captures disposed scoped services. The safe pattern is a bounded Channel queue drained by a BackgroundService that opens a fresh scope per work item and drains in-flight work on StopAsync.

A complete guide to ExecuteUpdate and ExecuteDelete in EF Core 11: the SQL they emit, the change-tracker gotcha that silently overwrites your bulk write, transactions, concurrency control with the affected-row count, and the EF Core 10 delegate setters that let you build conditional updates with plain if statements.

A BackgroundService is a singleton, so it cannot inject a scoped service like a DbContext directly. Take IServiceScopeFactory, open one scope per unit of work with CreateAsyncScope, resolve inside it, and dispose it when the work is done.

This banner is a pause, not a failure. It maps to the API's pause_turn stop reason (default 10 server-tool iterations). Click Continue, or in code re-send the assistant response. Full fix here.