PHPackages elcreator/aimage - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. elcreator/aimage ActiveEvolutioncms-plugin elcreator/aimage ================ AIMage — an AI image workbench for the Evolution CMS manager: describe a batch of image work in text or by voice, let a text model plan it, and let a cross-server worker carry it out against ai.artur.work while you are away. 00PHPCI passing Since Aug 25Pushed todayCompare [ Source](https://github.com/elcreator/aIMage)[ Packagist](https://packagist.org/packages/elcreator/aimage)[ RSS](/packages/elcreator-aimage/feed)WikiDiscussions main Synced today READMEChangelog (1)DependenciesVersions (1)Used By (0) AIMage ====== [](#aimage) An AI image workbench for the **Evolution CMS 3.5+** manager. Describe a batch of image work; it runs in the background. A text model asks about anything genuinely ambiguous, plans the work, and a background worker carries it out against the [ai.artur.work](https://ai.artur.work/profile) gateway, a slice at a time, for as long as it takes. The result of a job is always **changed image files**. Text, voice and previews are intermediate; a job that ends in a nice paragraph has failed at its purpose. --- What it does ------------ [](#what-it-does) - **"Upscale everything in `products/`"** — lists what you may actually see, queues one step per image, runs them. - **"Generate 10 hero images of a mountain lake at dawn"** — queues the generation, writes the results into a folder you may write to. - **"Make the backgrounds transparent"** — queues an edit per image; originals are never overwritten. - Anything ambiguous enough to change the output — which files, what style, how many — gets a question instead of a guess. Before you commit, the model picker shows **what it will cost and how long it will take**, with the provenance of both: a fixed tariff reads differently from a median of past runs, and a seeded latency prior is labelled an estimate rather than dressed up as a measurement. Requirements ------------ [](#requirements) - Evolution CMS **3.5.2+** with the system task registry (`EvolutionCMS\Services\SystemTasks\SystemTaskRegistry`) - PHP 8.3+ - A running scheduler — `php core/artisan schedule:work`, or cron calling `schedule:run` every minute. Without it batches queue and never start; the page says so rather than pretending. - An ai.artur.work API key, per manager or site-wide Install ------- [](#install) ``` cd core php artisan package:installrequire elcreator/aimage "*" php artisan migrate ``` Then open **AIMage** in the manager's Modules menu. Keys ---- [](#keys) Three tiers, in order: 1. **The manager's own key** — set on the page, stored encrypted in `user_settings`. 2. **The site-wide key** — `AIMAGE_API_KEY` in the environment, or a settings row an administrator sets. Configuration wins over the row. 3. **Nothing** — the page asks for a key instead of failing. Keys are encrypted at rest with AES-256-GCM (`Support\Crypt`), because Evolution CMS registers no Laravel encrypter and a database dump is a routine artefact. The secret comes from `AIMAGE_SECRET`, or from a generated `core/custom/aimage.secret` — never from the database beside the ciphertext. A stored key is never sent back to the browser in full. Permissions ----------- [](#permissions) Two separate questions, and neither substitutes for the other: - **`aimage`** — may this manager use the workbench at all. - **File groups** — which images they may touch, decided by the CMS's own `file_groups` table exactly as in the file manager, inherited down the folder tree. A manager confined to a folder by `filemanager_path` stays confined here. The worker has no session, so `Support\ImageScope` rebuilds the same facts from the database for a given user id and then defers to the core's own `FileManagerAccess` for every verdict — it is not a second permission model. Configuration ------------- [](#configuration) `config/aIMage.php`, overridable from `core/custom/config/cms/settings.php`. The values worth knowing: KeyDefaultMeaning`limits.slice_seconds``45`How much of each worker minute a batch may own`limits.parallelism``3`Batches in flight at once, across all managers`limits.max_images_per_job``200`Hard ceiling, whatever the plan says`limits.approval_threshold_eur``5.0`Above this, a plan waits for a signature`files.output_folder``aimage`Where results land, relative to the file root`files.allow_overwrite``false`Off means results are written beside originalsSecrets belong in the environment, never in this file. Design notes ------------ [](#design-notes) See [`AGENTS.md`](AGENTS.md) for the full picture. The three things most likely to be misunderstood: 1. **The dialect is chosen by model family, never by preference.** The gateway serves every model on both `/chat/completions` and `/messages`, but its translation drops tool calls in both directions. The planner is a tool-calling loop, so `claude-*` goes to `/messages` and everything else to `/chat/completions`. 2. **A model with `variants` must be priced per variant.** Quoting `price.amount` for `gpt-image-1` quotes the dearest tier — a 22.7× error against the cheapest. 3. **The model plans; the worker acts.** No tool the planner can call touches an image model. That is what makes a plan priceable before anything is spent, and what lets execution survive the conversation ending. Known limits ------------ [](#known-limits) - **Upscaling needs a publicly reachable URL.** `/images/upscale` takes `imageUrl`, not an upload, so a site on localhost or behind HTTP auth cannot upscale. The step fails with `NOT_PUBLICLY_REACHABLE` rather than timing out. - **Translations are machine-produced.** Every language Evolution CMS core carries is present — but none has been reviewed by a native speaker. Licence ------- [](#licence) GPL-3.0-or-later. ### Health Score 20 ↑ LowBetter than 12% of packages Maintenance65 Regular maintenance activity Popularity0 Limited adoption so far Community6 Small or concentrated contributor base Maturity11 Early-stage or recently created project Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Community Maintainers ![](https://www.gravatar.com/avatar/4d36fa562f4887de196822681d345f451099c93dddef44546230176f1df051a8?d=identicon)[artur.work](/maintainers/artur.work) --- Top Contributors [![elcreator](https://avatars.githubusercontent.com/u/974975?v=4)](https://github.com/elcreator "elcreator (6 commits)") ### Embed Badge ![Health badge](/badges/elcreator-aimage/health.svg) ``` [![Health](https://phpackages.com/badges/elcreator-aimage/health.svg)](https://phpackages.com/packages/elcreator-aimage) ``` PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)