Omega separates website planning from website production. The system uses Omega’s native deterministic planning engine and canonical knowledge for constrained structured strategy, validates planning data and preserves explicit customer choices and source evidence as authoritative inputs.
Omega AI Agent • your floating assistant in both dedicated editors
Click the floating Omega AI chat control at the bottom right while working in either the Pure HTML Website Editor (website-editor.php) or WordPress Website Editor (website-editor-wordpress.php). Omega's assistant uses its native knowledge and planning resources and, where available, its OVHcloud inference/engineering services. Both editors retain their own site-specific editing and publishing controls; opening the chat does not give it authority to publish changes.
Ask for current web standards, accessible design, SEO, responsive image guidance and website security references. Omega can research public pages and provide relevant source links, with safeguards against unsupported claims. Its research workflow uses Omega's self-hosted search and public-page retrieval rather than requiring customers to purchase a search API account.
Discuss website questions using Omega's own planning, knowledge retrieval, semantic and lexical language resources. The assistant can combine customer-supplied information with relevant Omega documentation and distinguish confirmed facts from assumptions; it is not a substitute for the website's deterministic validation controls.
Explain a project in natural language or provide supported text, source files and project ZIP evidence where the Agent offers uploads. It can organise relevant organisations, brands, content, pages, domains, requirements and code into a grounded project specification while flagging missing information instead of inventing facts.
Plan the same six Builder stages—Business, Pages, Design, Content, Media and Advanced. Ask for structure, wording, design directions, responsive assets, SEO/schema and accessibility guidance, then use Apply to Builder for a qualifying structured proposal. The customer reviews and controls all Builder inputs before Generate.
Ask about the Builder's 16 planning/production engine responsibilities, Pure HTML versus native WordPress output, or the eight Omega hosted plugin families with their 16 platform-specific implementations. The Agent can explain compatible WordPress plugins and Pure HTML modules, their security boundaries and performance/media capabilities; an explanation never installs a plugin automatically.
Request responsive HTML/CSS/JavaScript examples, explanations of supplied PHP or WordPress code, debugging help for errors/logs, safer revisions and reviewable diffs. It can help reason about page speed, security, schema, accessibility and browser compatibility without bypassing licensed-site validation.
In website-editor.php, the Agent can receive the current authorised file path, unsaved editing buffer, limited related-file context and validation details through the Editor bridge. Ask it to explain errors or propose file-specific and multi-file corrections to review and stage within the existing HTML code workflow.
In website-editor-wordpress.php, the floating Agent accompanies native WordPress Pages/Posts editing, WordPress-rendered preview where supported, the integrated WordPress Manager and the appropriate plugin panels. It can help investigate source and validation issues; any suggested database, theme or file edits still need the WordPress-specific authorised workflow.
Editor-only requests such as FIX MY VALIDATION ERRORS and APPLY ALL FIXES use the loaded authorised site context. Where a validated candidate is available, review the proposed files, explicitly choose Save All AI Fixes, then Validate Licensed Website and use the appropriate publishing control. The Agent cannot independently save or deploy a live customer website.
Ask about purchases, lifetime licences, subscriptions, invoices, checkout and your registered websites. Generic advice is available publicly; customer-specific facts require an authenticated, authorised Omega account session and are limited to appropriate account-safe information.
Get explanations of Omega Hosting, provisioning, DNS and SSL, deployment history, backups, restoration and site access. Any website-specific answer or operation remains subject to the customer's verified account, hosting entitlement and Website ID.
Ask about validation failures, missing hosting after payment, account activation, unavailable source, editor navigation, pending SSL or disconnected domains. The assistant can help establish safe diagnostic steps; it does not reveal secrets or override access controls.
Same assistant, two separate editing systems: The bottom-right Omega AI chat is available in both OVHcloud Editors, but Pure HTML and WordPress have different file/content models, previews, validation and publishing paths. Guest conversations and public research do not confer access to paid customer websites. NativeAI, web research, Builder tools and Editor repairs have separate entitlement and context requirements; actual availability depends on the authorised website and service state.
Role
This boundary is intentional: AI can add strategic reasoning without being allowed to overwrite the project's explicit requirements or directly own the deployment pipeline.
Production boundary
Current production order: AI Orchestrator → Entity Architecture → Website Specification → Site Architecture → Design System → Semantic HTML → Content + Conversion → SEO + Schema → Image → Performance → Security → Web Metrics Readiness → Accessibility → Forms + Backend → Deployment → Final Validation. Omega-native planning supplies structured, validated project state; it does not bypass the downstream production stages or Final Validation.
Before AI
Omega-native AI planning operates on the normalized project within the controlled Omega architecture.
Constrained request
That reduces the surface area for malformed or irrelevant AI output.
Plan validation
A successful API response is not the same as an acceptable site plan.
Resilience
Generation is controlled by Omega’s local architecture rather than an external AI provider.
After planning
The production renderer creates the actual files according to platform rules and the authoritative project specification.
Responsible use
AI can be inaccurate, incomplete, non-unique or unsuitable for a specific business or jurisdiction.
Omega Web Pro documentation
Start a Builder project and let AI assist the strategy while Omega retains control of validation, generation, preview, licensing and export.
OMEGA WEB PRO HOSTING
AI-assisted planning helps structure the website but does not receive hosting credentials, database passwords, SFTP credentials or private operational secrets.
Current production customer architecture
For a first-time Omega Hosting checkout, Omega saves the selected plan and pending website to one restricted checkout-bound customer account before payment, sends a secure one-time account-setup email, and requires the customer to set a password and sign in before continuing to the required purchase acknowledgements and secure Stripe Checkout. Paid Hosting and Editor entitlement remain locked until Stripe confirms payment. For a first-time Lifetime Licence purchase, an existing account is reused where available, or the customer account is created after Stripe confirms the purchase. My Account is the commercial identity, website, licence and billing centre; recurring hosting customers can use the Full Hosting Dashboard while entitled; lifetime customers retain their separate same-domain software rights.
Purchased websites, subscription/renewal state, lifetime licences, Pending Checkout, Purchase History, profile/security, Builder and Website Editor entry points.
Secure Stripe customer-portal access for the account's usable canonical production billing customer, including supported payment-recovery and subscription billing actions.
Entitled operational hosting controls for project workspaces, provisioning, deployment, backups, databases, SFTP and usage, with customer-facing DNS/SSL state surfaced through Omega interfaces.
ARCHITECTURE DISTINCTION
Omega AI Agent is the Omega-native project/account/developer intelligence layer that can analyse supported project material and prepare/apply a six-stage Builder draft. The customer reviews the Builder specification. Only after Generate does the established Builder pipeline proceed into its constrained Omega-native AI knowledge planning stage and Omega-controlled generation.
