Snippets are saved commands. They exist for the things you type over and over: a health check, a log query, a service restart, the awkward journalctl invocation you can never remember.
Open Snippets in the left navigation. The list shows every Snippet you have saved, with a search box at the top that matches names, descriptions, and the command text itself.
Create a Snippet
Click Add Snippet.
Give it a Name, a short label such as "restart dispatcher".
Write a Description saying what it does and when you would reach for it.
Put the command in Code. Multiple lines are fine, so a short script works as well as a one-liner.
Save. A Snippet created confirmation appears.
Use a Snippet
Find it, click Copy, and paste it into your terminal session.
Copying is the only action. Luumen does not run snippets for you, and LuumenAI does not run them either. A snippet stores a command; it does not automate one. For something LuumenAI can carry out with approval at each step, use a Skill.
Placeholders
There are no variables or templating. A snippet is stored exactly as you typed it. When a command takes an argument that changes, write the placeholder plainly so you notice it before running, for example systemctl restart SERVICE.
Snippets Are Personal
Snippets are not visible to other members of your workspace, and there is no shared library. To give a teammate one, send them the text. If a teammate needs a full procedure rather than a single command, make it a workspace Skill instead.
Edit or Delete a Snippet
Open a snippet to see its details, then choose Edit to change the name, description, or code, or Delete to remove it. Deleting is immediate and cannot be undone.