Your Omarchy.
With a memory.

Step 01 · Install

One command, as usual.

Open a terminal on your Omarchy desktop and run the Linux local installer. It sets up the runtime, memory storage, and the desktop app, then wires capture and recall into the supported agent tools it finds on your machine.

$ curl -fsSL https://get.rivethub.io/local.sh | bash

Read the installer · Full local setup guide

1. Follow the setup output. Review the detected tools and connection instructions.
2. Open RivetHub. The Linux desktop app should find your local node. If it opens without a connection, go to Settings, set the Gateway URL to https://localhost:5174, and save. You can also use the local browser interface.
3. Check your node. Run rivetos local status if setup or connection needs checking.

Already running a hub? Get the Linux desktop app and connect to that hub instead of installing another one.

Step 02 · Theme

Make it follow your theme.

1. Choose a theme in Omarchy. Open the Omarchy Menu with Super + Alt + Space, then choose Style → Theme.
2. Open RivetHub desktop Settings → Appearance. Select Omarchy to use the detected desktop palette. The selected theme’s name appears there.
3. Match the terminal. In terminal settings, set Color palette → App theme so the terminal follows the app’s Omarchy colors too.
4. Switch whenever you like. After changing your Omarchy theme, bring RivetHub back into focus to refresh its colors.

System and Omarchy are different choices. System follows light or dark mode. Omarchy reads the active theme’s palette. An imported terminal palette is a saved selection; choose App theme to keep following desktop changes.

Theme switching shortcuts and community themes are covered in the official Omarchy theme guide.

Step 03 · First memory

Make your first memory.

1. Start with a connected tool. Ask your agent to complete a small task with a recognizable detail, such as explaining a function in a sample project.
2. Find the captured session. Open it in RivetHub and check that the conversation and tool output you expect are there.
3. Ask another connected agent to recall it. Have it search memory for that detail and continue the work using the saved context.

Capture and recall depend on each integration being connected and your node running. Check supported integrations before relying on a new tool.

Your record lives locally. Agent providers still process the prompts you send them; optional embedding and compaction services process the content sent to them.

Questions

Good to know.