Skip to main content
AutomexiaDocs
Ctrl K

Migration from Rio#

If you use Rio, Automexia can import selected settings without changing Rio's files. This guide shows when import runs, what it copies, and how to check the result. Automexia does not replace the rio executable or delete Rio data. This is a one-way configuration import in current source, not a supported package migration. Read Development status before evaluating a build.

Decide whether to import#

The v0.4 import is considered only when Automexia has no config.toml of its own at startup. If you prefer a separate setup, create your own Automexia config first and leave Rio unchanged. In either case, back up both configurations before trying a development revision. See the configuration reference for Automexia's file location.

What can be imported#

When import is eligible, Automexia validates and copies only:

  • Rio's config.toml;
  • .toml files beneath Rio's themes/ directory;
  • bounded installed and disabled marker files beneath the legacy automexia/extensions/ state.

Logs, caches, backups, symlinks, executable content, large marker payloads, and unknown files are not copied. Existing Automexia files win conflicts. An interrupted import can resume, but a completed import does not repeat on each start. Malformed legacy configuration aborts import without installing config.toml.

Check the result before relying on it#

  1. Start a development build with the intended Automexia configuration root.
  2. Confirm the new config.toml and any imported themes are in Automexia's root, not in Rio's files.
  3. Open a non-sensitive session. Check the shell, theme, fonts, and shortcuts you actually use; an imported value may behave differently in this source revision.
  4. If import fails or the result is not what you want, keep Rio and your backups intact. Review the reported error and the resulting Automexia files before making another change. Do not erase Rio data as a repair step.

What migration does not do#

Automexia does not modify Rio's configuration, caches, logs, executable identity, or shell aliases. It does not copy arbitrary Rio files or turn a development build into a stable release. Keep the two configurations separate until you have verified the workflows you need in Automexia.