Yumii keeps all of her state in one folder in your home directory. Knowing the layout means you can back her up, move her, or wipe her — with a file manager.
~/.yumii/
├── auth.json # API keys (owner-only permissions)
├── config.json # non-sensitive settings
├── backend.port # which local port the backend chose this run
├── memory/
│ ├── yumii.db # sessions, summaries, searchable transcript
│ ├── checkpoints.db # full conversation state per session
│ └── store.db # long-term facts about you
├── models/ # downloaded on first launch, then offline forever
│ ├── kokoro/ # her voice (~330 MB)
│ ├── whisper/ # her ears (~130 MB for the default size)
│ └── vosk/ # only if you selected the Vosk STT backend
└── avatar/ # reserved for the future companion modeOn Windows, ~ is C:\Users\<you>.
The two config files
auth.json — secrets. Every API key, owner-only permissions, atomic
writes; each key is sent only to the provider it belongs to. The same
storage model Claude Code uses. Treat it like a password.
config.json — preferences. Plain, human-editable JSON: providers,
personality, model names, connected toolkits. Every key is documented in
the Settings Reference.
Hand-editing works — Yumii reads both at startup, so restart afterward. The dashboard is the friendlier editor.
Practical recipes
| Want to… | Do |
|---|---|
| Back up your companion | Copy ~/.yumii somewhere safe |
| Move to a new machine | Install Yumii there, copy ~/.yumii over, launch |
| Reset conversations, keep settings | Delete memory/ while she's closed |
| Factory reset | Delete ~/.yumii — next launch recreates it and onboarding runs again |
Uninstalling the app never touches ~/.yumii — your data outlives the
program, deliberately. (The complete uninstall, including this folder, is in
Installation.)
What's not on disk
No telemetry file, no analytics ID, no cloud sync state. The complete list of network destinations: the LLM/STT/TTS providers you configured, Composio if you connected apps, and the one-time model downloads on first launch.