View as Markdown Open a local AI agent that can run terminal commands and complete a browser handoff, then paste this prompt in any folder on your computer.
That is enough to begin. Stay nearby while the agent works: you sign in to Cloudflare in your browser, choose between any ambiguous accounts or existing sites, and create your private dashboard password yourself. Never paste a Cloudflare token, dashboard password, or private setup link into the conversation.
What you need #
Section titled “What you need”
- A computer with
Node.js 22.12 or newer. Its standard installer includes npm andnpx
. Ifnpx
is unavailable, ask the agent to help you install Node.js first, then use the same prompt again. - A Cloudflare account. Cloudflare’s included usage is enough for many personal and small sites; usage above its published limits may require a paid plan. - An email address for the private dashboard login.
You do not need Git, Corepack, or a Git-cloned copy of microfeed’s source code. The published CLI contains the matching deployment source and Yarn runtime.
What happens next #
Section titled “What happens next”
- The first command prepares the exact microfeed release in a private cache. Initial setup can take several minutes and use about 1.3 GB; it does not put source files in your current folder.
- Cloudflare opens a browser page for you to sign in. The agent explains each important choice and asks before reusing an existing site or resource.
- After deployment, you open a private one-time setup page and choose the dashboard password yourself.
- The agent runs
npx @microfeed/cli manage status
and continues until the hosted application, dashboard protection, database, and media storage are verified.
The result is a microfeed site in your Cloudflare account with a public website, RSS feed, JSON Feed, and private Admin dashboard.
For detailed browser handoffs, screenshots, and recovery steps, continue to
[Deploy with a local AI agent](./ai-agent/). To run the same guided commands
yourself, follow [Deploy manually](./manual/). After installation, use the
[post-deployment checklist](./after-deploy/) to publish a test item and connect
the content CLI.
Codex, Claude Code, and Cursor are trademarks of their respective owners and are shown only as examples.