Everything Camlin Create can do, and how to ask for it

A fresh page opens with the well under the avatar reading “Tap to start”. One tap or key turns sound on and the avatar says hello. Browsers keep sound off until you touch the page, so nothing plays before that.

Tap the well to talk; tap it again to stop. Or type into the box under the avatar and press Enter. Both take the same asks and land on the same canvas.

Keep listening starts off, so the avatar hears you only when you tap the well — room noise and its own voice never turn into an ask you did not make. Turn it on and the mic reopens after each reply, so a conversation flows without tapping; the mic stays closed while the avatar speaks. Your choice is remembered on this device.

Tap the stop square while the avatar is speaking to cut it off, or start talking with Keep listening on. Your next ask edits the piece on the canvas rather than starting again.

Every turn is a version. Undo puts the previous one back on the canvas without another turn; Redo goes forward again. History (next to Undo) lists every version with a picture, what you asked for and when — tap one to go back to it. Build again from an older version and that becomes the newest; the versions it replaced stay in History, greyed, behind “Show superseded”. The avatar knows when you have gone back and says so, once. When a creation holds more than one piece, History has a row of chips at the top naming each piece; pick one and its versions are listed and the canvas shows it. Undo, Redo and Restore only ever move the piece on the canvas — restoring the film to version 3 never touches the document beside it (“Back to version 3 of the film”).

