kitten-@-load-config(1)

📦
version 0.49.2 · 12 versions
, in arch rolling, nixpkgs unstable

💅 NAME 💅

kitten-@-load-config — bestie, this is the one that (re)loads a config file. That's it, that's the whole vibe. ✨

(Oh and btw, this whole page lives in the kitten manual — it's a kitten @ remote-control situation, so keep that in mind, iykyk.)

🎀 USAGE 🎀

kitten @ load-config  CONF_FILE ...

🌸 DESCRIPTION 🌸

OK so listen 🫶 — this command (re)loads the specified kitty.conf config file(s). Iconic, right?

If you don't specify any files at all, then it just reloads the config file you specified before. No cap, it remembers.

⚠️ Okay this part is important: the paths you give must exist and must be readable by the kitty process — and specifically on the computer where that process is running. Very "who, where, what" of it all. 💀 And relative paths? Those get resolved with respect to the kitty config directory — again, on the computer running kitty. So don't be confused about which machine's config dir, okay? 🦋

✨ OPTIONS ✨

  • --ignore-overrides [=no] — so normally, any config overrides you already set at the kitty invocation command line (or from a previous load-config-file command) are respected, like, they get priority. Use this option to have them ignored instead. It's giving "nvm, forget what I said earlier" 💅
  • --override, -o — override individual config options! You can pass this multiple times, go off. Syntax is name=value. For example: -o font_size=20 🔥
  • --no-response [=no] — don't wait around for a response saying the action succeeded. Sounds chill but... note that using this means you will not be notified of failures 😭 so like, use at your own risk bestie.
  • --help, -h [=no] — show help for this command. Slay, the built-in safety net 🎀

🌈 GLOBAL OPTIONS 🌈

These are the options that come with the whole remote-control thing, not just this command. Still important though! 👑

  • --to — an address for the kitty instance you wanna control 🎯. This corresponds to the address you gave the kitty instance via the --listen-on option, or the listen_on setting in kitty.conf. If you don't specify it, the environment variable KITTY_LISTEN_ON gets checked. And if that's not found either? Then messages get sent to the controlling terminal of this process — which basically means it only works if this process is run inside a kitty window. Sneaky little fallback ngl 🙈
  • --password — a password to use when contacting kitty. This makes kitty ask the user for permission to perform the specified action — unless the password has already been accepted before, or is pre-configured in kitty.conf. Wanna use a blank password? Then you gotta specify --use-password as always. 💜
  • --password-file [=rc-pass] — a file to read the password from. Trailing whitespace is ignored (rude of it to be there anyway 💀). Relative paths get resolved from the kitty configuration directory. Use - to read from STDIN. Use fd:num to read from the file descriptor num. This one is used if no --password is supplied, and it defaults to checking for the rc-pass file in the kitty configuration directory. 🍓
  • --password-env [=KITTY_RC_PASSWORD] — the name of an environment variable to read the password from. Used if no --password-file is supplied. Defaults to checking the environment variable KITTY_RC_PASSWORD. 🧚
  • --use-password [=if-available] — if there's no password available, kitty will usually just send the remote control command with no password at all. This option lets you force it to always or never use the supplied password. And if it's set to always but no password is provided? Then the blank password gets used. ⭐

Choices: if-available, always, never — pick your fighter 💅

okay that's literally the whole page, you ate that 💖 go reload some configs, main character 💖

This page is from the kitten Manual, version 0.49.2, dated Oct 01, 2026 — so if anything looks different in your build, that's why, bestie. 🦋 ✨ 🎀

📦 where this page comes from