momentic-mobile migrate simplified-format rewrites legacy mobile tests and
modules discovered by the project’s include and exclude settings through the
simplified format serializer and sets fileFormat: v2 on
momentic.config.yaml. It does not change the rest of the project config (agent
versions, ai.useMemory, ai.failureRecovery) and does not upgrade your
installed CLI version.
If you want the file rewrite plus a CLI version bump and recommended config
defaults, use
momentic-mobile upgrade
instead.
momentic-mobile@latest, the command warns you and points
at npx momentic-mobile@latest upgrade so you can install the newest
serializers before rewriting your files.
A migration error stops the command, and some files may already have been
rewritten. Revert the local changes made by the command, fix the reported
serialization error, and rerun the migration.
Requires authentication through login or MOMENTIC_API_KEY. The migration
writes identity snapshots so existing step caches can be reused after step IDs
are omitted from YAML. This command has no --dry-run option; use the upgrade
preview to inspect conversion counts for a legacy-format project. If the config
already says v2, that preview skips file discovery and does not report leftover
legacy files. Follow the
migration guide for validation and
rollback.
Options
string
Path to the Momentic configuration file. When omitted, Momentic searches the
current directory and its parents for
momentic.config.yaml or a workspace
configuration. Use this flag to select a project when discovery finds more
than one.string
Momentic API key. Defaults to
MOMENTIC_API_KEY, then the key saved by
login in ~/.momentic/auth.json.boolean
Skip the migration confirmation prompt. Start from a backed-up, clean working
tree.