What you end up with
TODOLISTO installed like any other app on your Windows PC. It is free, and it stays free — there is no account, no trial and no subscription at the end of this.
- Time
- About 17 minutes
- Steps
- 11
- Cost
- Free
Before you start
These are one-time installs. If you have used PowerShell before, you may have them already — the first step checks.
Install Git
Run the installer, then reopen PowerShell.
Open installerYou know this worked when: Git responds with a version number
Install Node LTS
Run the LTS installer, then reopen PowerShell.
Open downloadYou know this worked when: Node responds with a version number
Install TODOLISTO
Open PowerShell
Keep it open beside this page.
You know this worked when: PowerShell is open
Check Git and Node
Git and the current Node LTS are required.
Type this into PowerShell, then press Enter.
git --version node --versionYou know this worked when: Git and Node respond with version numbers
Copy TODOLISTO to this PC
Type this into PowerShell, then press Enter.
cd ~ if [ ! -d TODOLISTO/.git ]; then git clone https://github.com/CodingBhaiRaghav/TODOLISTO.git fiYou know this worked when: A TODOLISTO folder appears
Open the TODOLISTO folder
Type this into PowerShell, then press Enter.
cd TODOLISTOYou know this worked when: Your terminal prompt is inside the TODOLISTO folder
Use the reviewed version
Type this into PowerShell, then press Enter.
git checkout 2c8861ff4b6c833620ec8dedaf99e822d9a363baYou know this worked when: Git reports the reviewed commit
Try TODOLISTO
Keep PowerShell open.
Type this into PowerShell, then press Enter.
uv run python main.pyYou know this worked when: TODOLISTO opens
Allow Accessibility
Approve it when Windows asks.
You know this worked when: Accessibility is turned on
Allow Notifications
Approve it when Windows asks.
You know this worked when: Notifications is turned on
Try it
TODOLISTO should be open and ready to use.
You know this worked when: TODOLISTO works
If something goes wrong
Nothing here can damage your computer, and every step can be run again safely. If a command fails, the usual cause is the step before it not having finished.
Still stuck? Tell us what happened and we will fix the guide. Include the step number and we can usually reproduce it.