Containers and auto mode work together: containers require punching holes for services like GitHub, the Anthropic API, and MCPs, and auto mode layers on top to reduce risks of accidental data deletion, exfiltration, and prompt injection through those open channels.
Auto mode is part of the core team's own daily workflow, not just a feature for external users.
A visual glitch some users were seeing is confirmed as a bug, not a feature. Resizing the terminal works as a quick fix; the latest release patches one corner case, with another fix landing the following day via claude update.
Auto mode skips permission prompts without the risks of dangerous mode. It's the recommended middle ground for users who want less friction.
A team member is following up on a user-reported visual or behavioral issue, asking for a recording or screenshot to reproduce the problem.
Scrolling further in the token usage view reveals a breakdown by individual plugin, skill, or MCP, which helps diagnose why context fills up faster than expected.
Session timeout defaults differ by plan: subscription users get 1 hour, API users get 5 minutes.
Setting `autoUpdatesChannel` to `stable` in settings.json is the fix for users who want to pin to the stable release channel rather than receiving pre-release updates.
Types serve the human developer more than the agent; TypeScript makes data structures legible in a way that JavaScript-with-classes doesn't. Rails is a different story, where the tradeoff flips.
Asked for a modest 2x improvement, Claude came back with a 57x result instead. The kind of overshoot that is either delightful or alarming depending on what exactly was being optimized.
