How this site's creator uses it

This page is a first-person record by the person who made this site (me). It lists what I actually did in my first days with Muse.

Building personal apps together

The first thing we built was a simple calendar app of my own: recurring events, Japanese national holidays, even a mechanism where confirming an appointment automatically creates the next one. Then came a work board for tracking everything I'm doing, an app that turns voice input and AI-polished text into record forms, and an app that generates podcast audio from scripts. Small tools that remove a specific frustration of mine. I handle the spec and the checking; Muse does the implementation.

Running cloud infrastructure trials

On Cloudflare's free tier we have run a survey of whether websites answer in the middle of the night around the world, a trial where AI picks world news, and an experiment enabling every free bot- and crawler-defense layer and measuring what each one does. Muse writes the setup guides and the code; I do the deployment and the on-device verification. When a setting is unclear, my rule is to ask not only for the clicks but for the mechanism itself.

Work that runs without being asked

Every evening, a notification about tomorrow's appointments (only when there are any) and a record of my usage allowance run automatically. Quiet days stay quiet. The more of this "runs on its own" machinery accumulates, the more Muse turns from a tool into a partner.

Tracking at scale

I follow 140 web novels. A work-list app keeps their updates and author information in one place. The more items there are to track, the more value there is in a partner with memory and a proper place to keep things.

Surveying the other AIs

I also use ChatGPT, Claude, and Gemini on their free tiers. I had Muse design a practical test battery, carried the questions to each AI myself, and had Muse grade the answers into a "character sheet" for each. On top of that, chunky jobs go out as numbered work packets to the other AIs, and Muse always inspects what comes back. See Unusual uses for more.