Visually (at least in this case) it's easier to parse the available variant values as well. I feel like I am just explaining declarative code, but helpful to unpack since you're trying to get at why you like it.

I'm the same.The look feels more static/stationary and a switch can feel more dynamic so it brings this sense of calm to me haha. More so it's helping articulate intent. These are things to *get* by a specific key vs these are things to *do* when condition is met.

For inso this author pumps out a new robust TUI like very week. ratatui.rs

Do it.

Advanced mode www.anthropic.com/engineering/...

turso.tech/multi-tenancy

www.flightcontrol.dev/blog/ultimat...

And they can overlap too like an iterating session can have just Chrome Devtools MCP and Context 7 for docs etc.

Yeah like if I am going to debug/investigate some issues I'll want the Sentry MCP and maybe the Chrome Devtools MCP etc. I can run `claude --mcp-config .mcp_debug.json` which loads those up. Otherwise I rarely need those MCPs for most tasks like planning/executing.

I use discrete mcp configs to help cut down on initial context consumption. Like one for debugging vs implementing etc.

That’s be cool. You kind of get this with stage manager, would be way more helpful as PiP.

Then w/ bugs it's frustrating, but claude has been great at extracting core things in to a new blank project and building reproduction up from there.

I find owning some things has helped. Like scaffolding the project manually to create "pillows" for claude to build around. Initializing the project from a known starter template. Authoring a typical/barebones route w/ action handling. A few UI components etc.

Maybe cronitor.io

So they're not all natural chip?

For sure. I was just being silly.

So “use client server”?