marceloeatworld/hyprland-ai-skill
hyprland
FlaggedThis skill should be used when the user asks about "Hyprland configuration", "hyprland.lua", "hyprland.conf", "Hyprland Lua config", "hyprctl", "Hyprland keybinds", "Hyprland window rules", "Hyprland monitors", "Hyprland dispatchers", "Hyprland animations", "Hyprland workspaces", "Hyprland IPC", "Hyprland plugins", "hyprlock", "hypridle", "hyprpaper", "hyprcursor", "hyprpicker", "hyprsunset", "xdg-desktop-portal-hyprland", "Hyprland on NixOS", "Hyprland Home Manager", "Hyprland layouts", "Hyprland dwindle", "Hyprland master layout", "Hyprland FAQ", "Hyprland performance", "Hyprland Nvidia", "Hyprland screen sharing", "Hyprland special workspace", "Hyprland smart gaps", "Hyprland multi-monitor", "Hyprland tearing", or any topic related to configuring, troubleshooting, or extending the Hyprland Wayland compositor and its ecosystem tools.
references/notifications.md
View on GitHub<!-- source: https://wiki.hypr.land/configuring/core/advanced-configuration/notifications -->
<!-- wiki commit: 41c7222 (2026-11-20 18:16:21 +0100) -->
<!-- auto-generated by scripts/generate-references.sh - DO NOT EDIT MANUALLY -->
---
weight: 30
title: Notifications
---
Hyprland has simple built-in notification system.
Notifications are simple text boxes, with an optional icon, positioned in the top-right corner of the active monitor.
**They are not meant to handle your system notifications.**
## Parameters
| Name | Description | Type | Default | Limits |
| --- | --- | --- | --- | --- |
| text | Text of the notification | string | [[Empty]] | |
| timeout | Timeout/duration in ms | int | [[Required]] | |
| icon | Icon type, see [below](#icon)| string | `"none"` | |
| color | Notification color. `0` means "default color for icon" | color | 0 | |
| font_size | Size of the font used to display the notification | int | 13 | |
### Icon
Icon can be one of the following, selected by either Lua name or hyprctl ID:
| Name | Lua name | hyprctl ID | Default color |
| --- | --- | --- | --- |
| None | none | -1 | <code style="background-color:#000000;color:#FFFFFF">#000000</code> |
| Warning | warn/warning | 0 | <code style="background-color:#FFCC66;color:#000000">#FFCC66</code> |
| Info | info | 1 | <code style="background-color:#80FFFF;color:#000000">#80FFFF</code> |
| Hint | hint | 2 | <code style="background-color:#B3FFCC;color:#000000">#B3FFCC</code> |
| Error | err/error | 3 | <code style="background-color:#FF4D4D;color:#000000">#FF4D4D</code> |
| Confused | confused/question | 4 | <code style="background-color:#FFCC99;color:#000000">#FFCC99</code> |
| Ok | ok | 5 | <code style="background-color:#80FF80;color:#000000">#80FF80</code> |
## Creating a notification
### Lua
```lua
-- Just push a notification
hl.notification.create({ text = "Hello from Lua!", timeout = 15000, icon = "info", font_size = 20 })
-- Assign "HL.Notification" object to "somevar" for later use and push the notification
local somevar = hl.notification.create({ text = "Please store me", timeout = 228638, icon = "hint" })
-- Get a table of all active notifications as "HL.Notification" objects
hl.notification.get()
```
### Hyprctl
To create a notification from hyprctl, you can use `hyprctl notify` command.
It takes the same information as `hl.notification.create()`, but in a slightly different format.
See more about it [here](../using-hyprctl#notify).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |