# Frontman

> Ship updates to your existing WordPress site faster with Frontman's AI editor. Describe one update, inspect the page, and refine the result. Next.js, Astro, and Vite use a separate development and source-review workflow.

## WordPress

Install [Frontman from the WordPress Plugin Directory](https://wordpress.org/plugins/frontman-agentic-ai-editor/), activate it, and open Frontman from the WordPress admin menu. Requires WordPress 6.0+, PHP 7.4+, administrator access, Frontman sign-in, service access, and your own supported AI provider with separate costs. Frontman for WordPress is production-ready. Start with staging and backups. WordPress-native writes persist to the connected installation; published content on a live site can change immediately. Preview is not a universal approval gate.

- [WordPress homepage](https://frontman.sh/)
- [WordPress setup guide](https://frontman.sh/docs/integrations/wordpress/)
- [Framework workflow and installation](https://frontman.sh/frameworks/)

The following sections describe the framework workflow.

## What problem does Frontman solve?

Known website updates still need implementation: builder controls, file hunting, or handoffs. Frontman brings the request and rendered page into one editing loop. Inspect the result and refine it; visual context does not guarantee correctness.

## Who is Frontman for?

- **Designers** who want to make spacing, typography, color, and layout changes directly in the running app without opening an IDE or filing a ticket. Source changes still need developer review, tests, and deployment.
- **Product managers** who need to update copy, tweak structure, or explore feature ideas without waiting for an engineering sprint. Frontman gives non-technical teammates a chat interface alongside a live view of the app.
- **Frontend developers** who want faster iteration with richer context than terminal-based AI tools provide. Click an element, describe the change, see it happen — instead of writing prompts that specify file paths and line numbers.
- **Teams** that want to collapse the gap between "people who can describe a change" and "people who can make a change" — while keeping the entire engineering review process intact.

## How it works

Framework integrations require a running supported development project and permitted workspace access. They expose source and dev-server context alongside browser tools for DOM, styles, and selection. A hosted or self-hosted Frontman server orchestrates tasks and sends relevant context to the selected AI provider. WordPress uses native CMS tools, not the framework filesystem tools.

Frontman is intended for development workflows. RuntimeEnv disables the integration outside development by default, with explicit enable overrides. This is a runtime guard, not automatic build stripping. Check the configuration, built artifact, and deployed `/frontman` route when Frontman must be absent. Source changes use your team's normal Git review, tests, and deployment process.

## Key capabilities

- **Browser-aware editing** — sees the live DOM, computed styles, and component tree; traces elements to source files
- **Multi-select** — Shift-click multiple elements, add instructions to each, fix them all in one pass
- **Framework integrations** — Next.js, Astro, and Vite (React, Vue, Svelte) with deep runtime context
- **Bring your own AI** — Anthropic and OpenAI OAuth connections; supported saved keys for Anthropic, OpenRouter, Fireworks AI, and NVIDIA. See provider setup docs for current access.
- **Built-in Lighthouse audits** — run performance and accessibility audits without leaving the browser
- **Source-available** — package-specific licenses. Try Frontman free: five uses, no card. AI-provider costs are separate. See [pricing](https://frontman.sh/pricing/).

## Docs

- [Homepage](https://frontman.sh/): WordPress product overview and plugin installation
- [For frameworks](https://frontman.sh/frameworks/): Next.js, Astro, and Vite overview, feature highlights, and installation instructions
- [Markdown homepage](https://frontman.sh/index.md): Canonical markdown summary for agents
- [Pricing Markdown](https://frontman.sh/pricing.md): Trial, subscription terms, and separate provider costs
- [Authentication Markdown](https://frontman.sh/auth.md): Public reads versus authenticated product access
- [Framework Markdown](https://frontman.sh/frameworks.md): Framework setup and development workflow
- [FAQ](https://frontman.sh/faq/): Answers to common questions about features, frameworks, safety, and technical details
- [Developer docs](https://frontman.sh/docs/): Installation, authentication, integrations, usage, and reference guides
- [API keys and providers](https://frontman.sh/docs/api-keys/): Bring-your-own-key authentication docs for Claude, ChatGPT, and OpenRouter
- [API catalog](https://frontman.sh/.well-known/api-catalog): RFC 9727 catalog of public read-only resources, not an editing API
- [OpenAPI description](https://frontman.sh/openapi.json): Documentation index and latest framework adapter versions; no credentials required
- [Agentic resources](https://frontman.sh/.well-known/ard.json): ARD proposal listing published skills and the public API description
- [Agent skills index](https://frontman.sh/.well-known/agent-skills/index.json): Official Frontman skill-md artifacts
- [Frontman Agent Plugin](https://frontman.sh/plugin.json): Official skills package; plugin root in the source repository is apps/marketing/public
- [AI Catalog](https://frontman.sh/.well-known/ai-catalog.json): Same public resources as ARD, with publisher identity and unsigned source provenance
- [Frontman API catalog Markdown](https://frontman.sh/.well-known/api-catalog.md): Public read-only API endpoints and access requirements
- [Frontman changelog Markdown](https://frontman.sh/changelog.md): Maintained release notes
- [Docs llms.txt](https://frontman.sh/docs/llms.txt): Scoped docs context
- [API llms.txt](https://frontman.sh/api/llms.txt): Scoped API context
- [Developers llms.txt](https://frontman.sh/developers/llms.txt): Scoped developer context
- [Changelog](https://frontman.sh/changelog/): Release notes and version history
- [GitHub](https://github.com/frontman-ai/frontman): Source code, contributing guide, and issue tracker

## Blog

- [Introducing Frontman](https://frontman.sh/blog/introducing-frontman/): Origin story and core vision — why we built a browser-based AI agent
- [Getting Started](https://frontman.sh/blog/getting-started/): Installation and first-edit walkthrough
- [Why AI Coding Agents Are Blind to Your UI](https://frontman.sh/blog/ai-coding-agents-blind-to-ui/): The perception gap in file-level agents and how runtime context fixes it
- [Frontman vs Cursor vs Claude Code](https://frontman.sh/blog/frontman-vs-cursor-vs-claude-code/): When to use file-level agents vs. browser-level agents
- [Multi-Select Editing](https://frontman.sh/blog/multi-select/): Batch multiple UI fixes into a single operation
- [The Runtime Context Gap](https://frontman.sh/blog/runtime-context-gap/): How live DOM, computed styles, and component tree improve AI code generation
- [Lighthouse Audits Without Leaving the Browser](https://frontman.sh/blog/lighthouse-audits-without-leaving-the-browser/): Built-in performance and accessibility auditing
- [Security Model](https://frontman.sh/blog/security/): Development boundaries, encrypted API keys, reviewable diffs, and limitations
- [Team Collaboration](https://frontman.sh/blog/team-collaboration/): How designers and PMs use Frontman alongside developers

## Comparisons

- [Frontman vs Cursor](https://frontman.sh/vs/cursor/): Browser-based visual editing vs. IDE-based file-level AI
- [Frontman vs GitHub Copilot](https://frontman.sh/vs/copilot/): Runtime-aware agent vs. inline code completion
- [Frontman vs Stagewise](https://frontman.sh/vs/stagewise/): Feature-by-feature comparison of browser-based AI tools
- [Frontman vs v0](https://frontman.sh/vs/v0/): Editing existing production apps vs. generating new UIs from scratch

## Optional

- [Browser-Aware AI Tools in 2026](https://frontman.sh/blog/browser-aware-ai-tools-2026/): Industry landscape and where browser-based AI coding is headed
- [Add Runtime Context to Your AI Workflow (Next.js)](https://frontman.sh/blog/tutorial-nextjs-runtime-context/): Tutorial on enriching AI agents with live application context