Frequently Asked Questions

Frontman is an AI website editor for existing sites. It runs inside WordPress or your framework dev server, shows chat beside a live view of your site, and lets you click what you want changed. For WordPress, it uses WordPress-native tools. For Next.js, Astro, and Vite sites, it outputs real code your team can review and merge.

Cursor and Claude Code are built for developers working from files or terminals. Frontman starts from the website itself. It sees the live page, selected elements, CSS, CMS or component context, routes, and logs, so website changes start from what marketers, designers, and site owners can actually see.

Frontman is built for WordPress site owners and maintainers, plus marketing and design teams responsible for Next.js, Astro, or Vite websites. Developers still install and review code-backed changes, but routine website edits can start from the browser instead of a ticket.

Yes. Frontman is open source on GitHub at github.com/frontman-ai/frontman. Every prompt, every tool call, and every piece of context the agent uses is visible in the source. Licenses vary by package and integration, and are declared in the repository and release artifacts.

Update landing page copy, CTAs, hero sections, spacing, colors, mobile polish, navigation menus, WordPress blocks, Elementor layouts, templates, widgets, media, and WooCommerce content. For code-backed sites, Frontman turns those requests into reviewable source changes.

For JavaScript frameworks, navigate to localhost/frontman in your browser. For WordPress, open your site's /frontman route. In both cases you get a chat interface alongside a live preview of what the agent is working on.

For JavaScript frameworks (Next.js, Astro, Vite), Frontman runs in development only — never in production. Every change produces a standard code diff that goes through your team's normal review process. Nothing gets merged without an engineer approving it.

Frontman supports Next.js, Astro, Vite, and WordPress. For JavaScript frameworks it integrates as middleware, turning your local dev server into an MCP server. For WordPress it installs as a plugin that exposes WordPress-specific tools for posts, pages, blocks, Elementor content, menus, templates, widgets, settings, and WooCommerce when active.

Yes. Frontman for WordPress installs from the WordPress Plugin Directory and opens at /frontman on your site. It lets administrators edit posts, pages, Gutenberg blocks, Elementor pages, menus, templates, widgets, settings, cache, and WooCommerce data beside live preview. See /wordpress/ for the product overview and /docs/integrations/wordpress/ for setup.

Frontman gets context from the runtime it is installed into. For JavaScript frameworks, it hooks into your local dev server and browser tools. For WordPress, the plugin exposes WordPress-native content, template, menu, widget, option, Elementor, and WooCommerce tools directly from the running site. In both cases, the agent queries live runtime context instead of relying only on static files.

Yes — unlike the JavaScript framework integrations which are development-only, the WordPress plugin can run on a live site. WordPress sites are often edited directly in production, and the plugin respects that workflow. That said, this is experimental software. Use it with care: start on a staging site, keep backups, and review changes before relying on it in production.