Mission 1 - Domain to Live Website

Launch your first live AI website.

Connect a managed domain in the dashboard, then build directly with Codex in WebTerminal or first pair OpenClaw with Telegram and send the same instance-aware handoff from chat. Either path turns your creative brief into a public website that you can verify and improve.

Mission outcome

A working HTTPS website on your attached domain, built in your private managed AI environment and ready for mentor review.

Choose your control surface

Work directly in WebTerminal, or operate through OpenClaw in Telegram.

Both paths use the same managed instance, domain handoff, editable creative brief, release checks, and mentor proof gate. Choose the interface that helps you start and stay in control.

Direct path - no extra setup

Build in WebTerminal

Use the full-width terminal on this page when you want immediate visibility of commands, files, services, and validation output. Paste the instance handoff first, then your edited website brief.

Continue in WebTerminal

Telegram-first path - one-time setup

Operate with OpenClaw

Prefer a chat interface? Complete OpenClaw Mission 0 first to install the orchestrator, pair your bot with Telegram, and verify the live connection. Then return here and send the same instance handoff and edited brief through your paired OpenClaw chat.

1
Open the OpenClaw Orchestrator Lab and self-enrol.
2
Complete Mission 0 and verify Telegram pairing end to end.
3
Return to this mission and send the same handoff plus website brief from Telegram.

Start OpenClaw Mission 0 Preview the OpenClaw guide

The interface changes; the delivery contract does not. Publish a real HTTPS website, validate it, and submit objective proof.

Founder walkthrough

Watch the complete domain-to-delivery workflow before you begin.

English audio with captions. The recording uses a real managed domain and a real instance workflow; no credentials or private learner data are shown.

Open the accessible transcript

Video chapters

00:00Result first: the finished public website
00:24Attach a managed domain
01:03Copy the instance handoff
01:15Brief Codex and build
02:26Verify HTTPS, mobile, accessibility, and proof

Your five-step operator path

1
Connect domain - select a running instance and attach a new managed domain.
2
Copy handoff - open the Agent tab and copy the Instance Agent Handoff.
3
Brief the agent - paste the handoff and edit the creative requirements below.
4
Launch - let the agent inspect, build, configure, and publish the website.
5
Verify - open the public URL and capture objective release evidence.

Attach the domain in your dashboard

Use the Domains tab for the running instance that belongs to this practice workspace. The platform owns public DNS and TLS; the instance agent owns the website application and local web service.

1
Open the Sell.Systems Automation dashboard and select the running practice instance.
2
Open Domains, enter a unique first label, and choose agenthost.link for this website mission.
3
Choose Plan domain and review the exact domain and routing plan.
4
Choose Add domain and confirm the requested addition within the confirmation window.
5
Wait until the domain status is active. Do not change public DNS manually.
6
Open Agent, choose Instance Agent Handoff, and copy the complete handoff prompt.

Open the Domains dashboard

Edit your website brief, then send it with the instance handoff

Keep the domain handoff above this prompt. Replace every bracketed field with your own creative requirements. The instructions are agent-agnostic even though this course demonstrates the workflow with Codex CLI.

You are the implementation agent for this website.

Read https://github.com/SELLSYSTEMS/rules-for-creation-webdesign-websites-for-ai-agents/blob/main/AGENTS.md and every file it requires before changing files. Use the current workspace and the managed domain already supplied in the instance handoff.

CREATIVE BRIEF - EDIT EVERY BRACKETED FIELD
- Working name: [ADD YOUR WEBSITE OR BRAND NAME]
- Purpose: [DESCRIBE THE REAL OFFER OR OUTCOME]
- Primary audience: [DESCRIBE WHO THIS WEBSITE IS FOR]
- Primary action: [DESCRIBE THE ONE ACTION VISITORS SHOULD TAKE]
- Required sections: [LIST THE SECTIONS YOU NEED]
- Tone and visual direction: [DESCRIBE THE FEELING, REFERENCES, AND NO-GO STYLES]
- Required facts and proof: [ADD ONLY FACTS YOU CAN SUPPORT]
- Required languages: [LIST LANGUAGES OR WRITE ENGLISH ONLY]
- Supplied assets: [LIST REAL LOGOS, PHOTOS, COPY, OR WRITE NONE]
- Additional creative requirements: [ADD YOUR OWN IDEAS HERE]

DELIVERY CONTRACT
1. Inspect the current project, runtime, domain handoff, existing files, and active services before editing.
2. Create an original, production-ready responsive website with one product-relevant signature visual moment, not a catalogue of effects.
3. Use original generated imagery only where it supports the subject. Never generate fake proof, testimonials, dashboards, customer logos, or product states.
4. Keep the important meaning in semantic HTML. Implement keyboard access, visible focus, reduced motion, correct font/script coverage, and RTL behavior for every requested language.
5. Implement factual title and description metadata, canonical behavior, social metadata, crawlable content, the narrowest correct structured data, robots behavior, and sitemap coverage where applicable.
6. Keep secrets out of source control and public files. Record the source and usage basis of every supplied, generated, or third-party asset.
7. Configure the local application or web service for the domain from the handoff. Do not change platform-owned public DNS or TLS.
8. Validate the public URL, HTTPS, desktop and mobile layouts, text containment, required interactions, console/network errors, accessibility basics, metadata, structured data, and reduced motion.
9. Continue through implementation and verification. Do not stop after a plan or ask me to restate the task. Ask one precise question only if an irreversible requirement is truly missing.
10. Finish with the public URL, changed files, commands/services used, validation evidence, asset provenance, and any honest remaining risk.

Build a real media layer, not decorative filler

The walkthrough demonstrates original image generation with Nano Banana 2, narration with ElevenLabs, and final assembly with FFmpeg. Your website may use the best available tools, but every published asset must be relevant, reviewed, optimized, and truthfully sourced.

Do not submit until these release checks pass

Public URL - the attached domain opens the intended website without a login or redirect loop.
HTTPS - the browser shows a valid secure connection and no mixed-content warning.
Responsive layout - real desktop and mobile views have no overlap, clipping, or horizontal overflow.
Accessibility - keyboard navigation, visible focus, headings, labels, contrast, alt text, and reduced motion are usable.
Search and LLM readability - semantic HTML, factual metadata, canonical URL, structured data, and crawlable answers agree with the visible page.
Proof - screenshots and notes show the real URL and verified state without secrets or private data.

Practice on your own server without limits: websites, bots, content, and automations in one place.

Launch AI Systems Free →