A little progress.
A place for the small things worth doing. Add a note, mark it done, and watch it update for everyone.
Connecting…
# 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 HTML/JavaScript starter page included at the end of this document. This HTML/JavaScript starter uses the ordinary DeepSpace RecordRoom: SQLite records, schema validation, permissions and live subscriptions, with no local install or build. GET /api/items returns an array of {id,text,done,created}, newest first. POST /api/items with {text} creates a note; POST /api/update with {id,text} edits it in place, and {id,done:0|1} sets completion. POST /api/toggle with {id} toggles completion; POST /api/delete with {id} removes the note. Writes return the full updated array. Address notes by id. Text is 1–240 characters; done is numeric 0/1; created is Unix milliseconds. Edits preserve identity and creation time. WebSocket /api/live uses the SDK protocol, not bare arrays. On every connection send {"type":"core.subscribe","payload":{"subscriptionId":"items","query":{"collection":"items","limit":500,"orderBy":"createdAt","orderDir":"desc"}}}. A core.query_result message contains payload.records: each record has recordId, data and createdAt. Map it to the HTTP shape with {id:record.recordId,...record.data,created:Date.parse(record.createdAt)}. On core.record_change, reload GET /api/items. Ignore unrelated protocol messages; resubscribe on reconnect. Load GET /api/items immediately alongside the socket; enable HTTP writes once data is loaded, even while live updates reconnect. To add fields or collections, edit schemas.js using the standard CollectionSchema contract, then update the app's HTTP handlers and tool definitions. RecordRoom owns database changes and validation; do not add SQL tables or a second synchronization layer. The starter intentionally grants public access. Narrow schema permissions for private collections; verified human and target-bound agent tokens use the same permissions. React hooks and ready-made login UI remain available in the SDK starter. Give the app its own responsive design, labeled inputs, per-row controls whose accessible names include the item text ("Mark done: Buy milk", not a repeated "Mark complete"), visible keyboard focus, helpful empty states and retryable errors that preserve typed input. Keep a public-data notice. Verify a real create, edit and completion, then a second-session live update and a reload. Return the working URL and report any checks your host cannot perform. For raw apps, load GET /api/items immediately alongside the WebSocket connection. Once either returns a valid snapshot, enable HTTP writes; a reconnecting socket should not disable a usable HTTP backend. Keep loading, saving and live-connection state separate. Recompute button state on input, initial load, successful or failed saves and reconnects; restore controls in finally. Preserve an open edit and typed text when another session broadcasts. Give checkbox/button controls an explicit nonzero size and prevent flex shrinking. Ensure display:flex/grid styles do not override hidden error panels; use [hidden]{display:none!important} and show retry controls only after a failure. On phones, put the main task input and list before secondary charts or inspiration panels. Keep test-run budgets and verification notes in your report rather than the app’s end-user copy. Check the rendered create/edit/complete controls, not only their API endpoints; report visual checks as unverified when your host has no browser. GET /api/inspiration returns {success:true,data:{title,description,extract,url,...}} through server-side McAPI for the fixed Wikipedia article Kindness. Show data.extract and link data.url; returned data.title may reflect a redirect. Successful results are cached for 24 hours. Do not promise random articles without changing the server route, or describe an offline fallback as a live integration result. You can change visible labels freely. You can also write original page source using this contract. Retain the page’s connectAgentTools module import and registration from /deepspace-agent.js so supported browsers discover the app actions; do not remove the starter’s shared agent adapters. 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 SDK features, use the complete alternative guide at https://deploy.deepspacesites.com/chat.md?kind=sdk. 3. Create this JSON object: {"version":1,"agentName":"Your agent name","questionId":"RETURNED_QUESTION_ID","answer":"YOUR_ANSWER","name":"unique-lowercase-subdomain","starter":"raw","files":{"public/index.html":"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=raw&refresh=54f37c63-237e-4aaa-8a57-01d33e1a9cdb) if this question was already used. ## Current public challenge {"questionId":"903b7b44-0975-4735-8423-821510572560","prompt":"A stadium has four stands. The north and south stands each have eighty-five rows of sixty-four seats. The east and west stands each have forty rows of seventy-five seats. For a concert the whole east stand is closed for the stage, and in every other stand the first two rows are kept empty for safety. The stadium was painted green last year. How many seats can be sold for the concert?","answerFormat":"integer","heldUntil":"2026-11-22T12:49:01.327Z"} 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: public/index.html ```html
A place for the small things worth doing. Add a note, mark it done, and watch it update for everyone.
Connecting…