Omniscio

Import from Hermes (bring a Hermes Agent setup into Omniscio)

Import from Hermes brings a Hermes Agent setup into Omniscio: memories, skills, scheduled jobs, MCP servers and personalities. You pick a Hermes folder, see every item with what will happen to it, tick what you want, and only that is created. Hermes's files are never changed, secrets never travel, and nothing imported runs on its own.

On this page

What it is

A one-way importer for people moving from Hermes Agent (Nous Research) to Omniscio. It reads a Hermes home folder and turns each item into the Omniscio thing that does the same job:

  • Memories (MEMORY.md, USER.md) become Global Memory entries about you.
  • Skills (folders holding a SKILL.md) become your skills.
  • Scheduled jobs (cron/jobs.json) become scheduled jobs.
  • MCP servers (config.yaml) become managed MCP servers.
  • Personalities (config.yaml personalities and a custom SOUL.md) become personalities.

Where to find it

  • Lab switch: Settings, Lab, Import from Hermes (off by default).
  • The section: search Settings for "Hermes", or use the Import from Hermes… link under the Hermes card in Settings, Account.
  • Desktop only. The phone and web views show a note that the import runs in the desktop app.

How it behaves

  1. Pick a home. The section lists the Hermes folders it found: the one HERMES_HOME names, the default folder, and each profile. Choose a folder… accepts a folder you pick only when it looks like a Hermes home.
  2. Read the preview. Every item gets a row, grouped as Personalities, Memories, Skills, Scheduled jobs and MCP servers. Each row says New, Already in Omniscio, Can't import, Needs a look or Couldn't read, with a sentence saying why and any notes on how it will arrive.
  3. Tick what you want. New rows start ticked, except Hermes's own built-in skills and the first-run SOUL.md Hermes writes by itself. A group checkbox ticks the whole group.
  4. Confirm flagged rows. A row whose text looks like planted instructions or a secret is Needs a look. Ticking it opens Import anyway?, which lists what was found; only a confirm imports it.
  5. Pick a project for jobs. When a job is ticked, choose the project imported jobs run in.
  6. Optionally pick a default personality among the ticked personalities, while Personalities is on in Lab.
  7. Import. Only the ticked rows still offered by a fresh read of the folder are created. The result shows how many were created, already there, refused or failed, with a reason for each.

What arrives, and how

  • Memories are skipped when a memory with the same title is already in that scope, whoever wrote it, so importing twice adds nothing. They need Global Memory on in Lab.
  • Skills land in your skills folder. A name you already have, a folder Omniscio itself copied into Hermes, an unsafe name, a folder over the size or file limits and a secret file are refused.
  • Scheduled jobs arrive paused, need no approval, and have self-healing off, so a failing imported script never starts a paid fix session. A schedule Omniscio cannot run exactly (an interval that does not divide the clock, a one-off in the past, too frequent a session job) is refused with its reason. With Scheduled jobs plus on in Lab, a Hermes deliver of origin becomes an inbox delivery target, local becomes no target, and a chat platform is a note naming the service to connect; context_from jobs that are in the same import become chained report context (see Scheduled jobs plus). With it off, those settings are noted and not stored. Tool sets and model pins are noted as not imported.
  • MCP servers arrive switched off. A command or URL that carries a secret is refused; an environment variable whose value is a secret is dropped and its name is listed for you to fill in.
  • Personalities keep their mode: added to the built-in persona, or replacing it (a custom SOUL.md replaces it).

What never happens

  • Nothing under the Hermes folder is written, renamed or deleted.
  • No value from .env or auth.json is read; secret values are never stored, logged or shown.
  • No link or junction inside the Hermes folder is followed.
  • No imported job runs and no imported server starts until you turn it on.
  • Two imports never run at once; one started while another runs is refused, not queued.

Last verified 2026-10-29