5 Claude Code Terminal Commands You Might Be Missing
A senior dev who's been using Claude Code in the terminal for 6+ months shares five commands that significantly improved their daily workflow. These aren't flashy features, but practical friction-removers.
1. Customize your statusline with /statusline
Adds a persistent status bar at the bottom of your terminal. You can ask Claude to display model name, git branch, context usage percentage, or anything else you need at a glance.
2. Run shell commands with !
Prefix any command with ! to execute it directly from the chat. The output stays in the conversation, so you can follow up without copy-pasting. Use Ctrl+B while a ! command is running to send long-running commands to the background.
3. Mention files with @
Type @ + filename to trigger path autocomplete. This is much faster than letting Claude search your repo for the right file.
4. Expand working context with /add-dir
Add another directory to the session. Perfect for projects split across multiple repos — you can work with both simultaneously.
5. Start a side conversation with /btw
Ask a quick question without interrupting Claude's current task. For longer side discussions, use /branch to spin off a new session.
These commands may seem simple, but the author found they removed a lot of friction from daily use.
📖 Read the full source: r/ClaudeAI
👀 See Also
Claude Code Agents Don't Automatically Read Project Documentation
When Claude Code dispatches subagents like Sonnet to write code, those agents only see what's explicitly included in their prompt and don't automatically read CLAUDE.md, MEMORY.md, or other project context files unless specifically instructed to do so.
Model Routing Cut API Costs by 85% vs Claude Max Subscription – A Developer's Analysis
A Claude Max subscriber tracked token usage and found only 15% of tasks needed Opus. Switching to API routing (Sonnet for routine tasks, Opus for hard reasoning) dropped monthly cost from $200 to ~$30 with identical output quality.
Three Overlooked Bottlenecks in AI Agent Workflows: Ingestion, Context Management, and Model Routing
A deep dive into the three layers often skipped when optimizing AI agents: clean input ingestion, context window management across steps, and task-appropriate model routing. Practical fixes include using structured parsing, summarized step outputs, typed schemas, and matching models to task complexity.
Collaborative vs Directive AI Prompts Yield Different Outcomes
A Reddit discussion highlights measurable differences in AI-assisted development outcomes between users who collaborate with AI using "we" language versus those who give directive "do this" commands. The collaborative approach surfaces dead-ends and challenges assumptions through shared context.