PICOM-INSPECT(1)

💖 PICOM-INSPECT 💖

okay so bestie, let me put you onto picom-inspect — it's the little tool from the picom world that lets you easily test your picom rules ✨ no cap.

---

✨ SYNOPSIS ✨

picom-inspect [OPTIONS]

---

🦋 DESCRIPTION 🦋

So here's the vibe: picom-inspect matches your picom rules against a window of your choosing 👑 like, you point it at a window, and it tells you which of your rules are (and aren't) doing their thing.

It helps you test your rules, and shows you which ones of your rules (don't) work. literally a vibe check for your config, fr fr 💅

---

🎀 OPTIONS 🎀

First thing you gotta know: picom-inspect accepts all options that picom does. Naturally, most of those options will not be relevant 🙈 but like, they're there.

These are some of the options you might find useful (See picom(1) for descriptions of what they do):

• --config
• --log-level
• --log-file
• all the options related to rules 💜

picom-inspect also accepts some extra options:

🌸 Extra options 🌸

• --monitor — keep picom-inspect running in a loop, and dump information every time something changed about a window. it's giving surveillance but make it helpful 👀✨

---

💀 NOTES 💀

picom-inspect is prototype right now. it's lowkey still in its experimental era, so pls be gentle 🥺

If you find any bug — for example, if rules are matched differently compared to picom — please submit bug reports to:

https://github.com/yshui/picom

---

🌈 RESOURCES 🌈

• Homepage: https://github.com/yshui/picom

---

👑 SEE ALSO 👑

• xcompmgr(1)
• picom(1)

---

💜 AUTHOR 💜

Yuxuan Shui

---

okay that's the whole page, you ate that 🫶 this was the picom-inspect page, dated 2026-02-07, and yeah it's from the picom-inspect crew — go forth and debug your rules, bestie, periodt 💅🎀