kitten-@-close-tab(1)

💅 kitten-@-close-tab — close the specified tabs ✨

okay so bestie, real talk: this is the kitten-@-close-tab page from the kitten manual, and it's literally the "make these tabs go poof" command. no cap, it's giving main character energy for your tab bar. 🎀

---

🌸 Name

kitten-@-close-tab — close the specified tabs 🫶

---

✨ Usage

kitten @ close-tab

that's it. that's the vibe. 💅

---

💖 Description

so this closes, like, an arbitrary set of tabs. not just one. a whole curated little group of them, and you get to pick which ones. the --match option is your bestie here — you can use it to specify complex sets of tabs to close. 🦋

for example (and this is the iconic one), if you wanna close all the non-focused tabs in the currently focused OS window, you go:

kitten @ close-tab --match "not state:focused and state:parent_focused"

and they're gone. slay. ✨

---

🔥 Options

• --match, -m — the tab to match. match specifications are of the form: field:query. where field can be one of: id, index, title, window_id, window_title, pid, cwd, cmdline, env, var, state, session and recent. query is the expression to match. expressions can be either a number or a regular expression, and can be combined using Boolean operators. 👑

the special value all matches all tabs. periodt.

for numeric fields: id, index, window_id, pid and recent, the expression is interpreted as a number, not a regular expression. negative values for id/window_id match from the highest id number down — in particular, -1 is the most recently created tab/window. 🧚

when using title or id, first a matching tab is looked for, and if not found a matching window is looked for, and the tab for that window is used. iykyk.

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 is used to match the *n*th tab in the currently active OS window. the recent number matches recently active tabs in the currently active OS window, with zero being the currently active tab, one the previously active tab and so on. literally counting backwards through history, bestie.

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 and . 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 using the env field to match on environment variables, you can specify only 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. 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 is only one focused tab and it is the tab to which keyboard events are delivered. if no tab is focused, the last focused tab is matched. the value focused_os_window matches all tabs in the currently focused OS window. 🌈

ngl, you can use the kitten @ ls command to get a list of tabs. do that first if you're not sure what you're aiming at, okay? 🙈

• --no-response [=no] — don't wait for a response indicating the success of the action. ✨ note that using this option means that you will not be notified of failures. like, you're choosing peace and ignorance. valid, but know what you signed up for. 💀
• --self [=no] — close the tab of the window this command is run in, rather than the active tab. it's giving "i'll do it myself". 🫶
• --ignore-no-match [=no] — do not return an error if no tabs are matched to be closed. no drama, no error, just vibes. 🌸
• --help, -h [=no] — show help for this command. the classic. 👑

---

🌟 Global options

• --to — an address for the kitty instance to control. corresponds to the address given to the kitty instance via the --listen-on option or the listen_on setting in kitty.conf. if not specified, the environment variable KITTY_LISTEN_ON is checked. if that is also not found, messages are sent to the controlling terminal for this process, i.e. they will only work if this process is run within a kitty window. so yeah, context matters, bestie. 🎀
• --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 set to always and no password is provided, the blank password is used. 😭

choices: if-available, always, never 🌸

---

⭐ reminder: --no-response means no failures get reported back to you. iconic for speed, tragic for debugging. choose wisely, babe. 💖

---

and that's the whole page, bestie!! this was kitten-@-close-tab(1) from the kitten Manual, version 0.49.2, dated Oct 01, 2026 — go forth and close those tabs, you absolute icon 👑💜🎀