Skip to main content
Capell home
Live demo

Find pages and prepare changes with AI

See the agent architecture Open the live demo

Capell is a Laravel CMS built on Filament. When installed through Composer, Agent Bridge supplies the AI Command Centre's typed, permission-aware commands for finding records, previewing changes, and activating registered packages already present in the application. Optional AI Creator and AIOrchestrator packages add provider-backed, schema-constrained site planning and private previews.

Human-readable targets Exact previews One-use confirmation
CMS capture: agent context AI context is assembled inside an explicit boundary. The real Agent Bridge screen shows where trusted package context is selected and prepared before an external agent receives it.
CMS capture · Content index Every page and its structure stay visible in the admin. The populated Pages index keeps page hierarchy, publish status, update time, page type, and PageSpeed state visible beneath its SEO overview.
Publishing Studio: review Move the draft through review. Reviewers approve, request changes or reject in the actual CMS interface, and approval notes are logged.

Real Capell product screens

Actual Agent Bridge prompt builder screen showing scoped package context and prompt controls inside Capell.

Find the page, check the change

Use AI-assisted requests for bounded work while keeping permissions and review in control.

AI is useful when it reduces the effort of finding the right page or preparing a change you can inspect. Capell's installed capabilities define what a request can do; the wording of a prompt does not grant extra authority. Evaluate the package scope and confirmation path before using it for consequential work.

Capell page editing form
The page form provides a concrete target to inspect before preparing or confirming a content change.

With Agent Bridge installed, the AI Command Centre interprets a bounded set of direct commands and, where no command shape matches, ranks the operations that could fit rather than guessing one. The shared capability catalogue resolves human-readable site, page, and package references, validates authority, presents an exact preview, and requires confirmation where the operation can change data or release state.

Optional AI Creator and AIOrchestrator packages add provider-backed, queued site generation. They constrain output to the live site schema and installed Capell choices, record the run, keep previews private, and refuse external scraping or close reproduction. Applying the validated plan uses the same one-use Agent Bridge confirmation path as other high-risk work.

What to verify

  • Autocomplete shows only capabilities the installation contributes.
  • Page and site records can be found by names, domains, slugs, and URLs without exposing internal identifiers.
  • Package activation is limited to registered code already present through Composer.
  • Preview is non-mutating and the matching confirmation can be used only once.
  • Public output contains approved content, never agent prompts, permissions, audit state, editor URLs, or model metadata.

Start with a bounded request

Ask for work whose target and outcome you can verify.

Begin with page lookup or a previewable content change. Identify the intended site, page and field, then inspect the resolved target before confirming a write. A natural-language request can be ambiguous even when it sounds clear to the person making it.

Agent Bridge and AI Creator are optional paid packages with different responsibilities. Review their current entries and installed capabilities; voice input is another input method, not a separate permission model. Keep the human decision where a change requires approval.

Keep the review meaningful

Check the content and the application boundary before publication.

An AI-assisted draft can still contain an incorrect offer, an unsupported claim or the wrong action destination. Review the actual proposed content and the public result before approving the change.

Respect the application's permissions and supported capability scope. AI Creator's private site-preview workflow is not permission to alter unrelated application behaviour. Keep secrets and sensitive customer information out of prompts unless the approved workflow explicitly supports them.

Adoption decision

Review the AI packages before adoption

Both packages are paid and currently preview-only. Use the live demo to inspect the public workflow first, then test the package path away from production. Keep a human responsible for provider terms, review, confirmation, and the final production release.

Stable
Maturity
Agent Bridge and AI Creator are Stable in the release catalogue, with preview-only access.
Paid access
Access
Both are paid packages; preview visibility means they are not current Marketplace install options.
Review first
Production
Pilot away from production and keep a person accountable for approval.
Live demo
Try it
Inspect the public command flow before choosing a package.

Stable maturity does not grant installation access. These packages remain preview-only; use the demo to assess the workflow and confirm availability before committing to it.

Interactive command flow

Try an example command

The same capability catalogue powers typed prompts, voice input, autocomplete, external agents, and package-contributed tools. Names, titles, slugs, domains, and URLs stay human-facing; internal identifiers remain inside Capell.

This is a public demonstration of the workflow. It is not connected to an admin account and cannot change a site.

AI Command Centre
Demonstration only

Autocomplete uses capabilities installed on the site.

Resolved operation

capell.pages.open_editor

Open an existing page

Target found by
Page title or URL
Authority
Current editor policy
Risk
Read
  1. Understand intent
  2. Resolve target
  3. Check authority
  4. Preview impact
  5. Confirm
  6. Audit
Exact preview

Open About in the page editor

No confirmation

Capell resolves one accessible page from its title and returns the admin destination only to the signed-in editor.

What would change
  • No content change
  • No public response change

Public output never receives the editor URL, record identifier, permissions, or field paths.

No operation runs from this public demonstration.

Architecture

How Capell checks an AI request

Start from the task. Capell discovers installed capabilities with their names, descriptions, intents, examples, schemas, risks, and confirmation requirements. The command interpreter can suggest a match, but the capability still resolves records and enforces policy for itself.

  4. Model

    Policy

    The current user, token scopes, package state, site access, and native publishing readiness are checked at execution time.

    See the capability boundary
  5. Model

    Confirmation

    Mutations bind an opaque, expiring, one-use token to the user, payload, capability, and reviewed preview. Persistent confirmation secrets are stored only as keyed hashes.

    See the capability boundary
  6. Model

    Audit

    Secret-scrubbed entries record previews, confirmations, rejections, and results without leaking them into the public site.

    See the capability boundary
Governed site generation

Generate a private site preview with AI Creator

Brief

Describe the organisation, purpose, audience, tone, required pages, and any abstract inspiration.

Generate

A queued provider call proposes original copy and structure using only installed Capell choices.

Validate

The site, theme, pages, sections, language, private visibility, and content rules must pass the live schema.

Review and apply

Inspect the private preview and exact impact, then confirm once or send the brief back for another draft.

What AI can and cannot change

Autocomplete is generated from installed, discoverable capabilities. Voice is only another input method. Preview remains non-mutating, confirmation expires after one use, policies are checked again at execution, and public HTML receives only approved render data.

Review the trust model
Targeting

Names and URLs, not exposed IDs

Suggestions

Installed capabilities only

Preview

Non-mutating by contract

Confirmation

Opaque, expiring, one use

Extensions

Composer-present packages only

Cloning

Owned internal content only

Generated sites

Original and private by default

Public output

No admin or agent metadata

Loading section

Next step

Start with page lookup and previews

Start with record lookup and previews. Add publishing, extensions, and AI Creator as each policy and workflow is ready.

The useful first test is simple: name a real page, ask Capell to open or change it, and inspect the resolved target and exact preview. Then trace the same operation through an external agent.

See the agent capability layer Open the live demo
Loading footer