Media AI
Media AI adds a Doctor action on media-library images once a provider is configured.
What Media AI helps you do
This private package is outside the Released and Beta channels, so no public install path is available.
Workflow screenshots
6 capturesMedia AI adds a Doctor action on media-library images once a provider is configured.
Editors can improve images, remove backgrounds or objects, restore, or upscale, then keep edited output as a new media item.
Successful runs can also write localized alt text and captions while the original file stays untouched.
The action stays hidden until a provider is configured, so AI is never a silent dependency.
Use it when media workflows need explicit, editor-triggered AI help.
What changes on your site
Review the admin, public, data, scheduled, and command surfaces Media AI adds when enabled.
- Media
- Assistant
- Image Doctor
- Background Removal
Install after you have checked the fit.
Confirm version compatibility, support, data access, migrations, retained data, and removal steps first. Then install the Composer package from the account that owns access.
-
01
Require the package
composer require capell-app/media-ai -
02
Register the extension
php artisan capell:extension:enable media-ai -
03
Clear schema cache
php artisan capell:admin:clear-schemas-cache
Evaluator scenarios
What to inspect in Media AI
Switch the evaluation lens to see how different roles should assess this package before installing it.
Test Media AI with a site owner
Request help on one image and reject the proposed wording. The library should retain the original text, proving that the assistant cannot publish changes autonomously.
Read more Show less
Expected evidence: It runs per image when an editor chooses to, and proposes candidate alt text or a variant rather than changing their library on its own. Site owners get the time back on the tedious part while keeping the final say over the brand.
Choose a lighter option when: It's no substitute for real brand or legal review of what goes public. If site owners would rather keep image work fully hands-on, manual production suits site owners better than any assist here.
Release and download evidence
- Total downloads
- 0
- Last downloaded
- No downloads yet
Version history
0 releasesNo package release history is published yet. Check the source and documentation before installing.
Before checkout
Know who owns access and what happens next
Payment, customer account ownership, site activation, and package access are separate steps. The checkout reference lets support trace a problem without moving the licence to another account.
Who processes the payment and taxes?
Lemon Squeezy hosts paid marketplace checkout and issues the tax receipt. Capell does not collect card details; it activates the matching marketplace licence after payment is confirmed.
Which account owns the licence?
The signed-in customer account that completes checkout owns the licence, receipt, support history, and future install access. Use the intended organisation account before paying.
How does the site receive package access?
The install flow connects the licence to the requesting site. Paid and private packages then use authenticated Composer access from the customer account that owns the licence.
What happens if checkout is cancelled or expires?
No licence is created until Lemon Squeezy confirms payment. After a cancellation or expired quote, return to the same marketplace listing and start a fresh checkout so price and package details are recalculated.
What should I do if access does not appear?
Keep the checkout reference from the page or receipt and contact support before trying another account. Support can trace the payment, customer account, licence, and connected site from that reference.
No approved reviews yet. Reviews from eligible customers appear here after moderation.
