Beta Features and Early Access

Claude Code continues to evolve rapidly with experimental features and beta programs. This guide explains how to access, test, and provide feedback on cutting-edge capabilities before they reach general availability.

Understanding Feature Stages

Alpha

Internal or limited testing with significant changes expected. May have bugs or incomplete functionality.

Beta

Feature-complete but gathering feedback. Available to specific user groups or plans.

Preview

Near-final implementation. Broadly available but may have minor adjustments.

Generally Available. Stable, supported, and recommended for production use.

Current Beta Features

GitHub Actions Integration Beta

Claude Code GitHub Actions enables AI-powered automation in your GitHub workflow:

name: Claude Code Review
on: [pull_request, issue_comment]

jobs:
  claude-action:
    runs-on: ubuntu-latest
    steps:
      - uses: anthropics/claude-code-action@beta
        with:
          github-token: ${{ secrets.GITHUB_TOKEN }}
          anthropic-api-key: ${{ secrets.ANTHROPIC_API_KEY }}

Features:

Respond to @claude mentions in issues and PRs
Automatic code review and implementation
Follows repository’s CLAUDE.md guidelines
Creates branches, commits, and PRs automatically

Native Binary Installation Alpha

An experimental installation method that provides platform-native binaries:

# From existing Claude Code installation
claude install

# Fresh install via script
curl -fsSL claude.ai/install.sh | bash

Figma Dev Mode MCP Server Beta

Design-to-code integration through Model Context Protocol:

# Enable in Figma Desktop App
# Preferences → Dev Mode → Enable MCP Server

# Add to Claude Code
claude mcp add --transport sse figma-dev-mode http://127.0.0.1:3845/sse

Capabilities:

Generate code from Figma designs
Extract design tokens and variables
Access Code Connect mappings
Screenshot design regions

Experimental Flags and Features

Environment Variables

CLAUDE_CODE_SHELL

Override automatic shell detection (v2.0.65)

export CLAUDE_CODE_SHELL=/bin/zsh

CLAUDE_CODE_PROXY_RESOLVES_HOSTS

Enable proxy DNS resolution (opt-in since v2.0.55)

export CLAUDE_CODE_PROXY_RESOLVES_HOSTS=true

CLAUDE_BASH_MAINTAIN_PROJECT_WORKING_DIR

Lock Bash tool to project root directory

export CLAUDE_BASH_MAINTAIN_PROJECT_WORKING_DIR=1

MCP_TIMEOUT

Adjust MCP server startup timeout (milliseconds)

export MCP_TIMEOUT=30000

Model Context Protocol (MCP) Servers

The MCP ecosystem includes many production-ready servers:

Playwright/Puppeteer: Browser automation and testing
Git: Version control operations
GitHub/GitLab: Repository management
PostgreSQL/MySQL: Database operations

Accessing Features

Subscription Access

As of version 2.0.58, Claude Code is available to:

Claude Pro Plan: Full access to Claude Code with Opus 4.5 model (upgraded from Sonnet-only in Nov 2025!)
Claude Max Plan: Enhanced limits and priority Opus 4.5 access
Enterprise Plans: Custom configurations and support

Checking Your Version

# View current version and features
claude --version

# Check system information
claude doctor

# View available slash commands
claude /help

# Check MCP server status
claude /mcp list

Recent Features (2025)

Based on recent releases, these features have graduated from beta to GA:

Claude Code for Desktop

Released in v2.0.51 - Standalone desktop application (Download)

Background Agents

Released in v2.0.60 - Run agents in background while you work

Named Sessions

Released in v2.0.64 - Use /rename and /resume <name> for session management

Rules Directory

Released in v2.0.64 - New .claude/rules/ directory for memory organization

Prompt Suggestions

Released in v2.0.67 - Tab to accept AI-suggested prompts

Model Switching

Released in v2.0.65 - Switch models with alt+p / option+p while typing

Opus 4.5 for Pro

Released in v2.0.58 - Pro users now have Opus 4.5 access

Hooks System

Released in v1.0.38 - User-defined automation points

Community-Driven Innovation

Contributing Ideas

GitHub Issues: Report bugs and request features at the official repository
Community Forums: Share use cases and workflows
Direct Feedback: Use /feedback command in Claude Code
Pull Requests: Contribute code directly to open-source components

# Create test environment
mkdir claude-test && cd claude-test
git init

# Test with clean configuration
claude --no-config

# Use temporary settings
export CLAUDE_CONFIG_DIR=~/.claude-test

# Disable auto-updates for testing
claude config set disableAutoUpdate true

# Use debug logging
export ANTHROPIC_LOG=debug

Upcoming Features

Based on community discussions and development patterns:

Enhanced CI/CD

Deeper integration with build pipelines beyond GitHub Actions

Team Collaboration

Shared contexts and collaborative coding sessions

Plugin System

Extensible architecture for custom integrations

Performance Mode

Optimized for large-scale refactoring operations

Providing Feedback

Effective Bug Reports

Environment Details
Terminal window
```
claude doctor > diagnostic.txt
```
Reproduction Steps
- Minimal test case
- Expected vs actual behavior
- Error messages and logs
Submit via Appropriate Channel
- GitHub Issues for bugs
- /feedback for suggestions
- Community forums for discussion

Best Practices for Beta Testing

Version Control

Always commit before testing new features

Incremental Testing

Start with non-critical projects

Document Findings

Keep notes on behavior changes

Share Knowledge

Help others with your discoveries

Troubleshooting Beta Features

Common Issues

MCP Server Connection Problems:

# Debug MCP connections
claude --mcp-debug

# Check server logs
claude /mcp logs <server-name>

# Restart MCP servers
claude /mcp restart

Permission Issues:

# Reset permissions
claude /permissions reset

# View current permissions
claude /permissions list

Model Access:

# Check available models
claude /models

# Upgrade plan if needed
claude /upgrade