An exact map of the machine.

Rashin is Ryoku's optional agent OS. It keeps a generated knowledge vault any coding agent reads, runs a local dashboard on loopback, and sets up Hermes in one click. Local, and off until you turn it on.

Three pieces, all local.

A knowledge vaultGenerated markdown maps of this machine that any coding agent reads instead of rediscovering it.
A local daemonA loopback service with a dashboard for the vault, vitals, and a Hermes chat. It never leaves 127.0.0.1.
One-click HermesSetup installs Hermes, wires it to the vault, and enables the daemon. You pick the provider.

the vault

~/.local/share/ryoku/rashin/
├─ AGENTS.md        entry contract every agent reads first
├─ CLAUDE.md        symlink to AGENTS.md, for Claude Code
├─ system.md        hardware, kernel, drivers, displays
├─ desktop.md       configs, owners, reload commands
├─ packages.md      package sets, versions, update state
├─ ryoku-repo.md    the Ryoku source tree, pre-indexed
├─ user.md          where your config diverges from the base
├─ habits.md        your directories, tools, shell rhythms
├─ memory/          agent-writable durable notes
└─ journal/         agent-writable dated notes

Generated files sit between fence markers. A reindex rewrites only what is inside them, so anything you or your agent adds outside survives.

Turn it on and point your agent at it.

Enable it in Settings, and the vault appears at ~/.local/share/ryoku/rashin. Your agent reads AGENTS.md there first (Claude Code follows the CLAUDE.md symlink), then the generated maps.

bash

# Turn it on in Ryoku Settings > Advanced > Rashin
# (or from a shell)
ryoku-rashin enable

# Your agent reads the vault contract first
cat ~/.local/share/ryoku/rashin/AGENTS.md

# Rebuild the maps at any time
ryoku-rashin index

# ryoku update re-indexes after new configs land
ryoku update

Three things it is not.

No bundled LLMHermes brings its own provider. You choose one during setup.
No remote listenerThe daemon binds loopback only. Nothing leaves the machine.
No MCPMarkdown is the interface every agent already speaks. MCP is a possible later step.

A map, not an assistant.

Some distributions bundle an assistant and market it as the future of Linux. Rashin does something narrower, on facts.

It bundles no assistant. It hands the agent you already run an exact map of this machine.
Everything is local. The daemon binds loopback and nothing leaves it.
It stays off until you turn it on in Settings.
Nothing phones home.
You keep your own provider and model.