Omarchy
2 posts
Setting Up Omarchy: My Arch + Hyprland Dev Laptop
Omarchy is DHH's opinionated Arch Linux setup: Hyprland as a tiling window manager, a themed terminal and Neovim, and every keyboard shortcut already decided for you. It's what my laptop runs, and it's where my local AI stack (Ollama and OpenClaw over Telegram) lives. This is the setup as I'd do it again, in order. Before you start - Use a dedicated drive. The installer wipes the disk you pick and sets up full-disk encryption. Dual-booting on one drive needs the manual install route. - Turn off Secure Boot (and TPM if your BIOS ties them together). The installer won't boot otherwise. - Have a wired or 2.4 GHz keyboard. You type the disk password before Bluetooth exists, so a Bluetooth-only keyboard can't unlock the machine. - Back up anything on that drive. It will be gone. 1. Flash the ISO and install Download the ISO from omarchy.org, write it to a USB stick (balenaEtcher on Windows/Mac, caligula on Linux), and boot from it. The installer asks a handful of questions: keyboard layout, username, password, hostname, timezone. Confirm them, pick the drive, and wait 2 to 10 minutes. 2. Learn these shortcuts on day one Everything in Omarchy is a keystroke. You don't need all of them; you need these, and Super + K shows the rest whenever you forget. The two that change how you work: Super + Alt + Space opens the Omarchy menu (install apps, change themes, update), and Super + 1–4 jumps between workspaces. I keep the editor on 1, browser on 2, terminals on 3 and chat on 4. 3. Update the Omarchy way Don't reach for pacman -Syu out of habit. Use Update Omarchy in the menu (or omarchy update in a terminal). It pulls new configs and runs migrations together with the package upgrade, so a new library version doesn't arrive without the config change it needs. Every update takes a Btrfs snapshot first. If something breaks, reboot, pick the pre-update snapshot in the Limine boot menu, and restore. One catch: snapshots restore the system, not /home. They won't bring back a deleted file, so keep real backups too. You can take one by hand before a risky change: bash omarchy-snapshot create 4. Set up the dev tools Omarchy already ships Neovim (LazyVim), Docker, mise for language runtimes, and AI coding CLIs (c opens OpenCode, cx opens Claude Code). What I add on top: bash Language runtimes through mise mise use -g node@24 python@3.12 Git identity git config --global user.name "Yashank Kothari" git config --global user.email "you@example.com" Anything else from the Arch repos or the AUR yay -S --needed ollama The omarchy command is worth a look too. Run it with no arguments to see every helper the menu uses (themes, fonts, screenshots, debug info). It's also what makes Omarchy easy for an AI agent to configure. 5. Make it yours, safely - Configs live in ~/.config (Hyprland, Waybar, terminal, Neovim). Edit there, not in the Omarchy source. - Try themes with Super + Ctrl + Shift + Space before you start editing colours by hand. - If you wreck your configs, omarchy reinstall resets them to the current release. It overwrites your changes, so commit ~/.config to a dotfiles repo first. What I'd tell myself before installing 1. Give it a week. Tiling feels slow for two days and then you can't go back. 2. Learn Super + K. It answers most questions. 3. Update through the menu, and trust the snapshots. 4. Put local AI on it. Next up: running models with Ollama.
My Own AI Assistant on Telegram: OpenClaw + Ollama on Omarchy
I message a Telegram bot from my phone, and an agent running on my Omarchy laptop answers, using a model served locally by Ollama. No cloud model, no open ports, and the agent can use tools on the machine I gave it. The piece in the middle is OpenClaw, an open-source assistant that connects chat apps to AI agents through a local gateway. Here's the exact setup, with real terminal output from each step. What you need - Ollama running with a model that supports tool calling (ollama show <model lists tools under capabilities). - Node 24.16+ (OpenClaw won't install on Node 22). On Omarchy: mise use -g node@24. - A Telegram account. 1. Install OpenClaw bash npm install -g openclaw@latest --allow-scripts=openclaw openclaw --version There's also a one-line installer (curl -fsSL https://openclaw.ai/install.sh | bash) and, if Ollama is already set up, ollama launch openclaw does the install, model pick and onboarding in one go. 2. Onboard it with Ollama as the model bash openclaw onboard --install-daemon The wizard asks for a model provider (choose Ollama), detects your local models, writes ~/.openclaw/openclaw.json, and installs the gateway as a systemd user service so it starts on login. The scriptable version of the same thing: The relevant part of the config it writes: json { "agents": { "defaults": { "model": { "primary": "ollama/qwen3:0.6b" } } }, "models": { "providers": { "ollama": { "baseUrl": "http://127.0.0.1:11434", "api": "ollama" } } }, "gateway": { "mode": "local", "port": 18789, "bind": "loopback" } } Keep bind on loopback. The gateway can run tools on your machine, so only local clients should reach it. 3. Check the gateway is up bash openclaw gateway status openclaw status 4. Create the Telegram bot 1. In Telegram, open a chat with @BotFather (check the handle exactly). 2. Send /newbot, pick a display name and a username ending in bot. 3. Copy the token it gives you. Treat it like a password. 5. Connect the bot to OpenClaw bash openclaw channels add --channel telegram --token <your-bot-token openclaw channels status --probe Or put it in ~/.openclaw/openclaw.json yourself: json { "channels": { "telegram": { "enabled": true, "botToken": "123456:ABC...", "dmPolicy": "pairing", "groups": { "": { "requireMention": true } } } } } The running gateway hot-reloads the change. dmPolicy: "pairing" is the important line: strangers who find your bot can't talk to your agent until you approve them. 6. Pair your own account Send your bot any message from your phone. That creates a pairing request. Approve it on the laptop: bash openclaw pairing list telegram openclaw pairing approve telegram <CODE Codes expire after an hour. Once approved, every message you send the bot goes to the agent, and its reply comes back in the chat. 7. Make the local model good enough This is where most local setups fall over: - Context window. OpenClaw's system prompt, tools and memory need room. Ollama's docs recommend at least 64k tokens for local models. Set OLLAMACONTEXTLENGTH=65536 on the Ollama service (how). - But context costs RAM. On an 8 GB test box, a 32k context got the model killed mid-load, and the agent just reported provider internal error, HTTP 500. If you see that, check journalctl -u ollama for a killed runner and lower the context or use a smaller model. - Model size. Tiny models can call tools but make poor decisions. Use the biggest tool-capable model your GPU runs comfortably, and keep a small one for quick tests. - Keep it warm. OLLAMAKEEPALIVE=30m stops the first message after a break from waiting for a model load. 8. Day-to-day commands | Command | Use | | --- | --- | | openclaw status | Health, sessions, channels at a glance | | openclaw logs --follow | Watch messages and tool calls live | | openclaw models list | Which model the agent uses | | openclaw doctor | Find and fix config problems | | openclaw gateway stop | Stop the gateway | | openclaw security audit | Check what the agent is allowed to do | Guardrails I'd keep - Pairing on, and only your Telegram user ID allowed. - Gateway on loopback, no port forwarding. - Run openclaw security audit after changing tools or skills, and keep risky tools behind approvals. - Keep the bot token and gateway token out of screenshots and git. None of the ones here show either. The agent loop running behind all this is the one from my AI agents guide, just with a phone on the other end.