Tip-only Claude how-tos for professional developers.
At a glance Claude Corner tip Confirm every Claude Code CLI that reads the file is on v2.1.281 or later before you set `”attribution”: false`. On a mixed-version team, hide the stamps with empty `commit` and `pr` strings plus `”sessionUrl”: false`. Move off `includeCoAuthoredBy`, which has been deprecated since `attribution` replaced it in v2.0.62. Claude … Read more
At a glance Claude Corner tip Turn the risky task into a short in-scope / out-of-scope checklist in Claude Desktop before any edit. In Claude Code, open `/permissions` and set explicit allow, ask, and deny rules while still in plan mode. Confirm deny wins, then leave plan mode only for the files and commands on … Read more
At a glance Claude Corner tip Opus 5.5 defaults to medium effort (Opus 5 defaulted to high), so a silent upgrade can feel softer than expected. Adaptive thinking stays on at every effort level on Opus 5.5; effort is the lever for depth, latency, and usage burn. After you change the model in Claude Desktop … Read more
At a glance Claude Corner tip Stop losing shared `AGENTS.md` playbooks when a repo also has `CLAUDE.md` or `CLAUDE.local.md`. Set Project instructions to `claude-md-and-agents-md` in `/config` (or the matching `pluginConfigs` setting) so both files load. Pin Claude Code to `v2.1.277` or newer before relying on native `AGENTS.md` support. You keep one `AGENTS.md` for Codex and … Read more
At a glance Claude Corner tip Keep focused subagents from reloading the full user, project, and local CLAUDE.md stack into every worker turn. Set `omitClaudeMd: true` on agent frontmatter or `–agents` JSON so those workers skip instruction files while managed policy still loads. Pin Claude Code to `v2.1.271` or newer (prefer your current fleet pin … Read more
At a glance Claude Corner tip Brief one coordinator with a single goal, then let it fan work into parallel Claude Code cloud threads. Put durable decisions in shared project memory so later threads inherit them instead of relearning them from you. If you do not have the redesigned Projects UI yet, wait or stay … Read more
Keep the skills and plugins you enable on claude.ai available in Claude Code terminal sessions signed in with the same account. Opt out deliberately with syncClaudeAiSkills / syncClaudeAiPlugins when a laptop must stay isolated from account packs. Pin Claude Code to v2.1.276 first so skill sync and corporate gateways do not collide with the advisor_20260301 … Read more
Start Claude Code in plan mode (–permission-mode plan or Shift+Tab) so it explores and proposes without editing until you approve. Pin plan as the project default with permissions.defaultMode, then approve into Manual, accept-edits, or auto when the plan is ready. Use Desktop's Code-tab mode selector the same way when you are not in the terminal, … Read more
Cap team burn with maxEffortLevel (Claude Code v2.1.267+) so routine sessions cannot climb into xhigh / max by accident. Steer per session with /effort, –effort, or CLAUDE_CODE_EFFORT_LEVEL, and save defaults with effortLevel / modelSettings. Watch the shared seat window with /usage, pick a cheaper model for routine work, plan first, and keep tool dumps short. … Read more
Drop legacy budget_tokens. On Claude Opus 5, adaptive thinking is the default and manual thinking.type: "enabled" returns 400. Steer depth with output_config.effort (low / medium / high / xhigh / max). Keep that field off the thinking object. Bound cost with a large enough max_tokens (hard cap on thinking plus text) and read usage.output_tokens_details.thinking_tokens. Your … Read more
