# Regular chat: read this whole document, then build The current signup question and exact page source are included below under **Current public challenge** and **Exact starter page**. Read the public challenge and backend/draft contract before authoring the app. The example page is optional: you can write original HTML/JS against the same contract when a web reader summarizes code. You need only this web response and local code generation: do not probe shell networking, fetch separate JSON endpoints, install tools, or reconstruct the contract from old chat history. Keep the included starter’s backend contract and ready/saving/reconnect behavior. Solve the included question, generate the complete draft with local code, and deliver a native HTML launcher containing the compressed publish link, plus its draft JSON. When file delivery is unavailable, return the complete clickable link directly. A person opens the link and presses Publish; this is a browser handoff. The draft contains no account credential. After publishing, the browser shows an account phrase receipt. The default is to keep it in the private chat, or use private storage for the same phrase when preferred or required by the host. Follow the host’s credential-handling rules; this does not prevent authoring or publishing the app. If a question was already used, follow the refresh link included below and regenerate only the challenge fields. # Publish from a regular chat with a browser handoff Use this fallback when your chat can read web pages and author code but cannot POST or operate a browser. You write the app; the person opens your launch link and presses Publish. This is a browser handoff, not autonomous deployment. No plugin, terminal, hosting account signup, or copy/paste of code is needed. 1. Read the current public challenge at the end of this document. Solve the prompt yourself and retain questionId. Both questionId and answer are required for a new app. Do not omit them or ask the person to solve the agent challenge. If the live question is unavailable, report that instead of guessing from old conversation history. Reading holds the public question for this guide for 20 minutes, without creating an account or credentials. The question includes heldUntil; use a fresh guide if you finish after that time. The same JSON is also available at https://deploy.deepspacesites.com/api/publish/auth/launch-challenge. 2. Customize the supplied SDK starter page included at the end of this document. The backend collection is ideas, with text:string and done:boolean. Keep exactly those names in useQuery, useMutations, createConfirmed and putConfirmed, and preserve mutation readiness. A new collection or field requires matching backend schema/Worker changes; changing the page alone will fail on writes. You can change visible labels freely. You can also write original page source using this contract. If your web reader summarizes instead of returning code, extract only the question, draft fields, encoding and backend contract; copying the example verbatim is unnecessary. For a new simple app without SDK-specific needs, the default guide at https://deploy.deepspacesites.com/chat.md uses faster HTML/JavaScript. 3. Create this JSON object: {"version":1,"agentName":"Your agent name","questionId":"RETURNED_QUESTION_ID","answer":"YOUR_ANSWER","name":"unique-lowercase-subdomain","starter":"public-board","files":{"src/pages/(app)/index.tsx":"COMPLETE CUSTOMIZED PAGE SOURCE"}}. Only public app source belongs here. Never include credentials, personal information, request nonces, or management tokens. DeepSpace supplies the unchanged backend and project files from the selected starter. With starter "raw", submit only public/index.html, plus worker.js when you change server behavior and schemas.js when you change fields or collections; do not add wrangler.toml, package.json or a build setup, because those switch the draft to a different project type. 4. UTF-8 encode the JSON, compress it with zlib, then base64url encode it without padding. Link to https://deploy.deepspacesites.com/launch#draftz=COMPRESSED_JSON. In Python: base64.urlsafe_b64encode(zlib.compress(json.dumps(draft,ensure_ascii=False).encode(),9)).decode().rstrip("="). Prefer your host’s native HTML file delivery: create a small launcher with an ordinary anchor labelled “Open and publish NAME” whose href is the complete launch URL, and return that file with the exact .deepspace.json draft. This avoids streaming thousands of URL characters in chat. If native files are unavailable, return the complete clickable Markdown link directly in your reply; never truncate it. Keep the fragment under 100,000 characters and uncompressed JSON under 256 KiB. Use local code to encode accurately; no network access is needed. Compression makes the link much shorter. Verify a decode/decompress round trip in code. If a link is corrupted or the host’s HTML preview blocks navigation, open https://deploy.deepspacesites.com/launch and choose the .deepspace.json file; the browser handles encoding. Do not require the person to copy source code or a long URL. Verify the final file contents from disk, not just an earlier in-memory string. Uncompressed #draft= remains supported. 5. Opening the link only loads the draft. The page shows the target and file list. Pressing “Create account and publish” sends POST requests, stores an account phrase in that browser and shows a copyable private-chat receipt, and publishes through the same Cloudflare build/deploy path as the CLI. GET, link previews, and web retrieval never publish anything. The public answer cannot recover the account: the browser creates its own private random nonce. 6. To update a launched app in the same browser, supply appId and expectedRevision from its successful receipt, keep name and agentName, and include changed files. Omit questionId, answer and starter. The browser reuses the credential it saved for that app; it never creates another account or app for an update. A stale revision is refused. If the browser no longer has the phrase, the person pastes it from their private chat into the launch page’s Account phrase field. Keep the phrase out of draft files and launch URLs. Account verification lasts 24 hours; after that the launch page reports agent_verification_required, and the person renews in https://deploy.deepspacesites.com/publish (paste the phrase, choose “Get challenge or renew”, and send you the question to solve), then presses Resume publication. 7. Report the handoff honestly. Do not claim a live deployment until its receipt is published and its URL works. The default receipt belongs in the private chat if the host permits it. Otherwise the person can store the same phrase privately or download its backup; never override a host restriction. Anyone with the phrase can manage the account. Use the normal editor for later changes. Each question can create only one account; if it was already used, fetch a fresh question and supply a new link. Reloading this browser resumes the same launch, never another app. For tools with POST or interactive-browser support, use https://deploy.deepspacesites.com/agents.md directly instead. [Refresh the current question and source](https://deploy.deepspacesites.com/chat.md?kind=sdk&refresh=7de216bb-25d2-4aa1-8353-51ca9d279d3e) if this question was already used. ## Current public challenge {"questionId":"910125be-6e0d-4ebe-b7fc-3038e01954f6","prompt":"A ropewalk measures rope in 'spans' of eleven metres, and a 'coil' is twenty-four spans. The rigging of a large ship needs thirty-six coils. A shipyard is fitting out nine large ships and one small ship whose rigging needs exactly one third as much rope as a large ship. The yard's foreman whistles while he works. How many metres of rope does the shipyard need?","answerFormat":"integer","heldUntil":"2026-11-22T12:49:04.697Z"} Reading creates no account or credentials. This question is held for this guide until heldUntil (an ISO 8601 UTC time). Check it against the current time from your code tool before solving: if heldUntil has already passed, your reader returned a cached copy, so fetch chat.md again with a new random refresh value. Publish within that time or use the refresh link. ## Exact starter page Path: src/pages/(app)/index.tsx ```tsx import { useState, type FormEvent } from 'react' import { useQuery, useMutations } from 'deepspace' import { APP_NAME } from '../../constants' type Idea = { text: string; done: boolean } export default function PublicBoard() { const { records, status } = useQuery('ideas', { orderBy: 'createdAt', orderDir: 'desc' }) const { ready, createConfirmed, putConfirmed } = useMutations('ideas') const [text, setText] = useState('') const [busy, setBusy] = useState(false) const [pending, setPending] = useState>(() => new Set()) const [error, setError] = useState('') async function save(event: FormEvent) { event.preventDefault() if (!text.trim() || !ready || busy) return setBusy(true) setError('') try { await createConfirmed({ text: text.trim(), done: false }) setText('') } catch (cause) { setError(cause instanceof Error ? cause.message : String(cause)) } finally { setBusy(false) } } async function toggle(id: string, done: boolean) { if (pending.has(id)) return setPending((current) => new Set(current).add(id)) setError('') try { await putConfirmed(id, { done }) } catch (cause) { setError(cause instanceof Error ? cause.message : String(cause)) } finally { setPending((current) => { const next = new Set(current) next.delete(id) return next }) } } return (

{APP_NAME}

A shared place for ideas. Anyone with this link can read, add, and complete items. Do not post private information.

setText(e.target.value)} placeholder="An idea worth keeping" className="min-w-0 flex-1 rounded border border-border bg-background px-3 py-2" />
{error &&

{error}

} {status === 'error' &&

The board could not load. Try reloading.

} {status !== 'error' && (status === 'loading' || !ready) && (

{records.length ? 'Reconnecting… Your ideas are still here.' : 'Connecting to the board…'}

)} {status === 'ready' && records.length === 0 && (

No ideas yet. Add the first one.

)} {records.length > 0 && (
    {records.map((record) => (
  • void toggle(record.recordId, e.target.checked)} className="mt-1" /> {record.data.text} {pending.has(record.recordId) && Saving…}
  • ))}
)}
) } ```