1. Tell Omega AI what you need
Describe the website, organisation, project, problem or result you want in natural language. Continue with follow-up requests as the project develops.
Omega AI Agent is the intelligent project-understanding and website-specification layer of Omega Web Pro. Describe the website you need, provide existing source material or supported project files, and Omega AI can analyse the evidence, understand the organisation and its relationships, develop a structured six-stage website specification, and apply that specification to the Universal Builder for you to review before generation.
Use Omega AI Agent to understand the project and prepare the six-stage Builder for you, or enter every Builder setting manually. Either route leads into the same customer-controlled Omega Web Pro production system.
Describe the website, organisation, project, problem or result you want in natural language. Continue with follow-up requests as the project develops.
Use the + control to attach supported source files or ZIP project archives. ZIP project analysis supports the Agent's configured 256 MB analysis limit when server upload limits permit it.
The Agent builds an evidence-grounded understanding of what is being created and how the supplied information relates.
The project understanding is translated into the same structured six-stage model used by the Universal Builder.
Read the human-readable website architecture and recommendations. For qualifying Builder requests, Omega AI also prepares the machine-readable Builder draft.
Omega AI places the prepared specification into the corresponding Builder selectors, controls and input fields.
Inspect, correct or override the populated values, change selections, edit fields and refine the project. Your explicit Builder selections remain authoritative.
You can manually select and enter all information across Business, Pages, Design, Content, Media and Advanced instead of using an Agent-prepared specification.
The structured Builder brief enters the established production pipeline. Omega-native AI knowledge assists the compact planning stage when configured; Omega controls website generation and its production responsibilities.
The generated website proceeds through Omega's quality gates and responsive preview before the applicable customer-controlled purchase, export or deployment workflow.
Open the Universal Builder directly → manually complete Business → Pages → Design → Content → Media → Advanced → review your selections → select Generate. Omega AI is an optional project-intelligence and specification route, not a replacement for the Builder.
Customer-safe account profile, websites, domains, purchases/orders, lifetime licences, subscriptions, plans, hosting state, pending checkout and limited billing/invoice status when available to the signed-in account.
Generate website code as text, review and explain code, diagnose errors, repair HTML/CSS/JavaScript, assist with PHP and WordPress, and provide targeted or diff-style code help.
Builder, Website Editor, deployment, backups, DNS, SSL, database, SFTP/SSH, hosting and troubleshooting guidance within the customer's authorised Omega workflows.
Analyse supported files and ZIP projects, extract evidence, understand entities and relationships, distinguish first-party domains and preserve project provenance for grounded recommendations.
Eligible signed-in Omega Web Pro customers with Website Editor access can work directly with their licensed website source code, see changes in the sandboxed live preview, and use the integrated Omega AI Agent to diagnose and prepare validated code repairs. Omega AI can prepare the corrected code, but the customer remains in control of applying and saving it.
The Website Editor continues to inspect the current editor buffer and reports whether the current edit introduces new validation issues. Server-side validation remains in the save path rather than trusting generated code simply because it came from Omega AI.
Differential validation distinguishes the current edit from pre-existing project issues. Customers can use the authoritative licensed-website validation workflow to check the complete project after repairs have been applied and saved.
If the authoritative project content changes after a repair candidate was generated, Omega's stale-candidate protection prevents that older candidate from silently overwriting newer website content. Generate the repair again against the current project state.
Omega AI prepares and validates repair candidates. The customer explicitly chooses whether to apply them, reviews the resulting code and preview, and uses the Website Editor's normal Save control. Omega AI does not silently save or deploy the website.
Fix these issues in my website pages: [paste or describe the Omega validation errors here].
Omega AI uses the authorised Website Editor context, analyses the affected code, prepares the required single-file or site-wide repair candidate, validates the candidate, and returns the proposed correction. When a validated repair is available, you can choose APPLY FIXES TO ALL, inspect the changed website pages and sandboxed preview, then use the normal Save button. After saving, Validate Licensed Website can perform the authoritative full-project validation before an updated licensed ZIP is generated.
Omega AI Agent is an Omega-native PHP, JavaScript, JSON, knowledge and reasoning system designed to understand projects and translate that understanding into structured website requirements. It is distinct from the Builder's Omega-native AI knowledge planning stage.
Analyse a natural-language request, project requirements, existing website/source material and supported documents or files to establish what is actually being built.
Identify useful business information, first-party domains, products, services, contacts, social destinations, content and other project facts from supplied evidence.
Distinguish organisations, parent companies, brands, specialist products, software applications, services, publications and domains instead of treating every discovered item as an independent brand.
Establish how entities relate to one another, what belongs to which organisation, which domains are first-party, and how products, services and content should be represented.
Turn project understanding into the structured information required by Omega Web Pro's six-stage Universal Builder rather than relying on an uncontrolled one-shot prompt.
Create both a human-readable specification and a machine-readable Builder draft that can be applied to the real Builder controls for customer review and editing.
The Omega AI workflow is designed so customers do not have to manually translate every document, website, business relationship and project requirement into dozens of Builder controls themselves.
Tell Omega AI what website you need and provide relevant source material or supported project files.
Omega AI identifies the target organisation, facts, entities, domains, products, services and relationships.
Omega AI converts that understanding into a professional six-stage website specification.
The structured draft can populate the actual Universal Builder controls automatically.
You remain in control. Review, correct or override the populated settings before generation.
The Builder normalises the structured brief and uses Omega-native AI knowledge for its compact assisted planning stage when configured.
Omega controls the production pipeline across architecture, design, content, media, schema, SEO and deployment output.
The generated website passes Omega quality gates and final validation before responsive preview, purchase/export or deployment.
Website and brand identity, domain, industries, business description, market, language, currency, timezone, audience, goals and public contact information.
Page selection, site architecture and repeatable page-family requirements for the website being created.
Structured visual and presentation requirements that guide the site's design system and responsive output.
Content requirements, supplied source information and structured direction for customer-facing website copy.
Logos, images and project media used by the responsive production and image-processing workflow.
Additional website requirements and advanced instructions that belong in the structured production brief.
Omega AI prepares a draft specification—it does not silently take ownership of the project. You can review or change the populated Builder settings before selecting Generate.
Understands the project, source evidence, entities, account/site context and website requirements, then creates the structured Builder specification.
Omega-native AI knowledge is used separately by the Builder for a compact structured planning stage. It is not the Omega AI Agent and it does not control the production system.
Omega controls the actual website-production pipeline, including specification handling, architecture, design, content conversion, rendering, schema, responsive media, accessibility, SEO, deployment files and strict final validation.
Natural-language simplicity and project intelligence feed a structured Builder rather than bypassing it.
Once the reviewed Builder specification reaches generation, Omega's production pipeline coordinates the website as a complete system rather than as disconnected page fragments.
Structured page architecture, navigation, page rendering and output appropriate to the selected platform.
Design-system output together with responsive image production and project media handling.
Content conversion informed by the structured brief and the entity architecture established for the project.
Search-facing metadata and structured data generated as part of the controlled website-production workflow.
Production checks and output responsibilities covering accessibility and performance readiness.
Strict final validation and responsive preview provide a quality gate before the finished website proceeds to export or deployment.
Within authorised and authenticated contexts, Omega AI can assist with relevant Omega Web Pro account and website information rather than operating as an anonymous disconnected chatbot.
Access remains subject to authentication, customer ownership and the authority of the underlying Omega Web Pro systems. Omega AI does not silently purchase products or bypass the customer's review of a website specification.
Omega AI Agent combines project/source intelligence, Builder specification assistance, authenticated customer account intelligence, Omega Hosting guidance, authorised Website Editor context, support/troubleshooting knowledge and a read-only web-development coding assistant. It is designed to work inside Omega Web Pro's existing ownership, entitlement, validation and production controls rather than bypass them.
Use the Agent as a conversational Omega Web Pro assistant. Ask about a website project, your Builder specification, your signed-in account, purchases, licences, plans, hosting, deployment, Website Editor, code, errors or supported Omega workflows.
Omega AI can analyse the customer's request and available project evidence to identify the target organisation, purpose, audience, website requirements, products, services, domains, contacts, content and other facts relevant to the website being developed.
The Agent maintains bounded conversation/project context so a project can be developed through follow-up questions instead of treating every message as an unrelated one-shot prompt.
The Agent's + attachment control accepts up to three customer-safe attachments per request. Supported direct source formats are TXT, Markdown, HTML/HTM, CSS, JavaScript, JSON, PHP, XML, CSV, YAML/YML, SVG and WEBMANIFEST, and the Agent also accepts ZIP project archives containing supported text/code files.
ZIP projects can be analysed read-only up to the Agent's configured 256 MB analysis limit when the server's PHP upload limits permit it. The analyser indexes supported project files, prioritises likely first-party source material, bounds the amount of content used for reasoning and can inspect a large project without treating every generated or dependency file as authoritative source.
The project analyser rejects unsupported types, detects credential/secret-like content and skips private/dependency paths such as secrets, credentials, vendor, node_modules and cache material. Passwords, API keys, private keys and similar secrets should never be uploaded.
From supplied project material Omega AI can extract useful evidence such as organisations, brands, products, contacts, locations, languages, headings, URLs, domains, social destinations and structured JSON-LD/entity information.
The Agent separates likely business/first-party domains from external/reference services so an analytics provider, social network, CDN or other external destination is not automatically treated as part of the customer's own business architecture.
Omega AI can distinguish parent organisations, brands, products, specialist applications, services, publications and domains and preserve how those entities relate to one another when developing the website specification.
For website-building requests, Omega AI can develop a structured recommendation across Business, Pages, Design, Content, Media and Advanced, using the project evidence and the Builder's actual field model.
The Agent can explain the recommended website architecture and Builder choices in normal language so the customer can understand the proposed project before generation.
For qualifying Builder requests, the Agent can return a structured Builder payload. In the integrated Builder context, Apply to Builder transfers the draft into the real Builder controls.
Omega AI is optional. Customers can manually select and enter all of the website information themselves across the same six Builder stages without using an Agent-generated specification.
An Agent-prepared Builder payload is a draft. The customer can inspect, correct and change the populated values before selecting Generate. Explicit customer selections remain authoritative.
The Agent/Builder bridge does not silently press Generate and does not silently purchase a website, licence or hosting plan. Generation and commerce continue through the established customer-controlled Omega workflows.
When the customer is signed in, Omega AI can answer from customer-safe account context resolved from the authenticated Omega Web Pro session, including the account name where available, lifetime-licence count, websites in the account, active hosting-subscription count and pending-checkout count.
The Agent can list the websites/domains represented in the customer's Omega account together with their Website IDs where that information is available.
Omega AI can report customer-facing website status and available plan, provisioning and last-invoice status, and can identify account-level website records whose hosting, entitlement, provisioning or billing state may require attention.
The signed-in customer can ask what lifetime licences are present in the account. The Agent can use the customer-safe licence ID, associated domain, Website ID and licence status made available to it.
Omega AI can explain purchases represented in the account, including lifetime licences, hosting purchases and available order records, and can work with pending-checkout information where it is part of the authenticated account context.
The Agent can answer questions about the customer's available hosting subscriptions and plans, including customer-facing status and scheduled cancellation information where supplied by the account/hosting systems.
Omega AI can use the limited customer-safe billing state available to it to identify listed hosting sites whose last-invoice state or billing-recovery status may need attention. Complete invoice documents and payment-method management remain in My Account / Billing Centre.
The Agent understands the current Omega Web Pro checkout/account workflow, including restricted checkout-bound account setup, pending Website ID/purchase intent, account activation, authenticated continuation of checkout and Stripe-confirmed payment/entitlement.
Omega AI can guide customers through interrupted/pending checkout, account setup email and activation/recovery paths without telling them to create duplicate accounts or repeat a purchase simply to work around activation.
The Agent can explain hosting status, plan/status information, entitlement and provisioning concepts for the customer's owned sites using the customer-safe hosting context available to the authenticated account.
Omega AI can help explain domain connection, DNS and SSL workflows and troubleshoot customer-facing states such as a domain not connected or SSL still pending. It does not expose private credentials or unrestricted server configuration.
The Agent can explain deployment/publishing, live-site updates, deployment validation and where to find deeper deployment history in the authorised hosting tools.
Omega AI can explain backup and restore-point workflows and direct the customer to the Full Hosting Dashboard for the operational controls. It does not silently execute a restore.
The Agent can explain where the customer can access deeper database and SFTP/SSH information for an owned hosted Website ID. Passwords, private credentials and server secrets are not exposed through Omega AI.
Omega AI can direct customers to the Full Hosting Dashboard for deeper operational hosting information such as usage, health and other controls that are intentionally outside the Agent's customer-safe read-only context.
The Agent understands the Website Editor/Code Editor workflow, including questions about editor access, live-site updates, Builder preview versus Website Editor preview, validation failures and source-unavailable conditions.
When the Website Editor explicitly supplies context from an allowed Omega origin, Omega AI can receive the current authorised Website ID, file/editor context, unsaved buffer and bounded validation/revision/related-file information for assistance.
Editor and website context remains bound to the signed-in customer's owned/licensed website records. A browser-supplied Account ID or Website ID is not treated as proof of ownership.
The Agent includes dedicated developer assistance for generating responsive website components and sections and other web-development code as text.
Omega AI can review supplied code, explain it, diagnose errors/logs, repair HTML/CSS/JavaScript problems and provide targeted replacement code or requested code-change guidance.
The Agent can assist with PHP and WordPress-oriented code and with conversion questions between Pure HTML and WordPress implementations while keeping production execution in the appropriate Omega/customer workflow.
Use the coding assistant to review or improve responsive behaviour, accessibility and performance-related implementation issues in supplied or generated website code.
Omega AI's project and code intelligence can work with website semantics, SEO-facing content and structured JSON-LD/entity evidence when analysing a project or helping with code.
The interactive Agent includes a workflow for customers who want only the code changes presented as a diff rather than a broad rewrite or explanation.
The Agent uses the compiled Omega knowledge corpus together with intent routing, language handling, semantic expansion, local planning, state, provenance and critic/evaluation layers to route questions into the appropriate Omega workflow.
Source/project analysis keeps extracted evidence and provenance available to the reasoning pipeline so project-specific recommendations can be grounded in supplied material instead of being presented as invented facts.
The Agent itself is an Omega-native PHP/JavaScript/JSON/knowledge/reasoning system. It is separate from the Builder's Omega-native AI knowledge structured planning stage.
Omega AI can analyse, explain, recommend and generate suggested code, but it does not silently execute code, write customer files, deploy a website, restore a backup, change DNS, reveal passwords/private credentials, bypass validation, make purchases or bypass ownership and entitlement controls. Those operations remain in the authorised Builder, My Account, Website Editor and Full Hosting Dashboard workflows.
The current Agent builds this context from the existing authenticated Omega Web Pro session. It does not trust an Account ID or Website ID supplied by the browser as proof of ownership. Only customer-safe fields deliberately allowed by the account, commerce and hosting integrations are exposed to the Agent.
Where present: Account ID, login email, customer name, company, phone, address lines, city, region, postcode, country, account status, account-created date, profile-updated date, email-verification date and account-setup-completed date.
Licence ID, Website ID, licensed/normalised domain, platform, licence type, licence status, generation count, created/updated dates, purchase date and last-generated date where present.
Order ID, Website ID, Licence ID, domain, platform, plan code/name, order status, payment status, amount, currency, created date, paid date and fulfilled date where available.
The same customer-safe order fields can be used for pending orders associated with the authenticated account, allowing Omega AI to identify pending checkout context without creating a second account or duplicate purchase.
Website ID, domain, platform, plan code/name/display name, customer-facing status, entitlement, provisioning status, hosting status, SSL status, DNS status, current-period end, scheduled cancellation, created/activated/updated/deployed dates and last-deployed date where supplied.
Customer-safe subscription/site records plus hosting site count, active-subscription count, billing-recovery-required state and hosting-access-allowed state. Operational OVH hosting state can be reconciled with the commercial/account view through the service-authenticated control-plane context.
Where confirmed payment evidence exists, the Agent can receive limited invoice history containing invoice number, event type, status, total, amount paid, tax, currency and event date/time, plus last-invoice status/number/total/tax/currency. Complete invoice documents and payment-method management remain in Billing Centre.
Omega AI can compare available hosting status, entitlement, provisioning and last-invoice status to identify account-level websites that may need attention, while directing deeper operational diagnosis to the Full Hosting Dashboard.
No passwords, payment-card data, Stripe secrets, private keys, server secrets, unrestricted credentials or write credentials are part of the Agent's customer context. The Agent is read-only and cannot use account context to bypass ownership or entitlement controls.
The current architecture combines multiple internal capabilities before returning a response, while exposing no external AI provider for the Agent response path.
Classifies requests and recognises relevant Omega concepts/intents including Builder, account, checkout, hosting, editor, deployment, coding and troubleshooting work.
Normalises customer phrasing, maps related Omega terminology and expands retrieval concepts so different wording can still reach the appropriate current platform knowledge.
Uses recent conversation history and extracted project state to preserve bounded continuity across follow-up requests.
Decomposes complex work into bounded steps. Builder work can be planned across source assimilation, business/audience/goals, all six Builder stages and final SEO/schema/accessibility/performance/security consistency checks.
Searches the compiled Omega knowledge corpus using intent-aware and general retrieval, then combines strong current evidence rather than relying on a single literal keyword match.
Depending on the request, the Agent can combine knowledge search, source assimilation, Builder Advisor, authenticated account context, customer-safe hosting context, authorised editor context and verification.
A critic layer checks the composed answer for grounding, completeness, sensitive-data boundaries and over-certainty signals.
The Agent can retain provenance information for selected Omega knowledge evidence and separately identify authenticated-account, hosting, editor and customer-supplied project-source context.
The current response identifies the engine as omega-internal-v13.4-native, the architecture as Omega-native and external_ai: false. This is separate from Omega-native AI knowledge planning later in the Universal Builder generation pipeline.
Open the Universal Builder and enter/select the project information yourself through Business → Pages → Design → Content → Media → Advanced. You can use the complete Builder without asking Omega AI to prepare anything.
Describe the project and optionally attach supported source/project files with the Agent's + control. Omega AI analyses the available evidence, develops the structured six-stage specification and can apply the draft to the Builder. You then review and change anything you want before Generate.
Omega AI's machine-readable output is applied as a Builder draft. The customer gets the opportunity to inspect and alter it before Generate.
Account, website, hosting and editor assistance is constrained by the authenticated customer's available context and entitlements.
Explicit customer choices remain authoritative. Omega AI assists with understanding and specification; it does not silently replace the customer's decisions.
Open Omega AI Agent when you want the system to understand your project and prepare the Builder specification, or open the Universal Builder and configure the six stages directly.
For a signed-in customer working in an owned/licensed website, Omega AI can use the authorised Website Editor context supplied by the Editor—including the Website ID, current file/editor context, unsaved source buffer and bounded validation, revision and related-file information—to understand the code or error the customer is actually working on.
Work inside the authorised Code Editor for a website that belongs to the signed-in customer account.
Ask about the current HTML, CSS, JavaScript, PHP or WordPress code, a validation failure, console/error message, responsive problem or requested code change.
Omega AI can reason from the Editor context supplied for the owned website, including the current unsaved buffer and bounded validation/revision information.
Omega AI can produce Pure HTML, CSS, JavaScript, PHP and WordPress-oriented code as text, explain the problem and provide corrected, replacement or diff-style code.
The customer copies the generated or corrected code and pastes it into the Website Editor / Code Editor. Omega AI does not silently write the customer file.
The normal Website Editor validation remains authoritative. Omega AI does not bypass validation or force an invalid change through the Editor.
Use the authorised Editor preview and, if needed, ask Omega AI to diagnose remaining errors or refine the code again.
When the code passes the customer's normal review and validation, saving or updating remains an explicit action in the authorised Website Editor workflow.
Omega AI can generate, explain, diagnose and correct Pure HTML, CSS, JavaScript, PHP and WordPress-oriented code as text. It does not silently execute that code, write customer files, bypass Editor validation, save changes or deploy the website. The signed-in customer remains in control of copy/paste, validation, preview and save/update actions.