AI
VilaAI / AirPilot Gap Brief
Source-backed snapshot - 2026-06-06

VilaAI owns the WHMCS operator layer.

The short version: AirPilot is ahead as a SaaS platform, but VilaAI still has several WHMCS-native support operations that AirPilot and the LibCyberAI variant do not have. The newest differences are promo redemption tools, refund/chargeback guardrails, GPT-5 transport tuning, Telegram reply-safety, and a WHMCS chat-session viewer.

VilaAI: panel-native support ops AirPilot: SaaS + portal + connectors LibCyberAI: libcyber-only worktree Focus: things missing from AirPilot

Coverage Snapshot

VilaAI is not bigger everywhere. It is specifically denser in WHMCS-native support operations and recent safety workflows.

29
VilaAI model tools registered in the WHMCS module.
27
AirPilot WHMCS-visible tools in the connector and SaaS registry.
18
LibCyberAI tools, focused on libcyber and not WHMCS.
6
High-signal VilaAI areas missing or not equivalent in AirPilot today.

What VilaAI Has

Use the filters to separate recent additions from durable product gaps. The LibCyberAI worktree is included where the gap matters.

Recent

Retroactive promo redemption tools

VilaAI added a two-step promotion recovery workflow: evaluate first, then apply with an idempotency key and a ledger.

  • Tools: evaluate_promo_redemption and apply_promo_redemption.
  • AirPilot WHMCS has normal promo-code validation, but not retroactive redemption.
  • LibCyberAI has coupon validation for libcyber, not WHMCS invoice correction.
Recent

Refund and chargeback staged handling

VilaAI now routes refund pressure through a staged policy with a five-working-day review promise and suppresses retention offers in that path.

  • Prevents the model from mixing cancellation-save tactics with refund escalation.
  • No implemented AirPilot or LibCyberAI equivalent was found outside planning text.
  • This is prompt and orchestration behavior, not just documentation.
Recent

Telegram default-polish fail-safe

The current VilaAI worktree can polish Telegram replies by default, block unpolished sends on polish failure, and offer an explicit raw-send confirmation.

  • Includes /nopolish, pending raw-reply state, callback confirmation, and stale update retry handling.
  • AirPilot has manual Telegram polish commands, not a default outbound reply gate.
  • LibCyberAI inherits the narrower AirPilot-style Telegram behavior.
Recent

WHMCS chat-session conversation viewer

VilaAI's dirty worktree adds a Conversations tab over existing WHMCS chat logs, with sessionization, badges, raw-log fallback, and Telegram deep links.

  • AirPilot has a portal conversation product, but this is not the same as a WHMCS-native log viewer.
  • No schema change: it derives sessions from existing chat-log rows.
  • Telegram notifications can jump directly into the relevant WHMCS conversation.
Recent

GPT-5 xhigh and transport controls

VilaAI has per-context reasoning and verbosity settings plus custom-endpoint capability handling, SSE idle control, and official-endpoint xhigh clamping.

  • AirPilot docs still list GPT-5 Responses API tuning as a gap.
  • LibCyberAI supports BYOK/custom base URLs, but not this per-context transport stack.
  • This matters for long-running WHMCS ticket and chat generation.
Recent

Brand-specific VilaVPN knowledge updates

VilaAI's knowledge data was recently synced to newer app download URLs and platform-specific install lines, including a Fire TV APK line.

  • This is operational content, not a platform feature.
  • AirPilot and LibCyberAI are more generic and do not carry this VilaVPN support corpus by default.
  • It is still a real support-answer advantage in the current VilaAI deployment.
WHMCS

Panel-native admin and recovery UI

VilaAI owns the WHMCS admin experience: queue dashboard, tool-call logs, billing-correction pages, blacklist, chat logs, settings, and webhook state.

  • AirPilot has portal surfaces and a connector, but the WHMCS connector admin is much thinner.
  • LibCyberAI intentionally removed WHMCS and platform billing surfaces.
  • This is the largest day-to-day operator gap.
Support ops

Ticket and human-support operations

VilaAI has deeper WHMCS ticket automation and human-support queue behavior than the AirPilot WHMCS connector currently exposes.

  • Includes panel-local tables and admin flows for human support requests.
  • AirPilot's own parity docs call this out as a remaining VilaAI gap.
  • LibCyberAI has libcyber tickets, not WHMCS ticket operations.
Nuance

Do not count overdue compensation as missing

VilaAI registers compensate_overdue_invoice_time; AirPilot uses compensate_overdue_time. The handler behavior maps to the same business action.

  • The meaningful WHMCS tool-name gap is the promo redemption pair.
  • AirPilot has several things VilaAI lacks, including image intelligence and Studio.
  • This brief is not an overall product ranking.

