Advanced Configuration

1Code can be configured through environment variables, config files, and UI settings to customize behavior for your workflow.

Configuration Sources

1Code loads configuration from multiple sources in priority order:

UI Settings (highest priority) - Settings panel in the app
Environment variables - Shell profile or .env.local files
Config files - .claude/ directory configs
Default values (lowest priority) - Built-in defaults

Environment Variables

Development & Build

ELECTRON_RENDERER_URL

string

Development server URL. Automatically set by electron-vite during development.Example: http://localhost:5173

MAIN_VITE_API_URL

string

default:"https://21st.dev"

API base URL for backend services. Override for local development.Example: http://localhost:3000

Authentication & API Keys

ANTHROPIC_API_KEY

string

Anthropic API key for Claude models. Used by Claude CLI for custom configurations.

In development mode, this is stripped to allow OAuth testing. In production, it’s preserved for CLI compatibility.

Example: sk-ant-api03-...

ANTHROPIC_AUTH_TOKEN

string

Alternative to ANTHROPIC_API_KEY. Used for OAuth tokens.Example: oauth_token_...

ANTHROPIC_BASE_URL

string

Custom base URL for Anthropic API. Use for proxies or alternative endpoints.Example: https://api.anthropic.com

OPENAI_API_KEY

string

OpenAI API key for voice transcription (Whisper API).Use MAIN_VITE_OPENAI_API_KEY for .env.local files.Example: sk-...

MAIN_VITE_OPENAI_API_KEY

string

OpenAI API key for voice transcription. Vite-compatible format for .env.local.Example: sk-...

Analytics & Monitoring

MAIN_VITE_SENTRY_DSN

string

Sentry DSN for error tracking (optional).Example: https://xxxxx@xxx.ingest.sentry.io/xxxxx

MAIN_VITE_POSTHOG_KEY

string

PostHog project key for analytics (optional, main process).Example: phc_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

MAIN_VITE_POSTHOG_HOST

string

default:"https://us.i.posthog.com"

PostHog API host (optional, main process).

VITE_POSTHOG_KEY

string

PostHog project key for analytics (optional, renderer process).

VITE_POSTHOG_HOST

string

default:"https://us.i.posthog.com"

PostHog API host (optional, renderer process).

FORCE_ANALYTICS

string

default:"false"

Force enable analytics in development. Set to "true" to enable.

Debugging

CLAUDE_RAW_LOG

string

default:"0"

Enable raw Claude CLI output logging. Set to "1" to enable.Automatically enabled in development (unpackaged) builds.

NODE_ENV

string

default:"production"

Node environment. Set to "development" for development mode.

Platform-Specific

SHELL

string

Default shell path. Used for environment loading.Examples:

macOS: /bin/zsh
Linux: /bin/bash
Windows: Uses COMSPEC instead

PATH

string

System PATH for executable discovery. Extended with common tool locations.

Configuration Files

Project Config: .claude/

Project-specific configuration stored in .claude/ directory:

my-project/
  └── .claude/
      ├── skills/           # Project-specific skills
      ├── worktree.json    # Worktree setup commands
      └── mcp-servers.json # MCP server configuration

User Config: ~/.claude/

User-wide configuration in home directory:

~/.claude/
  ├── skills/          # Global skills available in all projects
  ├── plugins/         # Installed plugins
  └── settings.json    # User preferences (managed by app)

Worktree Configuration

Define setup commands for worktrees in .1code/worktree.json:

.1code/worktree.json

{
  "setup-worktree": [
    "bun install",
    "cp $ROOT_WORKTREE_PATH/.env .env",
    "cp $ROOT_WORKTREE_PATH/.env.local .env.local"
  ]
}

setup-worktree

string[]

Array of shell commands to run when setting up a new worktree.Use $ROOT_WORKTREE_PATH to reference the main repo directory.

MCP Server Configuration

MCP servers can be configured globally or per-project:

~/.claude/mcp-servers.json

{
  "my-server": {
    "command": "npx",
    "args": ["-y", "my-mcp-server"],
    "env": {
      "API_KEY": "..."
    }
  }
}

Environment Variable Files

.env.local (Recommended)

Create .env.local in the project root for local development:

.env.local

# Main process env vars (use MAIN_VITE_ prefix)
MAIN_VITE_API_URL=http://localhost:3000
MAIN_VITE_OPENAI_API_KEY=sk-...
MAIN_VITE_SENTRY_DSN=https://...

# Renderer process env vars (use VITE_ prefix)
VITE_POSTHOG_KEY=phc_...
VITE_POSTHOG_HOST=https://us.i.posthog.com

Add .env.local to .gitignore to prevent committing secrets.

Shell Profile

Add environment variables to your shell profile for global availability:

~/.zshrc

# 1Code Configuration
export ANTHROPIC_API_KEY="sk-ant-api03-..."
export ANTHROPIC_BASE_URL="https://api.anthropic.com"
export OPENAI_API_KEY="sk-..."

# Optional: Custom API endpoint
export MAIN_VITE_API_URL="http://localhost:3000"

Restart your terminal or run source ~/.zshrc to apply changes.

Configuration Examples

Development Setup

.env.local

# Use local backend
MAIN_VITE_API_URL=http://localhost:3000

# Enable analytics in dev
FORCE_ANALYTICS=true

# Enable raw logging
CLAUDE_RAW_LOG=1

# Voice transcription
MAIN_VITE_OPENAI_API_KEY=sk-...

Custom API Proxy

~/.zshrc

