Emet can call an LLM on your behalf while you write: to tighten a paragraph, draft a page, translate an entry, generate an image or just answer “what did I publish in May?”. It’s all optional. There’s nothing AI-related in the interface until you add an ai: block to admin/cms.yaml, and even then nothing happens until a provider has a key (or, for a local model, an endpoint).
A few things worth knowing before you turn it on:
- Emet talks to the provider straight from your browser. There’s no proxy in between, so your API key goes to OpenAI, Anthropic or Google and nowhere else, but it also means the key has to live in your browser (or in the repository, if you set a site-wide one).
- Everything the AI does lands in the editor as an ordinary edit. Save, and it’s committed like anything else you typed. Nothing is published behind your back, but nothing is checked either, so read what it wrote before you sync to production.
- Every prompt includes the entry you have open and, if you’ve set one, your site’s brand voice. The model knows what it’s editing.
What’s here#
- Providers covers the
ai:config, API keys, model selection and the Gemini key types. - AI chat is the panel in the editor’s right column, with tools that can edit the entry, search your content and more.
- Inline actions are the one-click rewrites on selected text: improve, expand, summarise and so on, plus your own custom actions.
- Page builder drafts a whole entry, frontmatter and all, from a description.
- Image generation makes images with OpenAI or Gemini and uploads them to your media folder.
- Translation translates a selection or a whole entry into another configured language.