You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
A small self-updating machine/OS spec snapshot for an Omarchy OS Helper Agent
#7620
The text below here is written by Grok after we went back and forth for a couple of hours of exploration on this idea. It started when I just wanted to make a floating webapp, and I went to ask for it, and then realized that I was so tired of writing or copy/pasting my setup every time I want the default agent to help me change something, so here goes:
Impulse
I use an agent as a helper for the live OS — Hyprland, monitors, themes, packages, peripherals, “make this desktop behave.” Code can still come up in that conversation (a hook, a config snippet). The centre of gravity is the running machine.
That helper starts cold. It knows it is on Linux. It does not yet know this is Omarchy on Hyprland, which GPU and driver, what the display is doing, or which keyboard, mouse, and webcam are attached. The omarchy skill already teaches how to customize an Omarchy system. What would make those first turns immediately useful is this machine.
Idea
A short markdown snapshot (~20–30 lines), refreshed after the desktop is up and after omarchy update. One canonical file:
~/.config/omarchy/machine.md
Two layers, with a last mile Omarchy already has a shape for:
Facts — a generator plus an optional overlay. Agent-agnostic.
Injection — Omarchy already knows the user’s default agent. After writing the card, symlink it into that agent’s global auto-load path when the agent has one (for Grok, ~/.grok/rules/).
That is the same kind of table Omarchy already keeps: launch flags in omarchy agent, and skill symlinks into ~/.agents/skills, ~/.claude/skills, ~/.codex/skills, ~/.pi/agent/skills. A snapshot is a different kind of file from a skill, so the table would grow by one optional field: “directory this agent auto-loads extra markdown from.” Agents without such a path simply keep the card at the Omarchy location; the omarchy skill can point the helper at it.
A dedicated file in that auto-load directory, with an absolute path, is what lets the helper treat the card as already present on the first message. When the user runs omarchy default agent <name>, retarget the symlink. Linking the default agent matches the OS helper, which is omarchy agent. Skills are already linked for every known agent; core could do the same for the card with the same table.
What the generator writes
A fixed, short template:
Product from DMI
Omarchy version, Arch, kernel
Hyprland version, Wayland, no DE
CPU (model, cores/threads)
GPU + driver
RAM usable + disks (skip zram)
Displays from hyprctl monitors (connector, model, resolution, refresh, scale)
USB named devices (keyboard, mouse, webcam), so the helper can talk about the actual kit
Triggers that already exist:
~/.config/omarchy/hooks/post-boot.d/ — after the desktop starts, so hyprctl works
~/.config/omarchy/hooks/post-update.d/ — during omarchy update
Optional ~/.config/omarchy/machine.overlay.md for facts USB and DMI will not give you (retail name vs ODM, power over Thunderbolt from the monitor). The generator appends it, so the script stays generic.
Stamp generated. It is a snapshot. When the task depends on what is plugged in now, the helper can still query live (hyprctl, lsusb).
What I have running
Generator, overlay, and those two hooks. The card is about 200 tokens. After a reboot, a new helper session already had the snapshot and could describe the machine. Naming the agent’s global auto-load path (absolute) is what made that first turn land.
Ask
Would Omarchy like to carry:
a small machine.md + overlay + post-boot / post-update refresh, and
a symlink to the default agent’s global auto-load path, for agents that have one,
as something people can use when the agent is a desktop/OS helper?
I am happy to share the generator. The per-agent path table can stay tiny and skip-unknown, in the same spirit as skills and omarchy agent.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
The text below here is written by Grok after we went back and forth for a couple of hours of exploration on this idea. It started when I just wanted to make a floating webapp, and I went to ask for it, and then realized that I was so tired of writing or copy/pasting my setup every time I want the default agent to help me change something, so here goes:
Impulse
I use an agent as a helper for the live OS — Hyprland, monitors, themes, packages, peripherals, “make this desktop behave.” Code can still come up in that conversation (a hook, a config snippet). The centre of gravity is the running machine.
That helper starts cold. It knows it is on Linux. It does not yet know this is Omarchy on Hyprland, which GPU and driver, what the display is doing, or which keyboard, mouse, and webcam are attached. The omarchy skill already teaches how to customize an Omarchy system. What would make those first turns immediately useful is this machine.
Idea
A short markdown snapshot (~20–30 lines), refreshed after the desktop is up and after
omarchy update. One canonical file:~/.config/omarchy/machine.mdTwo layers, with a last mile Omarchy already has a shape for:
~/.grok/rules/).That is the same kind of table Omarchy already keeps: launch flags in
omarchy agent, and skill symlinks into~/.agents/skills,~/.claude/skills,~/.codex/skills,~/.pi/agent/skills. A snapshot is a different kind of file from a skill, so the table would grow by one optional field: “directory this agent auto-loads extra markdown from.” Agents without such a path simply keep the card at the Omarchy location; the omarchy skill can point the helper at it.A dedicated file in that auto-load directory, with an absolute path, is what lets the helper treat the card as already present on the first message. When the user runs
omarchy default agent <name>, retarget the symlink. Linking the default agent matches the OS helper, which isomarchy agent. Skills are already linked for every known agent; core could do the same for the card with the same table.What the generator writes
A fixed, short template:
hyprctl monitors(connector, model, resolution, refresh, scale)Triggers that already exist:
~/.config/omarchy/hooks/post-boot.d/— after the desktop starts, sohyprctlworks~/.config/omarchy/hooks/post-update.d/— duringomarchy updateOptional
~/.config/omarchy/machine.overlay.mdfor facts USB and DMI will not give you (retail name vs ODM, power over Thunderbolt from the monitor). The generator appends it, so the script stays generic.Stamp
generated. It is a snapshot. When the task depends on what is plugged in now, the helper can still query live (hyprctl,lsusb).What I have running
Generator, overlay, and those two hooks. The card is about 200 tokens. After a reboot, a new helper session already had the snapshot and could describe the machine. Naming the agent’s global auto-load path (absolute) is what made that first turn land.
Ask
Would Omarchy like to carry:
machine.md+ overlay + post-boot / post-update refresh, andas something people can use when the agent is a desktop/OS helper?
I am happy to share the generator. The per-agent path table can stay tiny and skip-unknown, in the same spirit as skills and
omarchy agent.All reactions