New release v1.0.7: Easier deployment and reliable theme workflows

We are pleased to announce microfeed v1.0.7, bringing together the deployment, theme, editing, and browser-agent improvements introduced across versions 1.0.6 and 1.0.7.

These releases let people deploy and manage microfeed from any folder through the published CLI, expand the Built-in theme catalog to seven purpose-built designs, make remote GitHub theme installation and activation more reliable, and add experimental draft-only tools for compatible browser agents.

Deploy and manage microfeed from any folder

The official @microfeed/cli now includes the complete management launcher. Run npx @microfeed/cli manage without first Git-cloning the microfeed source repository yourself. The launcher downloads the exact tagged release into a private persistent cache, installs its locked dependencies, and keeps saved deployment state separately so later cache repairs cannot erase connected instances.

When a coding agent starts the launcher, it receives the exact deployment skill and management-reference paths to read. It begins with Cloudflare account discovery, distinguishes a new installation from an existing compatible Worker, asks before ambiguous account or site choices, preserves resource-reuse and confirmation safeguards, and continues until status verifies the deployment.

Every existing management command remains available through the same prefix, including account discovery, initialization, connection, deployment, status, local development, themes, snapshots, domains, authentication, Cloudflare Access guidance, and guarded destruction.

Seven Built-in themes and richer previews

microfeed now includes Default, Podcast, Editorial Blog, Photo Grid, Video Channel, Link Digest, and Product Changelog Built-in themes. Each design has its own source, immutable package release, representative demo content, and media-license inventory.

Initialization and deployment synchronize Built-in releases without changing the active theme. New versions are installed inactive so administrators can preview them with either theme-owned demo content or current site content before choosing whether to activate them. Built-ins remain protected from manual deletion, while the Custom-theme version quota increases to 100.

Format v2 themes can also choose whether an Item search result opens its local microfeed page, original URL, or media attachment. Missing destinations fall back safely, Page results remain local, and stable CSS hooks let themes style search details without supplying arbitrary result HTML.

The visual editor now makes newly inserted images and videos responsive on narrow screens while preserving their intended desktop maximum. Existing authored media remains unchanged.

Reliable remote theme workflows

Version 1.0.7 makes public GitHub theme installation independent of GitHub's shared unauthenticated REST API quota. microfeed now resolves public branches, tags, and commits with an anonymous shallow Git fetch while preserving exact-commit installation, declared-file limits, regular-file validation, and symlink rejection.

Remote theme activation, deactivation, rollback, and deletion now reach microfeed correctly instead of being rejected as cross-site form submissions. One-time authorization grants, inactive installation, cleanup, instance selection, confirmation, and verification safeguards remain in place.

Admin theme details now prioritize copyable prompts for an AI coding agent that can run shell commands, such as Codex or Claude Code. An update prompt names the current site and original source, asks the agent to connect the existing site if needed, installs the update inactive, pauses before activation, and verifies the site afterward. Export prompts preserve the exact installed package identity and stop before committing or publishing.

See the theme guide and @microfeed/theme-kit reference for the complete workflows.

Experimental draft-only browser-agent tools

When a signed-in protected dashboard runs in a compatible browser with the native document.modelContext API, microfeed automatically exposes seven concise WebMCP tools. A browser agent can read Items and Pages and save only the visible new or unpublished editor as a draft.

The Worker enforces the result as unpublished again. Publishing, deletion, uploads, settings, default-404 content, published or unlisted content, public pages, and unsupported browsers remain outside the WebMCP surface. Webhook events record webmcp as explicit provenance.

Updating an existing Workers deployment

Open an AI coding agent that can run local shell commands and ask:

Update my existing microfeed site to v1.0.7.

Start by running `npx @microfeed/cli manage`, connect the existing
site if needed, deploy the update, and continue until `status`
verifies the deployment.

The launcher requires Node.js 22.12 or newer with npm, plus Git and Corepack. Complete any Cloudflare browser-authorization handoffs it requests, but never paste a Cloudflare token, password, or private password-setup link into the conversation.

If the intended instance is already saved and unambiguous, the equivalent direct commands are:

npx @microfeed/cli manage deploy --instance <instance-name>

npx @microfeed/cli manage status --instance <instance-name>

The update applies the theme-preview-fixture and WebMCP-provenance migrations, synchronizes the seven-theme Built-in catalog without changing the active theme, runs project checks, builds and deploys the Worker, and verifies the result. Ordinary deployment does not activate a new theme or enable webhooks that were never provisioned.

See the update guide and AI-agent deployment guide for details.

Read the complete notes for v1.0.6 and v1.0.7, or see the combined changelog for every change.