A creation can hold more than one piece: the game you are making and a document about it, a drawing and the 3D scene it became, a page and the app it was split into. Ask for something of a different kind — “write a one-page brief on this game” — and it is added beside what is on the canvas, never over it; the chat says “Added a document beside your game — In this creation →”. A document, deck or guide stays beside and the canvas keeps what it had (the Documents tab shows a dot); a new game, page or app becomes the piece on the canvas and the earlier one is one click away. A rail titled “In this creation” sits beside the canvas from the first piece — folded to a slim “In this creation · 1” strip while there is one piece (tap it to open; your choice is remembered), open once a second piece or a proposal arrives — listing every piece with its kind, version and which one is on the canvas, and Code · Preview · Documents tabs sit over the canvas: Preview is the piece itself, Code is its files (the tab names the file you have open), Documents lists the supporting pieces so a letter is read next to the film. Under an app the rail shows its files as a tree; the file the maker is writing pulses, and that file is read-only in Code until the turn ends. Each piece has its own History, Undo and Redo, its own proposal and its own share link. The ask you type goes to the piece on the canvas — the chip on the composer (“→ Feedback letter”) says which; pick another under In this creation to change that. Each row’s menu offers Open, Rename, History, Share this, Start new creation from here, Make this the main piece (for a document that outgrew the thing it was written about — the roles swap, nothing is deleted or moved, and every link keeps opening what it did) and, for documents, Delete; “New document” at the bottom starts an empty one for the maker to fill. The main piece’s menu also offers “Download with documents” once the creation has any: one zip with the piece as usual and every document under docs/ (a document as .md, slides as .html, a guide as .json). Keyboard: Ctrl/⌘ 1, 2, 3 switch Code, Preview and Documents; Ctrl/⌘ Shift ] and [ step through the pieces. On a phone the tabs sit inside the Canvas view and “In this creation” opens as a sheet. A creation holds up to twelve pieces.

Once something is on the canvas, a toolbar sits along its top edge as a fixed row — always there, never over your work: the kind and name of the piece (the name you gave it under In this creation), the Code · Preview tabs — Documents joins once the creation has a supporting piece and Logs once the preview has logged something, each with a count — Add detail and Make it harder (more under ⋯, where New document also lives), Undo / Redo / History (always on the row; greyed when there is nothing to undo), Import a 3D capture, Show code, Download, the 3D exports and VR where they apply, and Maximize. Code or Preview is remembered per creation, so a project you like to read as code opens that way next time. On a phone, or with Code open beside the preview, it is one compact row you can slide sideways. An app’s file names appear at the top of the canvas only while Code is on. Maximize (or the F key) fills the window with the canvas; only then does the toolbar float over the top edge and fold to a slim pill after a couple of seconds — move the pointer, touch the canvas or tab to it and it comes back, and double-tapping the pill leaves Maximize. The avatar keeps its conversation and is paused while hidden; Escape, F or the button bring the page back. Shared pieces have the same button; there it goes full screen.

New creation clears the chat and the canvas. The chat you had belongs to that creation: open it again from My creations and it is back, and the avatar picks up where you left off. Signed-out visitors keep their chat only for the page.

Reload the page — or come back to the tab, or open the same link — and the same creation opens at the same place: the piece you had on the canvas, Code or Preview (Documents or Logs if you had them up), the file you were reading, and any proposal still waiting. If the maker was mid-way through an ask, it picks the turn back up and keeps showing progress. The address bar carries the place (project, piece, view, file), so a bookmark or a copied link opens there too. Signed out, the canvas comes back for as long as the tab is open.

Camlin opens with a short line that varies from visit to visit. When you open a creation it says which one and where things were left — “Back to “Apex Kart”, your game at version 4. Last time you asked for “make it faster”. A change is waiting for you to apply or discard. What next?” — or, after a reload mid-turn, that it is picking the turn back up.

Under the chat sit the message box, Send and one ⊕ button. Everything else lives behind the ⊕, in a sheet as wide as the chat column: Attach a picture or file, the Max mode switch, the files riding on your next ask, what Studio remembers, and any notice. When Max is on, the ⊕ shows MAX underneath and glows orange. When something new lands in there while it is closed — a file finished uploading, Studio remembered something — the button glows and pulses (and a screen reader hears what) until you open it. When a creation has several pieces a small chip above the ⊕ names the piece your next ask edits (hover to read the full name) so the message box keeps its width. Esc or a click outside closes it.

Open Code and type. The pane says “Edited — not applied” and the file’s tab gets a dot; Apply (or Ctrl/⌘ S) makes your edit a new version, Revert drops it. If the maker lands a new version while you are mid-edit, your text is kept and the pane says the canvas moved on — Apply keeps your text, Revert takes the new version. After Apply the avatar knows: “You edited app.js (+12 −3). I can check it, explain it, or carry on from your version — just say.” Your next ask carries that summary, so the maker builds on your edit and never quietly writes those lines back.

In History, “Start new creation from here” copies that version as the first version of a new creation (you name it — “Moon (from v3)” is suggested) and the original is untouched. “From another creation…” does the same from any version of your other creations.

Every ask shows a small “Working… 12 s” line with Stop while it makes; after half a minute that opens into the progress card steps. A follow-up on a large project (“change the button colour”) is still a small ask — the canvas size does not make it a big turn. If it actually takes a while, Camlin says so then (“This is taking a while — I’ll keep showing progress.”) and keeps the card going. Stop keeps the last good version on the canvas and that turn is not counted. If your connection drops, or you reload or come back to the tab, the page picks the same turn up where it left off — nothing is lost and nothing is done twice. Turns have a ten-minute limit; if a piece is complete when the limit lands you get it as far as it got. After a long turn the chat asks once whether to notify you when long turns finish; it will not ask again.

The Max switch in the ⊕ options menu beside the message box (signed-in only) gives the maker its full output budget and deeper reasoning for that turn — for a long story page, a big game or a project with many files, including a full game whose app.js is large. Max keeps the whole app in view rather than cutting a file mid-script, so a kart-sized project can be edited in one turn. While it is on, the ⊕ button itself shows MAX underneath and glows orange, so you can see the mode without opening the menu. It is slower and uses more of your daily allowance — mostly in thinking time before the first line of code, so for a small tweak (“polish the buttons”) the progress card says “Max mode is on — a small change like this is usually quicker without it.” The progress card still shows while it works; Camlin only says it is taking a while if it actually does. It stays on for the rest of your visit until you turn it off. If a Max turn would use more than what is left of today’s allowance, Camlin says so before starting rather than stopping half-way.

Sometimes a piece is bigger than the maker can write in one go. It first keeps going where it stopped — the progress card says “Picking up where it stopped” — and only if the piece still cannot be finished does the chat show a quiet card: the canvas keeps the last good version, the turn is not counted, and you can Retry, split the ask into smaller steps, or (signed in) tap “Try in Max mode” to send the same ask with the full budget. A single page, game or drawing may be up to 200 KB; a reply that comes out bigger is never cut to fit — the chat says “Kept your last version — that reply came out over the size limit” and your canvas does not move. The same line appears when a reply was cut off before the end, so “updated” always means the canvas actually changed.

While an app with several files is being written, the progress card names the file — “Writing app.js · 3 of 4”. When the turn lands, a short line under the reply says what moved: “Changed app.js and style.css; kept 2 files”, or “No files changed — kept your last version” when the maker sent nothing new. Files you did not ask about are never rewritten. A large file (over about 6 KB) is not retyped either: the maker sends just the lines that change — the progress card and the code pane read “Patching app.js” — so a twenty-line fix to a 90 KB file takes seconds rather than minutes. If a patch does not line up with the file, that file is kept as it was, the reply says so (“Could not apply the edit to app.js — kept it as it was.”) and the maker gets one more go.

A switch in the top bar, “Show code creation”, is on by default and remembered on this device. While the maker works, the Code view opens on the file it is writing and the text flows into it — the file strip lights that file, the existing tree stays, a patch is applied in place rather than shown as hunk text, the caret follows the insertion and the view follows it, other files fill in as they finish — with a line above saying where it is (“Writing app.js · 2 of 4 so far”, “Patching style.css”) and the steps so far — Thinking it through, Searching our libraries, the maker’s own notes, Checking and fixing. When the turn lands the Preview is back (or Code, if that is what you had open). Switch it off and you get the small progress card alone, as before. It works on a phone (inside the Canvas view), beside the Logs pane, and while a proposal is waiting — the proposal folds to its strip so you can see the code stream. Review the stream in Safari or Chrome — Cursor’s in-editor browser does not keep requestAnimationFrame running, so games and colour motion freeze there; the code stream itself does not need that.

A page, game or app runs in the preview and, like any web page, it logs things: console.log lines, warnings, uncaught errors, a file that failed to load, and for games a note when frames stall. Those lines appear in a Logs tab beside Code | Preview | Documents (⌘/Ctrl+4) — the tab shows up the moment something is logged, with a count of unread lines or of errors. Filter by level, Copy the lines, Clear them; a “since last turn” marker shows what was logged after your last ask, and a reload of the preview draws a divider so old lines are not mistaken for new. While the preview has errors, a red pill on the canvas says so (“2 errors · 1 warning”) — tap it to open Logs — and a “Fix the errors” action appears on the canvas toolbar and in the tab. Ask that, or any edit while errors are showing, and a short digest of the distinct errors and warnings with counts goes with the ask, so the maker reads the message, file and line and fixes the cause rather than rewriting; it says what it fixed. The progress card reads “Fixing: TypeError … at app.js:42” while it works, and once the new version has run, a line in the chat says how it went: “Fixed all 2 errors; the preview runs clean”, or “Fixed 1 of 2 errors; 1 still shows in the logs”. A game’s one automatic repair uses the same digest. Logs work with the maker off too — capture and the tab are the page’s own; only “Fix the errors” needs the maker.

A page or game that has grown large (roughly 75 KB and up) is hard for the maker to return whole on every small ask. “Convert to project” on the canvas toolbar splits it on this page, at no cost and without the maker rewriting a line: the styles go to style.css, the script to app.js, the rest stays in index.html with the link and script tags in place. It checks itself first — the moved code is byte-for-byte the original, the preview builds, every file it references exists, the element ids the script uses are still there — and the chat lists what passed and what is left for you to try (playback, controls, chapters, phone layout). The result arrives as a proposal (below): Apply to keep it, Discard to keep the single file; a check that fails, or a runtime error in the first five seconds, turns Apply red and the report says which. After converting, each ask changes only the files that need it. The maker will suggest it when a file is getting big rather than refusing the edit.

Edits to an app with several files, edits to a large piece (over 16 KB), and every Convert to project land as a proposal, not straight onto the canvas: a “Proposed — not applied” card covers the canvas until you decide. It names what happened (Converted to a project, an app edit, a large edit), lists every file with what changed (“app.js changed +12 −3 · style.css new · 2 files kept”), shows the checks a conversion ran, and Show changes opens every changed line, file by file, right there in the card. Apply makes it the next version; Discard drops it and the canvas keeps what it had — the turn stays in the chat either way. Try it on the canvas puts the card aside as a strip along the bottom so you can use the proposal: Show current flips back to what you had, Show proposed back to the proposal, Review reopens the card. Your work stays on its current version until you apply. Keep asking while a proposal is open and the maker builds on the proposal; Apply then lands the whole review as one version. Undo or History while a proposal is open drops the proposal first. Tick “Always review” on the card and every turn arrives as a proposal; small edits to small pieces otherwise land as they always did. A proposal keeps for seven days, per piece. Signed in, it is kept with the creation too, so a reload — or another device — finds it waiting, and Apply lands exactly the version you reviewed without sending it up again. Enter applies while the card has focus (Ctrl/⌘ Enter too), Escape puts it aside; Discard is always a tap. On a phone the card fills the Canvas view.

Ask for a document, a deck or a guide about the game you are making — or a game from a drawing — and it is added to this creation beside what is on the canvas (see “In this creation” above); the piece on the canvas stays exactly as it was, with its own History. The chat says so. Signed out, the same happens for the page you are on; sign in to keep every piece.

The avatar switcher in the top bar steps through the Camlin avatars. Switching keeps your conversation and the piece on the canvas.

“Draw a yellow circle.”

Vector drawings that appear as they stream. Ask for more detail, a colour, a different shape.

“Make it a window with a view.”

Web pages and small interactive pieces, rendered live in a sandboxed frame. A times-table trainer or a map quiz is a page too — ask for a learning tool.

“Turn the room into 3D.”

Lit three‑dimensional scenes you can orbit. On a headset browser, “View in 3D” opens the scene as an immersive space (WebXR). On a laptop it stays on the canvas.

“Now make it a 3D model.”

Parametric models with a turntable preview. Ask for raised or engraved lettering — a name plate, a sign, a label on a lid — and the maker sets it in Inter (regular or bold, up to 40 characters a line). Download as GLB, STL, OBJ or USDZ; on an iPhone or iPad the USDZ opens in Quick Look so you can place it in the room.

“Build me a small to-do app.”

Multi-file apps in JavaScript or TypeScript with the preview beside a file strip. “Code” (the old Show code) opens an editor on any artefact, full width by default (“Preview beside” brings the split back); edit, then Apply (or Ctrl/⌘ S) to make it a version — Revert drops it — and the avatar knows what you changed on your next ask. Download the whole app as a zip. An app may hold up to 24 files and 600 KB in total; each ask after the first changes only the files that need it. Max mode keeps a large app.js in view rather than cutting it mid-script.

“Make a five-slide deck on…”

Slides with speaker notes the avatar can read aloud — ask it to “present” or “narrate” the deck. Export to PowerPoint or PDF.

“Write a one-page brief on…”

Written pieces with a table of contents, exportable to Word or PDF. A term of lessons or a club activity pack is an education programme in this form.

Drop a .ply, .splat, .ksplat or .spz file on the canvas.

Gaussian splat captures up to 150 MB open on the canvas and the avatar can talk about them. The capture stays on your device; it is not uploaded.

You still talk to the same avatar. When a plugin can help, Create offers it: Camlin Studio for an avatar of you, Camlin Architect when you want a Camlin Connect app — a booking line, a weather checker, a receptionist, or anything else — or when you are changing one already on the canvas.

Reading a flow or checking a capture can happen as part of the conversation. Studio fits, library offers, and going live wait for you. A confirm bar appears first. Creating a Connect draft does not wait on that bar — it starts as soon as you ask. Cancel on a confirm bar keeps things as they were.

“Make an avatar of me from these photos.”

Start here: sign in, attach photos or a short video, then ask Create to make a talking head of you.

“Make me a booking app for the clinic.”

Start here: ask Create for any Camlin Connect app — from the conversation, from a document you uploaded, or from a template if you pick one. Architect builds a draft as you talk. Confirm only to go live, overwrite a later save, or change Contact.

Coming next — not live in Create today. This page is a stub so Help tells the truth.

Coming next — not live in Create today. This page is a stub so Help tells the truth.

For documents, decks and guides, and for anything “latest”, “today” or “current”. Sources it used are listed under the artefact. Everyone gets this one.

For data, charts, calculations and tests. Pictures it draws land in the piece as charts; tables come back as files. Signed-in Create users only.

For pictures inside a deck, document or page. Signed-in Create users only; a few images per turn. Attach a picture and ask for a change — “make this a watercolour”, “put a hat on the cat” — and it is used as the base.

Drop a file on the message box, paste one, or use the paperclip. PNG and JPG pictures, SVG, PDF, TXT, CSV and JSON files up to 8 MB each. The maker sees pictures, reads PDFs and text files, and uses them for the ask — “build a page from this sketch”, “chart this CSV”, “summarise this PDF as a deck”. Without an account it is pictures only, two per ask; signed in, any of the seven types, six per ask, with a daily allowance of 60 files. Files are kept for the turn and are not shared with anyone else; there is no virus scanning, so only attach what you would open yourself.

Pages, games and apps can import well-known open-source libraries straight from this site — no install, no third-party CDN. Games can have real physics, sound effects, an on-screen joystick for phones, procedurally generated levels and enemies that find their way to you; apps can have drag-and-drop, fuzzy search, CSV import, charts, QR codes and a proper maths engine; 3D scenes can have physics and lettering. The maker knows the list, looks a capability up mid-turn when it needs to, and will offer one or two of these on your first game or app. What you can build with is below, by need.

Choose “Create a free account” on this site (or “Sign in” → “Create account” inside the maker). Enter your email and a password, then the 6-digit code we email you. That is it — you land in Create signed in. Passwords need 12 characters with upper and lower case, a number and a symbol; temporary or disposable email addresses cannot be used.

Your account is waiting for you. On the sign-in page (or the sign-up page) choose “Continue where you left off”, enter your email and the password you chose, and we send a new 6-digit code — use the newest one. The same happens if you try to sign in before confirming: we tell you the email is not verified yet and take you to that step.

Sign in with Camlin Connect from the top bar. An existing Camlin Connect login works too — it becomes a Create account the first time you sign in here. Signed in, your creations save as projects with versions, you can share any of them with a link or by email, and the maker gets all of its tools.

One Share button, in the top bar (the violet pill; Ctrl/⌘ Shift S opens it too — on a phone it is the violet square, and it is there on the Canvas view as well). It opens the share panel with a choice at the top: “This creation” or “Share Camlin Create”. Sharing Camlin Create gives you your own link to the front door — anyone who signs up from it is counted to you — with Copy link, Copy message, a QR code and, on a phone, the phone’s own share sheet; it works even before you sign in or make anything. For a creation, pick how the link should read: “Share this creation” puts the thing first with a small “Made with Camlin Create” footer, “Invite to Camlin Create” leads with your first name inviting them to join the beta. Then copy the link, or press Copy message for a ready-to-paste message — the title, a line about it, the link and “Made with Camlin Create” — that drops into any chat room, document, email or text message; where the clipboard allows it the picture comes along, so a chat or a document shows a card and a text message gets the words. Share… on a phone opens the phone’s own share sheet. Scan the QR code to open it on a phone, or type up to ten email addresses (with an optional note) and we send the invite for you — the email carries the title, a picture of the creation and the link. Anyone with the link can open and play it full screen on any device without an account; they never see your prompt or your email, only the first name you chose. Shares are linked to you: if someone joins Camlin Create from your link, the panel and My creations show “1 person joined from this” — a count only, never who. You can send up to 30 invite emails a day, and the same address at most once a day. Unshare from the panel to take a link down. When a creation holds more than one piece, the panel starts with a choice: “This film” (the piece on the canvas — the default) or “This creation (everything)”, which makes one link that opens with a tab for each piece. Links you shared before still open the main piece, exactly as they did. Each link has its own picture: a shared document previews as the document, a shared game as the game, and a whole-creation link shows the main piece. Email works for every choice too — the message names the piece (or the creation) it carries.

Signed in, the share panel’s Link tab ends with “Post to the library”. Add one line about the creation, pick up to five tags, and tick the box saying it is your own work and you are happy for it to be shown publicly under the first name above — then Post. It lists on create.camlinconnect.com.au/library, where anyone can open it; only you can post your creations, and nobody at Camlin can post them for you. New posts are checked by an operator before they show (usually the same day). Edits to the creation show in the library automatically. “Remove from library” takes it out at once and your share link keeps working; unsharing or deleting the creation removes the post too. If an operator holds or takes down a post, the panel tells you why in plain words. You can have up to 20 creations in the library and post five a day. Please only post what you made and have the right to share — uploaded images and files are scanned for malware before a creation can use them, and anything a visitor reports goes straight to the team.

Each account has 60 turns and about US$2 of making per day. When you reach it the avatar says so and the limit resets at midnight UTC. The whole service also has a daily budget — if the day’s budget is spent, making pauses for everyone until tomorrow. A small number of new accounts per connection per day keeps the door open for everyone.

We still hand out invite links for events and demos. An invite opens the maker for a while without an account and carries its own smaller allowance shared by everyone using it; create a free account whenever you want to keep what you make.

Free while in beta — no plan, no card. If that changes it will be published here first.

Open the account menu (the round button at the top right — it is there whether or not you are signed in) and choose “Beta — report a bug or idea”. Or just say it: “send feedback to the team”, “report a bug” or “help me write feedback” opens the same form with your words filled in, before a turn is spent and without touching the canvas; “Ask the maker instead” sends the words on as a normal ask. Pick Bug, Idea or Other, write what happened or what you wish it did (up to 2,000 characters), and send. If you are signed in we already know how to reach you; otherwise add your email if you would like a reply. “Include diagnostics” is on by default and sends the version, layout, theme, browser and the last error the page showed — the exact list is shown before you send, and it never includes what you said or made. Reports go straight to the people who build Camlin Create. You can send five an hour from one connection.

Everything the maker makes runs in a sandboxed frame on an opaque origin: it cannot read this page, your cookies or your session, and it cannot navigate you away.

Your words (typed or transcribed), the current piece and its versions go to the maker so it can edit them. 3D captures you import do not; they stay in your browser. The preview’s logs stay in your browser too: only a short digest of the distinct errors and warnings (message, file, line, count — obvious tokens and keys masked) goes with an ask while errors are showing, and the server keeps just the counts and the first error on the turn record, never the lines.

Anonymous and invite sessions keep nothing on the server beyond the day’s usage counter. Signed-in projects, versions and shares are stored so you can come back to them; delete a project and it is gone.

The mic is closed while the avatar speaks, and an echo guard drops any transcript that is really the avatar’s own words coming back through the speakers. If it ever drops a real ask, the guard has a kill switch: in the browser console run localStorage.setItem('camlin.create.echoGuard', 'off') and reload. Remove the key to turn it back on.

First-party, cookieless page analytics that honour Do Not Track and Global Privacy Control. Nothing is stored on your device.

Sends the typed ask.

On a fresh page, turns sound on and starts the avatar (the “Tap to start” state).

Maximizes the canvas (and restores it). Not while you are typing in the message box.

Code · Preview · Documents · Logs on the canvas.

Undo · Redo the piece on the canvas (not while typing or in the code editor).

Next · previous piece in the creation.

Share.

Apply a proposed change while the review card has focus; Escape puts it aside.

Restores a maximized canvas; leaves the full-screen 3D view.

The line between the avatar and the canvas has a grab handle on it: drag it, or focus it and press ← → (Shift for bigger steps), Home / End, Enter to reset. The width is remembered.

Applies your edit as a new version.

Say “a page”, “a game”, “a deck”, “a 3D model” when you care which one you get; otherwise the maker picks.

“Make it bigger”, “add a cat on the sill”, “now in blue” — the maker edits what is on the canvas.

“Add sound effects”, “real physics”, “a joystick for phones”, “use three.js”, “a d3 chart” — the maker maps it to a library on the list.

Tap the page once — browsers keep sound off until you do. Check the device is not muted. On a headset, allow audio for the site.

Allow the microphone when the browser asks. If you refused earlier, click the lock or site icon in the address bar and allow it, then reload. The mic is closed while the avatar speaks — wait for it to finish or tap the stop square.

This should no longer happen. If it does, reload the page and tap once before speaking, and tell us which browser you were using.

Undo, then ask again with a different word for the thing you meant. Some asks will not land first time in beta.

The maker repairs a runtime error once by itself. If it is still broken, ask it to “fix the error” or open Code and fix it yourself; Apply makes your edit a version and the avatar builds on it.

Your daily turns or budget are spent. Limits reset at midnight UTC. A free account has a larger allowance than an invite link.

Immersive view needs a headset browser with WebXR (Vision Pro Safari, Quest browser). On a laptop the scene stays on the canvas and you can orbit it.

Camlin Create updated while this tab was open. Nothing is lost: signed in, your creations save as you go; tap Reload when the current turn has finished to get the new version. Not signed in, the canvas clears on reload — sign in first if you want to keep what is there.

Tell us. Account menu → “Beta — report a bug or idea” reaches the people who build this; the diagnostics it offers to include help us find it faster.