a file organizer bot that lists its moves first

start with a backup, then give a bot on your own computer one project folder to tidy. ask for a proposed list of moves and renames, with uncertain files left alone. inspect that list before authorizing changes. dusk bot has file-edit approval settings, but a folder plan is still your responsibility. this routine separates inspection from moving and never treats duplicate-looking names as permission to delete a file.

by the dusk bot team · checked 12 november 2026 · how we made this

pixel art: a purple pixel bot, a yellow pixel bot and a orange pixel bot beside a folder of papers and a desktop computer, on a lemon field in front of snowy hills and green fields, one saying "moves listed before changes"

the routine

make a separate backup of the target folder yourself and open a few files from that backup to check it. then give a bot running on your own computer that project folder. keep it on Ask for approval.

paste this into a chat with your bot

every friday at 5pm, inspect only the project folder i gave you and propose a tidy-up in this chat. this run is a plan, not permission to move anything. ask me before you change anything.

list each proposed operation with its current path, proposed path and reason. group loose receipts under receipts, supplied reference material under references, and unfinished work under working. suggest descriptive names only when the contents make the name clear. keep file extensions unchanged.

leave ambiguous files, shortcuts, hidden files and anything inside an app-managed folder alone. flag name collisions instead of overwriting. do not delete, deduplicate or move anything outside this folder.

wait for me to confirm that my backup is checked and approve specific moves. before any approved move, check the paths still match the plan. stop if a file changed or a destination already exists. afterwards list only the operations actually completed.

when: fridays at 17:00 for inspection; approved moves are a separate step
needs: a bot on your own computer, one project folder you give it and a separately checked backup; no connected app

what comes back looks like this (an example, not a real inbox)

proposed tidy-up for the cedar project

current path -> proposed path | reason
receipt-priya.pdf -> receipts/receipt-priya.pdf | document identifies itself as a receipt
cedar-style-notes.txt -> references/cedar-style-notes.txt | supplied reference notes
draft-jo.txt -> working/draft-jo.txt | file is marked unfinished

left alone: final-final.pdf, purpose unclear.
collision: references/cedar-logo.png already exists; no replacement proposed.

no files moved. confirm the backup is checked and tell me which listed operations to apply.

choose a folder with a clear boundary

use a project folder you understand, rather than your whole home directory. tell the bot what belongs in each destination. “make it neat” leaves it guessing whether an old draft is finished work or an important reference.

files a bot makes on your computer live in its own folder or a project folder you give it.¹ keep this task on the machine holding the originals. the computer-use overview explains the broader setup, but no screen control is required just to ask for a folder plan.

back up before approving the list

use a separate copy or your normal backup method, and check it before the bot edits the original. there's no automatic undo for moved files, so keep your own backup. a written move list helps you review changes; it is not a replacement for a backup.

keep Ask for approval selected while trying the task. Auto-accept edits permits file changes, so leave that setting for a task whose scope you already trust.² the computer safety guide explains why small permissions matter.

leave uncertain files where they are

names alone are weak evidence. two files called “invoice” may belong to different customers, and a shortcut may point somewhere outside the folder. tell the bot to list uncertainty rather than force every item into a category. do not let a tidy-up become deletion.

renaming a file can also break a reference in another document or app. keep app-managed material out of scope and inspect the completed list before continuing work. if the folder contains collected web material, web scraping shows how to retain source information before you reorganize it.

the guard rails

check a separate backup before authorizing any move or rename
make the scheduled routine inspect only, then approve named operations separately
keep the bot on Ask for approval while testing the folder rules
never overwrite a destination or delete a suspected duplicate in this routine
stop when paths differ from the reviewed plan; do not silently improvise a new move

questions

can ai organize files on my computer without touching everything?

give the bot one project folder and require an inspection-only plan. this routine explicitly excludes other folders. review the proposed paths before authorizing the bot to change anything.

can it rename files based on what is inside?

you can ask for proposed descriptive names where the contents are clear. review each suggestion, preserve the extension and leave ambiguous files unchanged. some file types it may not be able to read.

is there an undo button if the folder looks wrong?

do not rely on an automatic undo for folder moves. keep your own checked backup and the operation list. the routine asks for a completed list so you can see what was actually changed.

sources

drafted with ai help from the dusk bot docs and the sources listed on this page, then checked against them. if something here is wrong or out of date, write to [email protected].