[Feature Request] Allow custom domain binding (CNAME / custom DNS) for hosted projects on chat.z.ai

[romangalaxys10-spec]

Summary & User Need

Users frequently build and deploy web applications directly from chat.z.ai using Agent Mode and Web Projects. Currently, when publishing, projects are hosted exclusively under randomly generated subdomains on *.space-z.ai (e.g., https://xxxxx.space-z.ai).

Clients and community builders have requested the ability to bind their own custom domains or subdomains (both free DNS domains and top-level domains) to their published projects, turning chat.z.ai into a viable production hosting alternative (similar to Vercel, Netlify, or Lovable).

---

User Case & Discord Context

• Reported by User: 『ƝØᑕ丅工Ꚃ』 in the official Z.ai Discord community
• Discord Thread Reference: https://discord.com/channels/1346756824233148527/1552319625889316944
• User Statement:

  "Let assume I made a website of something and I need to publish it, so I publish it but the url is xxxxx.space-z.ai. Can you guys add like I can add my external free domains and then publish it? ... My site can be live at the domain, top level domain and free domains etc."

---

Proposed Solution / Feature Scope

1. Custom Domain Binding in Publish Modal:
   • In the Publish dropdown/modal on chat.z.ai, add a "Custom Domain" configuration field.
2. DNS Verification & CNAME Target:
   • Provide standard CNAME / A-record instructions (e.g. CNAME pointing to cname.space-z.ai or a dedicated ingress router IP).
   • Basic TXT record or automatic HTTP challenge verification.
3. Automated SSL/TLS Provisioning:
   • Automatic Let's Encrypt / Cloudflare certificate issuance for bound domains.
4. Direct Connector / Native Integrations (Bonus):
   • Alongside WeChat and Discord agent connectors, offer a native GitHub repository connector in project settings to allow continuous sync and automated deployments.

---

Submitted on behalf of the community by Roman M. (Volunteer / Ambassador).

[github-actions]

👋 感谢你的反馈，我们已经收到。

• 维护者看到后会尽快回复你。
• 状态保持为 status: 待评估，你可以随时补充信息。
• 信息不全时我们会打上 needs: 更多信息 标签并 @ 你。

---

👋 Thanks — we've received your issue.

• A maintainer will get back to you as soon as we can.
• Status stays at status: 待评估 (Triage); feel free to add context.
• If we need more details, we'll add needs: 更多信息 and ping you.

[bosmdavid-gif]

+1. Until this exists, a workaround for anyone who needs their own domain today: if you can download/export the project's built files (the folder with index.html), put them on any static host that supports custom domains, then point DNS at it:

• www (or any subdomain): CNAME to the host's target.
• The bare domain (example.com): an A record to the host's IP, or ALIAS/ANAME/"CNAME flattening" if your DNS provider has it (a plain CNAME isn't allowed on the apex).
• Remove old A/AAAA records for the same names, and wait for the host to issue HTTPS (usually minutes, sometimes a few hours).

For the feature itself, the pattern that tends to work: CNAME for subdomains, an A record (fixed ingress IP) for apex domains since many registrars can't do ALIAS, a TXT record for ownership, and automatic Let's Encrypt. It also helps to show the certificate state in the UI, because "DNS verified but no HTTPS" is the most common stuck state people report.

Disclosure: I made DropTheHassle, which does the "drop the folder, get a free *.dropthehassle.app link, then point your own domain's A record at it" part. Any static host works for this, though.