|
|
|
|
|
by bicx
279 days ago
|
|
I adopted a couple practices (using dev containers and worktrees) just to make life a little easier. I also built my own shell script “framework” to help manage the worktrees and create project files. However, that took me just a couple days to do on my own (also using CC), and it didn’t lock me into a specific tool. I do agree that context poisoning is a real thing to watch out for. Coincidentally, I’d noticed MCP endpoint definitions had started taking a substantial block of context for me (~20k tokens), and that’s now something I consider when adopting any MCP. |
|
The new /context cc command is great for visualizing what uses how much of the context.
On the other hand, I'm curious about dagger's container-use MCP. https://container-use.com/agent-integrations