Frontman helps WordPress site owners, marketers, and designers update real websites without rebuilding, digging through admin screens, or waiting on developer tickets.
Individual engineers, not company endorsements.
Frontman is an AI website editor for existing WordPress, Next.js, Astro, and Vite sites. It runs inside WordPress as a plugin or inside your framework dev server as middleware, sees the live page, CMS or component context, CSS styles, routes, and logs, then turns visual requests into reviewable site updates. Open-source core with BYOK model support.
Choose your path
Frontman keeps one promise across both workflows: update the site you already have from the page you can see.
WordPress site owners
Update posts, pages, Gutenberg blocks, Elementor layouts, menus, media, settings, and WooCommerce data without hunting through wp-admin.
Install WordPress plugin →Marketing and design teams
Use Frontman on Next.js, Astro, and Vite sites so marketers and designers can click the page, request changes, and hand developers a normal diff.
See team workflow →Frontman is an AI website editor for existing sites. It runs inside WordPress or your framework dev server, reads the live page plus CMS or source context, then turns visual requests into reviewable website updates.
Website requests usually start with screenshots and vague descriptions. Frontman starts from the page itself: selected elements, computed styles, source mappings, routes, logs, and live preview feedback. That context helps the agent change the right thing with less back-and-forth.
const theme = primary: "#A259FF", radius: "8px", No more pixel-pushing in code you didn't write. Frontman understands your components, your design tokens, and your layout conventions — so every edit stays on-brand.
Spot a misaligned element? A color that feels off? Point at it, describe what you see, and Frontman refines the source to match your vision. No redlines, no handoff gaps, no compromises.
Select a component directly in your browser — a button, a card, an entire section. Describe the change in plain English. No file hunting, no line numbers, no IDE.
Pro tip: use the up and down arrows to move between components and divs
No more alt-tabbing between editor and browser. Frontman updates your code as you describe changes — and you see the results live, instantly. When you're happy, commit and push to Git without ever leaving your browser.
Everything you need to build faster, smarter, and with more confidence.
Inspects the real DOM, CSS styles, and component boundaries — the full runtime context that file-level agents miss.
Switch between device presets — iPhone, iPad, desktop — and see how your changes look at every breakpoint.
Reads build output, console warnings, and stack traces. Spots compilation errors and fixes them automatically.
Open-source core with BYOK model support. Use your API key from Anthropic, OpenAI, or OpenRouter for local development.
Reads agents.md, claude.md, or custom rule files at session start. Your conventions baked into every prompt.
Works with Next.js, Astro, Vite, and WordPress. Modern apps or CMS sites — your stack, your rules.
Framework middleware for modern apps. Plugin-native editing for WordPress sites.
The only AI coding tool with direct access to your running application
| Feature | Frontman | Claude Desktop | Cursor | Copilot |
|---|---|---|---|---|
| Sees live DOM & styles | ||||
| Edits code in-place | ||||
| Designer/PM friendly | ||||
| Framework-aware | ||||
| Open source | ||||
| Works in the browser | ||||
| Visual component selection |
Comparing AI tools for UI work? Read the frontend coding agent guide for Cursor, GitHub Copilot, Claude Code, v0, Bolt.new, Kombai, Stagewise, and Frontman.
One command to install, one URL to open, one AI to connect. That's it.
Run one command in your project folder
npx @frontman-ai/nextjs install Visit localhost/frontman in your browser
http://localhost:3000/frontman Connect to your preferred AI model subscription
FAQ
Everything you need to know about Frontman — the AI agent that lives inside your app.
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.
Your AI finally sees what you see. Click an element, describe what you want, and watch it happen — no more alt-tabbing, no more hallucinated layouts, no more broken diffs.
