Step 1: Install Claude Code
- Recommended Installation
- Cursor Guided Installation
Requirements: Node.js 18 or newer
If you encounter permission errors during installation, try using
sudo (MacOS/Linux) or run command prompt as administrator (Windows).Step 2: Configure Coding Plan
Get API Key
- Visit VibeCodeCheap Open Platform, Register or Login.
- Create an API Key on the API Keys page.
- Copy the API Key for use.
Configure Environment Variables
There are 2 ways to configure: via settings.json file (recommended) or via environment variable export.Replace
- Method 1: settings.json File (Recommended)
- Method 2: Export Environment Variables
- Method 3: Using --settings Flag
Step 1: Locate the correct settings.json file path
The configuration file is located in different paths depending on your operating system:- Windows
- macOS
- Linux
Path:
%USERPROFILE%\.claude\settings.jsonExample: C:\Users\YourName\.claude\settings.jsonStep 2: Open settings.json for editing
Choose one of the following methods to open the file:- Using claude command
- VS Code
- Cursor
- Notepad++ / Sublime / Vim
- Manual Opening
This command opens the file in your system’s default editor. If it doesn’t work, try another method below.
Step 3: Add configuration to the file
Add theenv fields to the settings.json file:your_api_key with your VibeCodeCheap API Key and save the file.Common troubleshooting
File open command doesn't work or opens wrong file
File open command doesn't work or opens wrong file
Cause: Commands like
code, cursor may not be in PATH, or file is opened in wrong location.Solution:-
Verify file location:
-
If file doesn’t exist, create directory and file:
-
Open file using absolute path:
Configuration doesn't take effect after saving
Configuration doesn't take effect after saving
- Check JSON format: Use JSONLint to validate
- Close all terminals running Claude Code
- Open a new terminal and run
claudeagain - Run
/statusin Claude Code to verify configuration
Cannot find .claude directory
Cannot find .claude directory
Cause: The
.claude directory hasn’t been created because Claude Code hasn’t been run yet.Solution:- Run
claudeonce (can exit immediately) - Or create manually:
settings.json file being overwritten or losing configuration
settings.json file being overwritten or losing configuration
Cause: Claude Code may automatically overwrite settings.json in some cases.Solution:
-
Backup configuration file:
-
Lock file to prevent overwriting (only when necessary):
-
Unlock when need to edit:
WSL: 'node: not found' error or wrong Node version
WSL: 'node: not found' error or wrong Node version
Cause: WSL is using Windows Node.js instead of Linux version.Check:Solution:
-
Install Node.js for Linux:
-
Fix PATH priority - Add to
~/.bashrcor~/.zshrc: -
Apply changes:
macOS: Permission errors when editing files or running commands
macOS: Permission errors when editing files or running commands
Cause: macOS has gatekeeper and SIP (System Integrity Protection) security.Solution:
- Allow terminal to access files:
- Open
System Settings>Privacy & Security>Full Disk Access - Add Terminal.app or iTerm2
- Open
- Fix directory permissions:
Step 3: Get Started with Claude Code
After configuration, you can start using Claude Code in the terminal:FAQ
How to Change the Model in Use
Mapping between Claude Code internal model environment variables and models:| Model | Multiplier | Context |
|---|---|---|
claude-sonnet-4-5 | 1x | 200K tokens |
claude-sonnet-4-5-20250929 | 1x | 200K tokens |
claude-opus-4-5-20251101 | 2x | 200K tokens |
gpt-5-mini | 0x (free-using) | 128K tokens |
glm-4.6 | 0x (free-using) | 200K tokens |
glm-4.7 | 0x (free-using) | 200K tokens |
~/.claude/settings.json:
- Claude Models
- GPT-5 Mini
- GLM 4.6
- GLM 4.7
How to Check the Current Model Status
Open a new terminal and runclaude, enter /help to see all available commands.
- Enter
/statusto check the current model status. - Enter
/modelsto list all available models.
Manual Configuration Not Working
If you’ve edited the~/.claude/settings.json file but changes don’t take effect:
- Close all Claude Code windows, open a new terminal and run
claudeagain. - If still not working, try deleting the
~/.claude/settings.jsonfile and reconfigure. - Confirm the JSON format is correct, check variable names and ensure no missing or extra commas.

