Skip to main content

Overview

typemux-cc supports three Python LSP backends. You can switch between them using the TYPEMUX_CC_BACKEND environment variable.

Available Backends

Pyright is the default backend if TYPEMUX_CC_BACKEND is not set.

Installation Instructions

Pyright is the default and most stable backend.
Verify installation:

ty (Experimental)

ty is a new Python type checker by the creators of uv (Astral).
Verify installation:
ty is experimental but verified to work with typemux-cc.

pyrefly (Experimental)

pyrefly is Meta’s Python type checker.
Verify installation:
pyrefly is experimental but verified to work with typemux-cc.

Backend Selection

Via Configuration File

Create or edit ~/.config/typemux-cc/config:

Via Environment Variable

Via CLI Flag

Backend-Specific Notes

Pyright

  • Most mature: Production-ready with extensive type checking features
  • Default choice: Automatically selected if TYPEMUX_CC_BACKEND is not set
  • Installation: Available via both npm and pip
  • Best for: General Python development, maximum compatibility

ty

  • Performance focused: Built by Astral (creators of uv and ruff)
  • Experimental: Newer project, still under active development
  • Best for: Users who want cutting-edge performance
  • Note: Some advanced type features may not be fully supported yet

pyrefly

  • Meta-backed: Developed by Facebook/Meta
  • Experimental: Less widely adopted than pyright
  • Best for: Projects already using Meta’s Python tooling
  • Note: Smaller ecosystem and community compared to pyright

Common Issues

Make sure the backend command is available in your PATH before starting typemux-cc. Use which <command> to verify.

Backend not found

Wrong backend being used

Verify your configuration:

Backend crashes

Enable detailed logging:
Then check the logs for backend-specific error messages.