If your coding session dies because logs, tool output, or retrieved docs eat the context window, chopratejas/headroom is the one to open first. Feed it a repetitive run where the model currently chokes, then compare the compressed prompt against the original on the exact facts you need: IDs, error lines, config values, file paths. Then ask the same question with each version and compare the answers.

For a different failure, pick DietrichGebert/ponytail when the assistant keeps wrapping a small change in fresh abstractions. Give it one bounded edit, such as adding validation to an existing form, and watch whether it reuses nearby code instead of inventing a framework. Pair that with DeusData/codebase-memory-mcp when the real question is impact: before renaming a function, ask who calls it and which tests or modules might notice. One guards the patch, the other maps who depends on it.