Devlog #8 - Rename stuff

I spent around 9 hours working on one of the biggest upgrades to M.I.L.O so far: file actions.

Until now, M.I.L.O could find files and understand their contents, but it couldn’t actually do anything with them. I decided to start with Rename.

Now I can tell milo rename my spiderman ticket (pixedH1723.pdf) to spiderman ticket and it asks for confirmation and then renames it.

It remembers which file “it” refers to, asks for confirmation, and then renames it.
A LOT of bugs happened 😭The first problem was that M.I.L.O found the correct Spider-Man ticket but also returned completely unrelated files.

For example, it found:README.md
pixedH1723.pdf

The README contained the words “Spider-Man” and “ticket” because those words were used in an example inside the README.

After filtering README files, M.I.L.O still found random files like:

cd.txt
vintage-ticket-stub.md

because they contained generic words like “ticket”.I fixed this by improving the search scoring system so M.I.L.O considers the combination of important terms instead of matching one generic word.

For a query like: Spider-Man + movie + ticket M.I.L.O now gives much more importance to files that actually contain those concepts together.

I also added path filtering so M.I.L.O ignores internal development folders such as:

node_modules
.git
__pycache__
.local
.agents
.next

Rename itself had a bug too, the first Rename attempt crashed with: name ‘os’ is not defined because the rename code was using Python’s os module without importing it. That was fixed, and I also added protection so M.I.L.O doesn’t rename anything without confirmation, won’t overwrite an existing file, keeps the original file extension, automatically handles files that no longer exist, and remembers the last file found through conversation memory.