# Use corporate proxy
export ANTHROPIC_BASE_URL="https://api-proxy.company.com"
export ANTHROPIC_API_KEY="company-key-..."

Offline Development

For offline development with Ollama:

Install Ollama: ollama.ai
Pull a model: ollama pull qwen2.5-coder:7b
Configure in Settings → Models → Ollama

No environment variables needed - 1Code auto-detects Ollama at http://localhost:11434.

Multi-Environment

Use shell aliases for different configurations:

~/.zshrc

# Production
alias 1code-prod='MAIN_VITE_API_URL=https://21st.dev /Applications/1Code.app/Contents/MacOS/1Code'

# Staging
alias 1code-staging='MAIN_VITE_API_URL=https://staging.21st.dev /Applications/1Code.app/Contents/MacOS/1Code'

# Local dev
alias 1code-local='MAIN_VITE_API_URL=http://localhost:3000 /Applications/1Code.app/Contents/MacOS/1Code'

Security Best Practices

Never commit secrets

Add .env.local, .env, and any files with secrets to .gitignore.

.gitignore

.env
.env.local
.env.*.local

Use encrypted storage

When possible, use UI settings instead of environment variables. The app encrypts sensitive data using Electron safeStorage.

Rotate keys regularly

Rotate API keys every 90 days:

Generate new key from provider
Update in 1Code settings/environment
Revoke old key

Use separate keys per environment

Use different API keys for development, staging, and production to limit blast radius of compromised keys.

Restrict key permissions

When possible, create API keys with minimal required permissions. Avoid using admin or root keys.

Environment Loading

From /home/daytona/workspace/source/src/main/lib/claude/env.ts:13-34:

// Keys to strip (prevent interference from unrelated providers)
// NOTE: We intentionally keep ANTHROPIC_API_KEY and ANTHROPIC_BASE_URL in production
// so users can use their existing Claude Code CLI configuration (API proxy, etc.)
const STRIPPED_ENV_KEYS_BASE = [
  "OPENAI_API_KEY",
  "CLAUDE_CODE_USE_BEDROCK",
  "CLAUDE_CODE_USE_VERTEX",
]

// In dev mode, also strip ANTHROPIC_API_KEY so OAuth token is used instead
// This allows devs to test OAuth flow without unsetting their shell env
const STRIPPED_ENV_KEYS = !app.isPackaged
  ? [...STRIPPED_ENV_KEYS_BASE, "ANTHROPIC_API_KEY"]
  : STRIPPED_ENV_KEYS_BASE

Troubleshooting

Environment Variables Not Loading

Check variable name: Use MAIN_VITE_ prefix for .env.local files
Restart app: Changes to environment require app restart
Check file location: .env.local should be in project root
Verify shell profile: For shell vars, ensure profile is sourced

Configuration Conflicts

When multiple sources define the same setting:

UI Settings (highest priority)
User config env vars
Vite env vars (.env.local)
Process env vars
Shell environment
Default values (lowest priority)

Shell Environment Not Working

1Code loads shell environment using:

const shell = process.env.SHELL || "/bin/zsh"
execSync(`${shell} -ilc 'echo $VAR_NAME'`)

Ensure:

Variable is in shell profile (~/.zshrc, not ~/.zshenv)
Profile is executable and doesn’t have errors
Shell is the correct one (check echo $SHELL)

Custom Models

Configure API keys and custom providers

Voice Input

Set up voice transcription with API keys

Skills & Commands

Create custom skills and slash commands

MCP Integration

Configure MCP servers

Get Started

Core Features

Guides

Advanced

Advanced Configuration

Configuration Sources

Environment Variables

Development & Build

Authentication & API Keys

Analytics & Monitoring

Debugging

Platform-Specific

Configuration Files

Project Config: .claude/

User Config: ~/.claude/

Worktree Configuration

MCP Server Configuration

Environment Variable Files

.env.local (Recommended)

Shell Profile

Configuration Examples

Development Setup

Custom API Proxy

Offline Development

Multi-Environment

Security Best Practices

Environment Loading

Troubleshooting

Environment Variables Not Loading

Configuration Conflicts

Shell Environment Not Working

Custom Models

Voice Input

Skills & Commands

MCP Integration

Build docs developers (and LLMs) love

Get Started

Core Features

Guides

Advanced

Documentation Index

​Configuration Sources

​Environment Variables

​Development & Build

​Authentication & API Keys

​Analytics & Monitoring

​Debugging

​Platform-Specific

​Configuration Files

​Project Config: .claude/

​User Config: ~/.claude/

​Worktree Configuration

​MCP Server Configuration

​Environment Variable Files

​.env.local (Recommended)

​Shell Profile

​Configuration Examples

​Development Setup

​Custom API Proxy

​Offline Development

​Multi-Environment

​Security Best Practices

​Environment Loading

​Troubleshooting

​Environment Variables Not Loading

​Configuration Conflicts

​Shell Environment Not Working

​Related Resources

Custom Models

Voice Input

Skills & Commands

MCP Integration

Build docs developers (and LLMs) love

Configuration Sources

Environment Variables

Development & Build

Authentication & API Keys

Analytics & Monitoring

Debugging

Platform-Specific

Configuration Files

Project Config: .claude/

User Config: ~/.claude/

Worktree Configuration

MCP Server Configuration

Environment Variable Files

.env.local (Recommended)

Shell Profile

Configuration Examples

Development Setup

Custom API Proxy

Offline Development

Multi-Environment

Security Best Practices

Environment Loading

Troubleshooting

Environment Variables Not Loading

Configuration Conflicts

Shell Environment Not Working

Related Resources