Skip to main content

Documentation 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.

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 unique 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 with pokedo 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.
# Create your first trainer (also initializes the Pokedex)
pokedo init --name "Ash"

# Create a second trainer later (reuses the cached Pokedex data)
pokedo init --name "Misty"
After init, the new trainer is automatically set as the default profile for subsequent commands.
Pass --quick on the first run to initialize with Gen 1 only (151 Pokemon) and get started in seconds. You can add more generations later by running pokedo init --name "Ash" --gen 2, and so on.

Viewing the current profile

Running pokedo profile with no subcommand prints the trainer card for the active default profile:
pokedo profile
The same information is available under the stats group:
pokedo stats profile
Both commands display name, level, XP progress, trainer class, current streak, total Pokemon caught, and earned badges.

Setting the default profile

The default profile is the trainer used by all CLI commands. To change it:
pokedo profile set-default Misty
You can pass either the trainer name or the numeric ID:
pokedo profile set-default 2
If the identifier does not match any trainer, the command prints the list of available trainers and exits with an error.

Viewing stats per profile

Switch to the profile you want to inspect with set-default, then run any stats command:
pokedo profile set-default Misty
pokedo stats profile          # Trainer card
pokedo streaks                # Streak history
pokedo badges                 # Badge progress
pokedo stats inventory        # Item bag
pokedo stats history --days 14  # Task completion history

Switching profiles in the TUI

Press p 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

1

Initialize the new trainer

Run pokedo init with the new trainer name. This creates the profile and sets it as default.
pokedo init --name "Misty"
2

Confirm the profile was created

Run pokedo profile to verify the new trainer card is active.
pokedo profile
3

Switch back to your original trainer

Use set-default with the original trainer’s name or ID.
pokedo profile set-default Ash
4

Verify the switch

Run pokedo profile again to confirm you are back on the correct trainer.
pokedo profile

What each profile stores

Every trainer profile is fully isolated. The following data is scoped per trainer_id:
DataScoped per profile
TasksYes — each trainer has a separate task list
Pokemon collectionYes — box, active team, Pokedex entries
Wellbeing logsYes — mood, sleep, exercise, hydration, meditation
Daily streakYes — current count, best count, milestone timestamps
InventoryYes — Pokeballs, evolution stones, special tickets
BadgesYes — achievement progress and earned badge timestamps
Trainer XP and levelYes
Trainer classYes
All of this lives in ~/.pokedo/pokedo.db. There is one database file; the trainer_id foreign key on every table keeps profiles separated.
Back up your progress by copying the entire ~/.pokedo/ directory. The pokedo.db file contains all trainer profiles, and cache/ holds the downloaded Pokedex and sprite data. Copying both directories is sufficient for a full backup.
cp -r ~/.pokedo ~/.pokedo-backup

Build docs developers (and LLMs) love