Initially I just added an auto-import to my PC because I didn’t want to rely on Freewrite’s cloud platform. Maybe there are things I’d rather keep private. I wanted the flexibility of a fully offline sync and storage of all my writing.
I do keep a public blog though, so I added tags. If a title had a #yolo tag, for example, it would kick off a series of shell commands that publish it straight to my WordPress blog.
Other times, when I write with a lot of typos, I’d add a #draft tag that kicks off an AI editor to do mild edits, fixing typos and capitalization.
The next iteration added different editor personas. For a rough draft, I could define whether I wanted light restructuring or full creative freedom. I built a text-based UI to manage this on my PC, and even added the ability to create new personas so I can vary how much creative freedom the AI has.
Today I picked it up again and improved the TUI so I can select multiple entries and combine them into one blog entry. Some days I’d write about something, then a few days later write another entry related to it.
Another thing I added, to free up my writing even more, is inline AI instructions. If I want to change topics mid-session, I can drop in an instruction that my editor picks up when it’s editing or synthesizing the text.
So far it’s worked pretty well.
Building this workflow has freed me up to just keep writing, without thinking about correcting myself or creating a new page.
I can stick to one file a day and just add inline instructions for anything I want to break out into a separate piece later.
It’s really fun to tweak this pipeline into something that works for me. It’s liberating not to rely on apps from providers, and I think it’s great that this device lets us build our own integrations like this.
being in tech 