Recent VilaAI Additions

These are the high-signal additions since May 2026 and the current dirty worktree changes that widen the gap.

2026-05-02

Refund handling staged with a review window

Prompt and orchestration changes isolate refund and chargeback pressure from retention-offer handling.

Missing in AirPilot implementation
2026-05-20

Retroactive promo redemption tools

VilaAI added evaluation, apply, rule-engine, ledger, manual checklist, and an explainer for post-purchase promotion recovery.

Direct tool gap
2026-05-24

Official OpenAI xhigh fallback clamp

VilaAI clamps unsupported xhigh reasoning to high on the official endpoint while preserving custom endpoint behavior.

Transport gap
2026-06-01

Support knowledge URL sync

The current VilaAI corpus was updated to newer platform download URLs and app-version support details.

Content advantage
2026-06-05/06

Telegram default polish and WHMCS conversation viewer

The active VilaAI worktree adds default-polish safety, retryable processed updates, pending raw-send confirmation, and chat-session viewing.

Current worktree gap

Tool Delta

The counts alone hide the key point: AirPilot WHMCS is close on classic billing/support tools, but misses the newest VilaAI promo-redemption pair.

Capability
VilaAI
AirPilot WHMCS
LibCyberAI
Why it matters
evaluate_promo_redemption
Yes
No
No
Safely calculates whether a customer should receive a retroactive promotion adjustment.
apply_promo_redemption
Yes
No
No
Applies the approved adjustment with an idempotent ledger instead of trusting a one-shot model answer.
validate_promotion_code
Yes
Yes
Coupon only
AirPilot can validate a WHMCS promotion code; LibCyberAI validates libcyber coupons.
billing correction workflow
Yes
Tool parity
No WHMCS
AirPilot has preview/start tools, but VilaAI has the deeper WHMCS-local admin and recovery surface.
overdue-time compensation
Yes
Yes
No WHMCS
Naming differs, but this is not a meaningful missing capability for AirPilot.
libcyber node/order/ticket tools
No
Yes
Yes
This is where AirPilot and LibCyberAI are ahead; it is outside VilaAI's WHMCS module scope.

Telegram Flow Difference

The newest VilaAI worktree is not just adding a command. It changes the outbound safety model for operator replies.

VilaAI current worktree

Admin reply /reply or callback Default polish if setting enabled Send polished normal path Polish failed do not silently send raw Pending raw confirmation Send as-is or cancel, expires after 2h

AirPilot / LibCyberAI today

Manual /polish operator chooses Show versions original or polished Copy/send manual path No default outbound polish gate found No pending raw-reply fail-safe equivalent in the inspected code

Evidence Trail

Repo-relative references from the local audit. This page is scrubbed for public hosting and omits sensitive operational details.

VilaAI implementation references

whmcsModules/vilaai/src/Services/AI/ToolManager.php - 29 registered tool names whmcsModules/vilaai/src/Services/AI/PromoRuleEngine.php - retroactive promo rule engine whmcsModules/vilaai/src/Services/AI/PromptRepository.php - staged refund and chargeback policy whmcsModules/vilaai/src/Infrastructure/OpenAIHttpClient.php - xhigh clamp, endpoint capability, SSE handling whmcsModules/vilaai/api/webhooks/telegram.php - current default-polish and processed-update changes whmcsModules/vilaai/src/Controllers/Admin/LogsController.php - current Conversations view changes

AirPilot and LibCyberAI references

AirPilot/docs/tool-current-state.md - 53 registry tools, 27 WHMCS-visible tools AirPilot/docs/vilaai-parity-gap-analysis.md - support-ops parity gaps called out by AirPilot docs AirPilot/whmcs-airpilot/src/Tools/ToolDispatcher.php - WHMCS connector tool dispatch whmcsModules/airpilot/src/Tools/ToolDispatcher.php - standalone connector copy tool dispatch LibCyberAI/app/core/tools/definitions.py - libcyber-only tool registry LibCyberAI/README.md - single-tenant libcyber-only custom variant scope

Practical Takeaway

If the goal is to make AirPilot catch up with VilaAI's WHMCS operator depth, these are the next ports that matter.

1. Port the promo-redemption pair

Bring over the two-phase evaluation/apply model, rule engine, settings, ledger, and idempotency behavior. This is the cleanest concrete tool delta.

2. Add reply-safety semantics

Default-polish should be a real outbound gate with retryable update processing, raw-send confirmation, and explicit bypass commands.

3. Separate platform wins

Keep AirPilot's strengths, including portal conversations, Studio, image intelligence, multi-tenant BYOK, and the LibCyberAI custom scope. The gap is WHMCS operator parity, not overall capability.