kitten-@-last-used-layout(1)

πŸ’… NAME πŸ’…

kitten-@-last-used-layout β€” bestie, this is the kitty kitten that flips you back to the last used window layout. It's giving "undo, but for your panes" ✨ (this is from the kitten manual, by the way πŸŽ€)


🌸 USAGE 🌸

kitten @ last-used-layout

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so here's the tea β˜•: this command switches to the last used window layout β€” but only in the tabs you specify. Don't specify any tabs? Then it just does the active tab, no big deal, lowkey effortless πŸ’…


✨ OPTIONS ✨

  • --all, -a [=no] β€” change the layout in all the tabs. every single one. go off πŸ‘‘
  • --no-response [=no] β€” don't wait for a response back from kitty. the vibe here is: even if no matching tab is found, the command still exits with a success code. (it's giving "no thoughts, head empty, exit 0" πŸ’€)
  • --match, -m β€” the tab to match! Match specs look like this: field:query. The field can be one of: id, index, title, window_id, window_title, pid, cwd, cmdline env, var, state, session and recent. And query is the expression you're matching with β€” expressions can be either a number or a regular expression, and you can combine them using Boolean operators πŸ”₯

The special value all matches all tabs. iconic, honestly.

For the numeric fields β€” id, index, window_id, pid and recent β€” the expression gets interpreted as a number, not a regular expression. Negative values for id/window_id match from the highest id number down, which means -1 is the most recently created tab/window 🫢

When you use title or id, first a matching tab is looked for, and if that's not found then a matching window is looked for, and the tab for that window gets used. the algorithm is thorough, we stan 🌟

You can also use window_id and window_title to match the tab that contains the window with the specified id or title πŸ‘€

The index number matches the nth tab in the currently active OS window. The recent number matches recently active tabs in the currently active OS window β€” 0 is the currently active tab, 1 is the previously active tab, and so on. a whole little timeline of your tab history, cute 🌈

The field session matches tabs that were created in the specified session. Use the expression ^$ to match windows that were not created in a session, . to match the currently active session, and ~ to match either the currently active session or the last active session when no session is active 🧚

When you use the env field to match on environment variables, you can specify just the environment variable name, or a name and value, for example env:MY_ENV_VAR=2. Tabs containing any window with the specified environment variables are matched. Similarly, var matches tabs containing any window with the specified user variable πŸ’œ

The field state matches on the state of the tab. The supported states are: active, focused, needs_attention, parent_active, parent_focused and focused_os_window. Active tabs are the tabs that are active in their parent OS window. There's only one focused tab and it's the tab to which keyboard events are delivered β€” main character energy, honestly. If no tab is focused, the last focused tab is matched. And the value focused_os_window matches all tabs in the currently focused OS window πŸ‘‘

ngl, a little tip: you can use the kitten @ ls command to get a list of tabs. super handy, no cap πŸ™ˆ
  • --help, -h [=no] β€” show help for this command. we love a self-aware icon πŸŽ€

🌟 GLOBAL OPTIONS 🌟

  • --to β€” an address for the kitty instance to control. This corresponds to the address given to 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 also not found, messages are sent to the controlling terminal for this process β€” which means they'll only work if this process is run within a kitty window πŸͺŸ
  • --password β€” a password to use when contacting kitty. This will cause kitty to ask the user for permission to perform the specified action, unless the password has been accepted before or is pre-configured in kitty.conf. To use a blank password, specify --use-password as always πŸ”
  • --password-file [=rc-pass] β€” a file from which to read the password. Trailing whitespace is ignored. Relative paths are resolved from the kitty configuration directory. Use - to read from STDIN. Use fd:num to read from the file descriptor num. Used if no --password is supplied. 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 no password is available, kitty will usually just send the remote control command without a password. This option can be used to force it to always or never use the supplied password. If it's set to always and no password is provided, the blank password is used πŸ’«

Choices: if-available, always, never


okay bestie that's the whole page, you ate that πŸ’…βœ¨ this was kitten-@-last-used-layout from the kitten manual β€” version 0.49.2, dated Oct 01, 2026 πŸŽ€πŸ¦‹ go forth and switch those layouts, periodt πŸ’–

πŸ“¦ where this page comes from