Skip to main content

​
Terminal Setup

​
iTerm2 for macOS

Use iTerm2 terminal instead of IDE terminals to avoid crash issues.
iTerm2 provides:
  • Better stability for long-running Claude sessions
  • Native notification support
  • Superior terminal emulation

​
Voice Input

​
Wispr Flow

Use Wispr Flow for voice prompting to achieve 10x productivity improvement.
Claude Code now has built-in Voice Mode. Use /voice to activate it.

​
Voice Feedback Hooks

Install claude-code-voice-hooks for audio feedback during Claude operations.
These hooks provide:
  • Audio notifications for tool use
  • Git commit confirmations
  • Session start/stop sounds
  • Custom team or personal sound preferences

​
Status Line

Configure a status line for context awareness and fast compacting.
The status line shows:
  • Current model and effort level
  • Context usage percentage
  • Session cost
  • Current directory
  • Custom information from your shell config
Use /statusline to have Claude generate a status line based on your .bashrc or .zshrc.

​
Permissions Management

​
Wildcard Syntax

Use /permissions with wildcard syntax instead of dangerously-skip-permissions:
  • Bash(npm run *) — Allow all npm scripts
  • Edit(/docs/**) — Allow editing all files in docs directory
This approach:
  • Maintains safety while reducing friction
  • Documents team-approved permissions
  • Supports glob patterns for flexibility
Never use dangerously-skip-permissions in production or shared codebases. Always prefer explicit permission configuration.

​
Sandboxing

Use /sandbox to reduce permission prompts with file and network isolation.
Claude Code’s sandbox:
  • Runs on your machine (open source)
  • Provides file isolation
  • Provides network isolation
  • Reduces security prompts while maintaining safety
See Sandboxing Documentation for detailed configuration.

​
Settings Customization

Explore settings.json features for a personalized experience:
  • Output Styles — e.g., Explanatory when learning a new codebase
  • Plan Directory — customize where plans are stored
  • Spinner Verbs — customize loading messages

​
Output Styles

Run /config to set an output style:
  • Explanatory — Recommended when learning a new codebase; Claude explains frameworks and patterns
  • Learning — Claude coaches you through making code changes
  • Custom — Create custom output styles to adjust Claude’s voice

​
Spinner Verbs

Customize your spinner verbs to personalize or share with your team: 
{
  "spinnerVerbs": [
    "pondering",
    "architecting",
    "refactoring",
    "deploying"
  ]
}
Check your customized settings.json into git so your team can benefit from shared configuration.

Build docs developers (and LLMs) love

Get started for freeTalk to us