mise.claude-code-web.toml

# Claude Code Web Environment Configuration
#
# IMPORTANT: Only needed for the Claude Code on Web sandbox.
# Desktop Claude Code and local development do NOT need these settings.
#
# Auto-activated via .miserc.toml, which detects CLAUDE_CODE_REMOTE=true and
# selects this env — so a plain `./bin/mise install` (e.g. the session-start
# hook) picks it up with no MISE_ENV needed.
#
# An explicit MISE_ENV overrides .miserc.toml, so to combine with developer
# tools yourself include this env: MISE_ENV=claude-code-web,dev.
# Multiple environments can be specified with the last taking precedence for
# conflicting values; settings from this file are merged with the others.
#
# Why these settings exist:
# - The web sandbox restricts git operations
# - libgit2 and gix cause "Failed to configure the transport" errors
# - Disabling them allows mise to use alternative git methods

[settings]
# Disable libgit2 and gix to prevent Flutter installation errors in the web sandbox
libgit2 = false
gix = false

[tools]
# Reuse the Node runtime baked into the web-sandbox image instead of downloading
# a fresh copy at session start. The base config pins node = "22"; here we point
# at /opt/node22 (a path: backend, so no version metadata is fetched). Only
# applies when this env is active, i.e. on Claude Code Web — local/CI keep "22".
node = "path:/opt/node22"

# Python and jq are already baked into the web-sandbox image and often get
# pulled in ad hoc (scripting, JSON munging). Point mise at the system copies
# so `mise install` doesn't fetch/build fresh ones every session.
python = "path:/usr"
jq = "path:/usr"