It’s Time To Increase Claude Code Visibility
Source: Alex Dunlop in Vibe Coding, cited in Medium Daily Digest of 2026-04-17.
Key takeaways
- Dunlop’s framing: “The tool that feels like it should be native” — Claude Code deserves more visibility in your daily workflow.
- Argument: developers under-use Claude Code because they treat it as a separate tool rather than baseline infrastructure.
- Concrete suggestions to integrate Claude Code more deeply into daily workflow.
- Complements Dunlop’s output-tokens-by-75% piece from the same digest.
The argument
A lot of Claude Code users use it like an optional side tool — open when you need it, close when you’re done. Dunlop argues it should be ambient infrastructure — always running, always available.
The language about “feels like it should be native” captures the UX disconnect: Claude Code is capable enough to be a primary interface, but most users don’t configure it that way.
Practical signals this article helps address
- You have Claude Code installed but don’t open it by default
- Your CLAUDE.md files are minimal because you don’t use it enough to justify investment
- You forget slash commands exist because you don’t use them daily
- Your team has uneven Claude Code adoption (see Rezvani’s monitoring piece — 2/7 engineers generate 80% of sessions)
If any of those describe you, Dunlop’s argument applies.
The recursive point
Njenga, Rezvani, and Dunlop are all writing about the same underlying phenomenon: tool under-use. The community-level realisation across April 2026 is that Claude Code is consistently under-used relative to its capability, and the fixes are mostly about changing habits rather than learning more features.
Related Playbook pages
- Cut Claude Code’s Output Tokens by 75% — Dunlop’s other April 2026 piece
- The New Claude Code Monitoring — Rezvani’s data on adoption gaps
- Onboarding — the path from “installed but under-used” to “productive”