Environment

Turn off the moving faces and the intro. Other values do nothing.

Skip asking the terminal for its background, which chamoji otherwise does once. Light means no foil colours. Other values are ignored.

Draw the faces and the logo in plain ASCII. This is the default on the old Windows console.

The fallback for the theme, when CHAMOJI_THEME isn’t set and the terminal doesn’t answer. A background of 7 or 15 is light; any other number is dark. Without either, chamoji assumes dark.

0 or false turns colour off, and the faces still move. 1, 2 or 3 sets the colour level, whatever the terminal says. true turns colour on at the level the terminal supports.

chamoji 0.14.0 doesn’t read it, so the colour stays. Use FORCE_COLOR=0 instead.

On Windows, chamoji draws its usual faces when this is set, and ASCII when it isn’t, as on the old console.

Set by most CI services. With it, nothing animates, there is no update check, the commit composer hook doesn’t open, and the one-time hints after init and in a monorepo without a release section don’t show. It also sets the colour level when the output is a terminal or FORCE_COLOR=true is set: full colour on GitHub Actions, Gitea Actions and CircleCI; 16 colours on Travis, AppVeyor, GitLab CI, Buildkite, Drone and Codeship. Other CI gets no colour, or 16 colours with FORCE_COLOR=true. A number in FORCE_COLOR always wins. On Windows, the Windows console’s level applies instead.

Nothing animates, and there is no colour unless FORCE_COLOR asks for it.

Don’t check npm for a newer chamoji. The same as --no-update-check.

The same, under the name other CLIs use.

Where the cache goes: $XDG_CONFIG_HOME/chamoji/update-check.json. A relative path is ignored. Default: ~/.config.

Where the cache goes on Windows, when XDG_CONFIG_HOME isn’t set.

The key for Jev, which --ai and the composer’s suggestions use. If it isn’t in the environment, chamoji reads that one line from .env.local, then .env, and no other variable in those files. For --ai on changelog, next-version and release, it reads them in the current folder, tracked files included. Memory search and the MCP server, with --ai, read them in the current folder and skip a file git tracks. The composer reads them at the repo root and skips a file git tracks. Skipping tracked files means a repo you clone can’t send your work to someone else’s account. Without --ai or the composer’s opt-in, nothing is sent.

For git commands that reach the network, such as memory sync, chamoji sets GIT_TERMINAL_PROMPT=0, and uses ssh -o BatchMode=yes unless you set an ssh command, here or in core.sshCommand. A missing password then fails the command instead of waiting for a prompt the face would draw over.

The older way to name an ssh program. When it’s set, chamoji leaves ssh alone, as with GIT_SSH_COMMAND.

init --agents checks whether chamoji is on it. When it isn’t, the server in .mcp.json starts with npx --yes @chamoji/cli mcp instead. setup offers the Claude Code step when claude is on it.