Claude Code v2.0.71: Configuration Control and Prompt Suggestions
You’re working through a complex debugging session. Claude Code suggests prompts based on context, and usually they’re helpful. But right now, you’re deep in thought, crafting a specific query that requires precision. The suggestions keep appearing, interrupting your flow.
Or maybe you’re the opposite user: you love suggestions. They speed up your workflow, help you discover features, and reduce typing. You want them everywhere, all the time.
Claude Code v2.0.71 gives you control. A new /config toggle lets you enable or disable prompt suggestions on demand, alongside a convenient /settings alias, Bedrock integration improvements, and bug fixes for path handling and permissions.
Control Prompt Suggestions
What changed: A new toggle in /config allows you to enable or disable prompt suggestions.
Why this matters: Prompt suggestions are valuable - they help you discover features, speed up common workflows, and reduce typing. But they’re not universal. Different tasks demand different interfaces. When you’re composing a carefully worded prompt that requires focus, suggestions can interrupt your thought process. When you’re moving quickly through familiar tasks, suggestions accelerate your workflow.
How to use: Access the configuration menu with /config and toggle prompt suggestions on or off based on your current needs. The setting persists across sessions, so you can set it once and forget it - or change it dynamically as your workflow shifts.
Example scenarios:
- Suggestions on: Exploring new features, learning command syntax, or moving quickly through repetitive tasks
- Suggestions off: Writing complex prompts, debugging intricate issues, or focusing on specific technical requirements
Settings Command Alias
What’s new: You can now use /settings as an alias for the /config command.
Why it helps: Discoverability and intuitiveness. New users expect “settings” as the natural command for configuration. Experienced users might prefer the brevity of /config. Both work now - use whichever matches your mental model.
This is the kind of small polish that reduces friction. When you’re looking for configuration options, both commands take you where you need to go.
Bedrock Integration Enhancement
What changed: The ANTHROPIC_BEDROCK_BASE_URL environment variable is now respected for token counting and inference profile listing.
Why this matters: Enterprise users running Claude Code with Amazon Bedrock can now specify custom base URLs for their deployments. Previously, token counting and inference profile listing didn’t respect this environment variable, limiting flexibility for custom Bedrock configurations.
Technical detail: Token counting and inference profile listing operations now use the custom base URL when ANTHROPIC_BEDROCK_BASE_URL is set. This ensures consistent behavior across all Bedrock operations in environments with custom endpoints or proxy configurations.
Use case: Organizations with custom Bedrock deployments, regional endpoints, or proxy configurations can now configure Claude Code once via environment variable and have all operations - including token counting and profile listing - work correctly.
New Syntax Highlighting Engine
What’s new: Claude Code’s native build now includes a new syntax highlighting engine.
Impact: Improved syntax highlighting performance and quality for code displayed in the CLI. This is infrastructure work that enhances the visual experience when Claude Code displays code, making syntax patterns clearer and easier to parse visually.
Bug Fixes and Stability
Version 2.0.71 includes three targeted fixes for file path handling, MCP server loading, and shell command permissions:
1. File Reference Suggestions
Fixed: @file reference suggestions no longer trigger incorrectly when the cursor is in the middle of a path.
Before: If you were typing a file path and your cursor was mid-path (e.g., editing src/|utils/helper.js where | is your cursor), Claude Code would trigger file reference suggestions inappropriately, interrupting your editing flow.
After: File reference suggestions now trigger only when contextually appropriate - at the start of a path or when explicitly invoked. Mid-path cursor positions no longer cause unwanted suggestion popups.
Impact: Smoother editing experience when working with file paths. No more fighting with suggestion popups while editing existing paths.
2. MCP Server Loading with Skip Permissions
Fixed: MCP servers from .mcp.json now load correctly when using the --dangerously-skip-permissions flag.
Before: Running Claude Code with --dangerously-skip-permissions failed to load MCP servers defined in .mcp.json. This created an inconsistency - the flag was meant to bypass permission checks but inadvertently broke MCP server initialization.
After: MCP servers load correctly regardless of permission flag settings. The --dangerously-skip-permissions flag now works as intended without breaking MCP functionality.
Impact: Developers using custom MCP servers in trusted environments can use the permission skip flag without losing MCP capabilities. Particularly useful for automation, testing, or controlled internal deployments.
3. Shell Glob Pattern Permissions
Fixed: Permission rules no longer incorrectly reject valid bash commands containing shell glob patterns.
Before: Commands like ls *.txt or for f in *.png; do echo $f; done were incorrectly flagged by the permission system. The wildcard syntax (*, ?, etc.) confused permission parsing, leading to false rejections of valid commands.
After: The permission system correctly handles shell glob patterns. Wildcards in bash commands are now recognized as legitimate syntax rather than permission violations.
Impact: Natural bash workflows with wildcards work without permission errors. You can use glob patterns like *.txt, **/*.js, or [0-9]* in commands without triggering false security warnings.
Getting Started
These features are available in Claude Code v2.0.71. Update to the latest version:
# Update Claude Code
npm update -g @anthropic-ai/claude-code
# Check your current version
claude --versionConfigure prompt suggestions:
- Type
/configor/settingsin Claude Code - Find the prompt suggestions toggle
- Enable or disable based on your workflow preferences
- The setting persists across sessions
Set up Bedrock custom URL:
# Add to your shell profile (~/.bashrc, ~/.zshrc, etc.)
export ANTHROPIC_BEDROCK_BASE_URL=https://your-custom-bedrock-endpoint.example.comTry glob patterns:
# These commands now work without permission issues
ls *.md
cat src/**/*.ts
for file in *.json; do echo "Processing: $file"; doneWhat’s Next
Claude Code v2.0.71 continues the focus on control and polish. The /config toggle for prompt suggestions gives you fine-grained control over your interface. The /settings alias makes configuration more discoverable. Bedrock improvements support enterprise deployments. Bug fixes remove friction from daily workflows.
These improvements don’t announce themselves with flashy features, but they remove small frictions that accumulate over time. Better configuration control means workflows that adapt to your needs. Better bug fixes mean fewer interruptions and unexpected behaviors.
For complete release notes and updates, see the official changelog.
Resources: