PokeDo supports multiple trainer profiles inside the same local SQLite database. Every profile is a fully independent trainer: it has its own task list, Pokemon collection, wellbeing logs, daily streak, inventory, and badges, all scoped by a uniqueDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/tldrwtf/pokedo/llms.txt
Use this file to discover all available pages before exploring further.
trainer_id. Multiple profiles are useful for household members sharing a machine, for running a casual playthrough alongside a focused one, or for experimenting with different trainer class builds without resetting your main save. The CLI always operates on the active default profile; the TUI lets you switch profiles interactively.
Creating a profile
Profiles are created withpokedo init. You can run init as many times as you like — each call with a new --name value creates a separate trainer and sets it as the default.
init, the new trainer is automatically set as the default profile for subsequent commands.
Viewing the current profile
Runningpokedo profile with no subcommand prints the trainer card for the active default profile:
stats group:
Setting the default profile
The default profile is the trainer used by all CLI commands. To change it:Viewing stats per profile
Switch to the profile you want to inspect withset-default, then run any stats command:
Switching profiles in the TUI
Pressp from the TUI dashboard to open the profile-switcher modal. It lists every trainer with their current level. Select a profile and click Continue. To make the selection persist across sessions, check Set as default profile before confirming — this is equivalent to running pokedo profile set-default <name> from the CLI.
Creating a second profile step by step
Initialize the new trainer
Run
pokedo init with the new trainer name. This creates the profile and sets it as default.What each profile stores
Every trainer profile is fully isolated. The following data is scoped pertrainer_id:
| Data | Scoped per profile |
|---|---|
| Tasks | Yes — each trainer has a separate task list |
| Pokemon collection | Yes — box, active team, Pokedex entries |
| Wellbeing logs | Yes — mood, sleep, exercise, hydration, meditation |
| Daily streak | Yes — current count, best count, milestone timestamps |
| Inventory | Yes — Pokeballs, evolution stones, special tickets |
| Badges | Yes — achievement progress and earned badge timestamps |
| Trainer XP and level | Yes |
| Trainer class | Yes |
~/.pokedo/pokedo.db. There is one database file; the trainer_id foreign key on every table keeps profiles separated.