All CLI flags can be set via environment variables. CLI flags take precedence over environment variables.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/K-dash/typemux-cc/llms.txt
Use this file to discover all available pages before exploring further.
Core Flags
Path to log file for debug output.When specified, logs are written to both stderr (default) and the specified file.Environment variable:
TYPEMUX_CC_LOG_FILEDefault: Not set (stderr only)Example:Maximum number of concurrent LSP backend processes.The proxy maintains a pool of backends (one per
.venv). When the pool reaches this limit, the least recently used backend is evicted to make room for new ones.Environment variable: TYPEMUX_CC_MAX_BACKENDSValid range: Minimum 1, no upper limitDefault: 8Example:Backend time-to-live (TTL) in seconds.Idle backends are automatically evicted after this timeout to free memory. Set to
0 to disable TTL eviction (backends only evicted via LRU when pool is full).Environment variable: TYPEMUX_CC_BACKEND_TTLDefault: 1800 (30 minutes)Example:LSP backend type to use for Python type checking.Environment variable:
TYPEMUX_CC_BACKENDValid values:pyright- Microsoft’s Pyright type checker (default)ty- Google’s ty type checkerpyrefly- Astral’s pyrefly type checker
pyrightExample:Usage Examples
Basic Usage
Enable Logging
Large Monorepo Configuration
Use Alternative Backend
Combine Multiple Flags
Flag Precedence
When both CLI flags and environment variables are set:- CLI flags take precedence over environment variables
- Environment variables are used if no CLI flag is provided
- Default values are used if neither is set
See Also
- Environment Variables - Alternative configuration method
- Configuration - Detailed configuration strategies
- Architecture - Backend pool management details