AI-Assisted Editing Comes to Nibbly

Nibbly's admin dashboard now includes optional AI-assisted tools built for the same flat-file, no-database philosophy as the rest of the CMS. The goal is not to replace editorial control, but to make common content tasks faster while keeping credentials and generated assets under the site's control.

AI Tools in the Dashboard

Admins can use assistant chat, draft text, improve prompts, generate images, and work with image-to-image flows where the selected provider supports reference images. Generated images are saved locally and appear in the Media Library, so they can be reused like regular uploaded assets.

Server-Side Provider Gateway

All AI requests run through Nibbly's server-side gateway in includes/ai/ai-helper.php. Browser code talks to Nibbly, not directly to an AI provider. API keys stay server-side, feature flags decide which tools are available, and provider settings live in content/ai-settings.json.

The gateway supports OpenAI-compatible providers, OpenAI and OpenRouter presets, and optional local or private endpoints when explicitly enabled. Usage counters, approximate cost tracking, and audit logs are stored as flat files under content/.

Multilingual Help Where Editors Need It

When a site uses multilingual editor fields, Nibbly can show translation actions directly inside the field tabs. The active language becomes the source, the other language fields are filled inside the open dialog, and the editor still decides when to save.

Designed for Control

AI features can be disabled globally or per capability. If a feature has no provider, key, model, or quota available, the dashboard shows a controlled disabled state instead of failing in the background. This keeps AI useful for teams that want it without making it a hidden dependency for sites that do not.