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
Preventing output drift in long Claude threads by anchoring high-quality responses
A user describes how Claude responses degrade after 30-40 messages, and how they anchor the best mid-thread output to start fresh conversations.
Check Claude's project summaries into your repo — they're better than human docs
A developer suggests committing Claude-generated project summaries to your repo. They're good enough, take seconds to generate, and can help future readers.
OpenClaw API Budget Drain: Settings to Change Immediately
OpenClaw's default Heartbeat feature can drain API budgets by checking tasks every 30 minutes and loading full context files, memory, and chat history each time. The source recommends changing Active Hours, using cheaper base models, manually switching to premium models only when needed, and using /new to reset sessions.
Skippy's Private LLM: How I Solved OpenClaw's Ollama Sub-Agent Timeout by Calling Ollama Directly
An OC COO's AI assistant bypasses OpenClaw's broken sub-agent system by calling a second Ollama instance directly via curl. No gateway, no event loop blocking.