Omniscio

Forms (Plugin)

Forms is the free Omniscio marketplace plugin for asking people questions: build a form, publish it as a public link anyone can open without an Omniscio account, and collect the answers back in the app — where an optional auto-send rule can hand a new response to an agent session.

On this page

Marketplace plugin — Forms is not built into Omniscio. Install it from the Plugin Marketplace and enable it; until you do, there is no Forms screen and no form link.

What it is

Forms reports usage as action names only, such as opening Responses or successfully publishing a form. These reports contain no form titles, question text, answers, or form and session identifiers. Clicking the Responses tab while it is already open does not count another visit; leaving and returning does. A failed usage report does not interrupt your work.

A form builder and response collector that lives inside Omniscio. You build a form out of fields, publish it, and get a public link — anyone can open that link and answer it, with no Omniscio account and nothing to install. Answers come back into the app attached to the form that collected them.

Its point is the last step: a response is one click from an agent. A form can carry an auto-send rule that hands a new response to an agent session with a prompt you wrote, so an answer can turn into work without anyone copying and pasting it.

You can also send responses by hand from the Responses screen: tick some rows and press Send N to agent, or press Send all to agent to send every response of the form, not only the 50 on screen. A confirm says how many agent sessions will start and how many of the day's 50 hand-sent sessions are left (the limit is counted across all your forms), and a batch over the limit is refused with a plain sentence. A response that did not go shows a "Not sent" or "Not sure if this one was sent" card with the whole reason and the respondent's answer in its own box. A response that already went to an agent never gets a second one: pressing Send to agent on it says "This response already has an agent" and offers Open that session, where you type new instructions, and a batch lists each such response as "Already has an agent" instead of counting it as sent. When some did not go, Send the failed ones again re-sends just those with the same instructions (never one marked "Not sure if this one was sent"), and the instructions you typed stay in the box for that form until a send where every response went.

New answers arrive on their own. Opening the Responses screen shows the answers you already have at once and asks the cloud for new ones straight away, with a quiet "Checking for new answers…" line under the header. An answer that just arrived appears at the top with a soft highlight that fades in about 3 seconds and a small New label for the rest of the visit. The line then says when Forms last checked and that new answers arrive every few minutes; Refresh sits beside it. While the screen stays open, the background pull (every 5 minutes) adds its answers without a click. If a check fails, your answers stay on screen under a short note naming the reason and when they were last updated, with Try again; a check that is only slow says "Still checking" and clears itself when it finishes.

You are told when answers stop arriving. If the background pull fails three times in a row (about 15 minutes), Forms puts one row in your Omniscio inbox, "Forms has stopped receiving responses", naming the likely cause: a full disk, the Forms cloud answering with an error, or the cloud answering too slowly. Responses then shows "New responses are not arriving" with the same cause, a reminder that armed rules cannot send anything until answers arrive, and Retry now. The next good pull removes the row and the banner by themselves. One or two failed pulls stay silent, and a sign-in problem keeps its own "Forms cannot sync your responses" row.

Leaving the editor never quietly drops unsaved edits. If saving keeps failing and Forms stops retrying, the line under the editor says "Not saved. Your latest changes are only on this screen for now." Leaving the editor then (another tab, Responses or Rules, another form, a new form, Settings or an agent session) asks "Your changes are not saved", with Stay and Leave anyway. Stay keeps every edit on screen; when everything is saved, nothing is asked.

Two safety properties are built into that shortcut, and both are deliberate:

  • The agent has no tools, and the answers reach it as quoted data it is told never to obey. The rule starts the session with your template plus the response's answers in one marked block. The agent cannot open files, run commands or call anything, so the worst a hostile answer can do is change the text the agent replies with.
  • An auto-send rule is always created disabled; you switch it on in the Forms panel.
  • An auto-send rule only starts an agent when Forms holds the arm record written by the maker's own Arm. A rule switched on from outside, copied, or changed after arming (its form, answer match or instructions) shows Needs attention with its switch off and stays silent until the maker presses Re-arm. Rules armed before this protection shipped need one Re-arm each.

Where to find it

  • Install it from the Plugin Marketplace (plugin-marketplace.md) — it is free, category productivity, authored by JLS Trading Co.
  • Its own screen — once enabled it adds a Forms row to the sidebar (clipboard icon) and hides the project panel inside it. That screen is where forms are built, published, and read.
  • The public link — a published form is served by Omniscio's cloud, not by your machine, so the link keeps working for answerers after you close the app.
  • For agents — its CLI routes are listed in plugin-cli-discovery.md alongside every other plugin's.

How it behaves

Agent sessions in the Sessions panel. A Sessions button at the right end of a form's tab row opens a panel beside the form. The button shows one amber dot while an agent needs you or one red dot while one has an error (red wins), with the counts only on hover. The panel has an Ask about your forms box (Enter starts an agent about the form you have open, and the line under the box says which form) above one list of every agent Forms started, by a rule, by Send to agent or from the panel, newest first. Each row names its form and says needs you, running, error or when it started. The agents start like any session you start yourself, so they also appear in Omniscio's sidebar and Inbox. Click a row to read and answer it inside the panel; the back arrow returns to the list, and open the session in Omniscio shows the full view. Open the session on a response that already has an agent opens it in the panel. Forms cannot answer an agent's request to use a tool: it says so, offers Open in Omniscio to answer, and keeps its reply box off until that is answered. Opening the panel puts the cursor in the box, Escape closes it and returns to the button, and Forms remembers whether you left it open. On a window narrower than 1100 px it goes over the form instead of squeezing it. On a phone the rail keeps its Forms | Agent sessions switch and the list grouped by form. Each form in the Forms list also says when its agents need you or are working. Only agents Forms started are listed; your other sessions stay in Omniscio's own sidebar.

Draft, published, closed. A form is in one of a few states. A draft is yours alone. A published form is live on its public link and collecting. Closing stops it collecting while leaving the link working — a visitor sees that the form is closed, and you can reopen it later. A form that was never published cannot be closed: Forms refuses in plain words and sends nothing to the cloud, so a draft stays on your computer until you choose to publish it. Unpublishing takes a published form back to a draft so you can edit it; answers already collected are kept. Publishing refuses, in plain words, a form with more than 500 questions, more than 5,000 options across its questions, or more than 512 KB of publish data; every real form is far below these limits.

Page routes only go forward. A form can send people to another page depending on an answer, or after a page, but only to a later page or straight to the end — never back, so a form can never loop. Reordering pages after a route is set can leave a route pointing at an earlier page, and Forms Cloud refuses such a form. Publishing now says so before anything is sent, in plain words that name the question, the answer and the page (for example: In "Do you own a car?", the answer "No" goes back to the page "Thanks". Routes can only go forward, so this form can't be published yet. Point it at a later page, or remove it.). The same applies to a route to a page that has been deleted, and to the other routing rules. Closing and unpublishing are never refused for this, so a live form with a bad route can always be stopped.

Closing and unpublishing change only the status. They never publish what you edited since the last publish, and a half-finished or invalid draft does not stop you closing or unpublishing a live form. Reopening a form whose content is unchanged is also status-only; reopening after edits publishes them, and the draft must be valid.

Connecting Forms to your Google account. Publishing, pulling responses and erasing cloud data all run under your Google account, so the first time you press Publish (or Connect) Forms opens a sign-in page in your browser and shows the link in case the page did not open. Sign in with Google there; the page then shows you a short code, and you type that code into Forms and press Finish. Only the Forms window that opened the page can use the code, so never send it to anyone, and a code you were sent by someone else is not one to type. The sign-in window lasts ten minutes; after that, press Connect again. To sign this computer out, open Settings and press Disconnect beside your account: it revokes this computer's key in the cloud, so the key cannot be used again, and your published forms and answers stay as they are. This computer also forgets which account was connected and where it had got to in pulling answers, so connecting again pulls from the start; answers already here are never doubled. Erasing your account clears the same things. Forms is connected on one computer at a time for each Google account: connecting it on another computer signs the first one out, and the first one then says so in Responses and in your inbox, with Connect to take it back. Your published forms belong to the Google account that published them: after you connect a different account, Responses names the account they belong to, and Delete on such a form offers Remove from this computer only, which leaves the cloud copy and its answers with that account.

When a different person signs in to Omniscio while a Forms window is open, Forms forgets the previous person's connection on this computer — the sign-in key, the connected account, and where it had got to in pulling answers — and reloads, so the new person starts signed out. Unlike pressing Disconnect, this does not revoke the key in the cloud, so the previous person's published forms and answers are untouched and they can connect again later.

Folding the forms list. When the Forms area is wide enough to keep the list beside the form you are working on (960px or more), a button in the top corner of the list folds it to a slim 48px strip, and the form you are editing gains the room. The strip keeps four things one press away: New form (+), Search forms, the list itself (press it to open the list again) and Forms settings, pinned to the bottom, each with its name on hover. Folding slides over a fifth of a second, or happens at once if your computer is set to reduce motion. The button says "Fold forms list" or "Unfold forms list" and tells a screen reader whether the list is open; Ctrl+Shift+E (Cmd+Shift+E on a Mac) does the same from the keyboard, and focus stays on the button. Forms remembers your choice for next time, for Forms only. On a narrower area, where the list is the whole screen or opens over the form, there is no fold button. The live preview's Hide and Show button beside your questions also remembers its state.

A new form's preview shows example questions, clearly marked. Before you add your first question, the live preview and the full-screen Preview show a few example questions so you can judge your look. A note above them reads "These are example questions, not yours", each one is tagged "(example)", they are greyed out and cannot be filled in, and there is no Submit button. In the one-question-at-a-time layout you see the note over the first example only. They disappear as soon as you add a real question, and a form people receive never shows them.

"Before you publish" says why its button is grey. The first publish (and Reopen) asks who the form is for, and the confirm button stays grey until Adults or Teens is picked. A short line beside it says so: "Choose who this form is for to continue." (or, if Children under 13 is picked, "This form cannot be published for children under 13."). Every confirm dialog in Forms is also never taller than the window: on a short window its text scrolls and Cancel and the confirm button stay in view.

What a respondent sees at the foot of a form. One short line: "Your answers go to the person who made this form" (or the name you set in "Asked by"), then "This site is protected by reCAPTCHA", then a Privacy & data button. Pressing it (or Enter or Space on it) opens a panel right there, with no new page: where answers and files are stored (Omniscio, on Google Cloud in the United States), that the maker may use an AI assistant to read and act on the answers (so, depending on the assistant you chose, they can be processed by a company outside the United States, including in China), how long they are kept (for as long as you have chosen, at least 90 days, and they can be deleted after that, or sooner if you delete the response or the form, so a respondent asks you to remove theirs), what reCAPTCHA checks, a request not to send passwords, card details or health information, and a link to Omniscio's full privacy notice. The request not to send sensitive things also appears right under every file upload and long answer question, where it matters most, in a small amber box so it is hard to miss. The keep time is the one you pick in "Keep answers for" (90 days by default, or 6 months, 1 year or 2 years); it covers the copy in Omniscio's cloud only, and the copy already brought home to your own computer stays, as the keep-time picker says.

One network cannot spend a form's whole day. Each form keeps, beside its daily limit (500 answers and 250 files or 512 MiB by default), a per-network share: 100 answers, 100 files and 128 MiB per network per form per day, keyed by a short hash of the caller's address that lives only in that day's record. Past its share a network is told it is their network, not the form, that is out of room, and the form stays open to everyone else; a caller the cloud cannot identify is never counted, so a keying gap can never lock a form. The address the cloud keys on is the right-most public hop of X-Forwarded-For, so a caller can prepend a forged value but cannot move its key by sending a header of its own; the rule assumes every hop to the right of the caller is a private Google-internal hop, which must be re-measured if a public proxy is ever put in front. Bot-check tokens are single-use: the page mints a limited-use App Check token for every submit and upload and the cloud consumes it on verification, refusing a second use (one reCAPTCHA assessment per request, free up to 10,000 a month). When a form's own daily limit is hit, the cloud writes a notice that the maker's next sync turns into one inbox alert per form and kind, naming the form and pointing at its Settings. The alert is remembered by the day the limit was hit, so the next day's sync, which still sees yesterday's notice, never raises it again.

A close always wins a race. Submit and upload both re-read whether the form is open inside the same step that spends the day's allowance, so a form closed (or deleted) a moment before the answers or file arrive refuses them with the usual "not accepting responses" (or "does not exist") message, stores nothing, spends nothing and writes no daily-limit notice. On the page, a respondent who saw "This form stopped accepting responses" and sends again after the form was reopened gets the normal thank-you, and when someone picks a second file while the first is still uploading, only the last file picked can become the answer and Submit waits for it.

Answers survive. Closing, unpublishing and editing never delete collected responses.

Uploaded files are checked by their bytes, and saved by their kind. The cloud accepts an upload only when its first bytes match the type it declares (PDF, PNG, JPEG, WebP, Word, Excel, plain text and CSV; a text file may not carry NUL bytes unless it starts with a UTF-16 byte-order mark), and answers "That file does not look like the kind it says it is." otherwise, logging the declared type and the first eight bytes for the operator. The check lives in the cloud function, not in the public page: the page's own pre-upload refusal still reads only the declared type, because a browser cannot sniff reliably before the bytes move and the server is the authority. When you download a file from a response, Forms keeps the respondent's base name but takes the extension from the stored type, so "Invoice.pdf.exe" saves as "Invoice.pdf" and nothing a respondent typed can become a program on your computer.

Page routing stays visible while you work. On a multiple-choice answer that sends a respondent to a later section, Forms shows an amber Routing: answer → destination badge beside the question in every layout. Choose Edit to change the route without changing the layout. In that dialog Save routing keeps your change, and Cancel, Escape or clicking outside it puts the route back the way it was when you opened it. A route made invalid by moving sections is kept visible so you can repair it rather than losing the routing choice. If moving a page left a route pointing at an earlier page, the badge turns red and ends (goes back), and a red line under it says why in the same words Publish uses (routes can only go forward, so this form can't be published yet). The answer's destination dropdown shows that same page in red as <page> (goes back), selected but not pickable, instead of falling back to "Continue to the next page"; choosing a later page, Continue or Submit clears the red entry, the badge and the line.

Changes made elsewhere survive your typing. When an agent, the AI chat, the Wizard or the CLI changes a form while you have it open in the Editor, your next save keeps their questions and their look (theme, font, background, layout, welcome and ending text) alongside your own edit. Where you changed the same thing yourself, your version wins. A page's own "After this page" dropdown (under Edit on its badge) does the same: a saved route back to an earlier page shows as <page> (goes back) in red, selected but not pickable, instead of "Continue to the next page". A route to a page that was deleted stays amber and reads Broken destination. Duplicating a question deliberately starts the copy with no routes.

Deleting really deletes, so it is guarded: it takes the published form down first, then removes the form's auto-send rules and its stored responses. If the take-down fails, nothing is deleted. A delete without an explicit confirmation is refused and returns a preview of what it would actually do.

Auto-send rules are capped. A rule carries a match condition, a prompt template, and a daily cap on how many times it may fire in a day. The plugin keeps a run record for every attempt — fired, skipped because the cap was hit, skipped because the rule was tripped, skipped because it is disabled, or failed — along with the response it acted on and the session it started, so "why didn't that answer reach an agent?" always has an answer.

You choose which AI does the work. Two settings in the plugin's own Settings (at the bottom of the forms list), drawn from the engines your Omniscio can run, steer every AI feature: which AI writes (the question pipeline, the Consult door, the background picker and the design gallery), running on your Claude plan first and your own API key as a backup for Claude, with any other engine on its own API key, and which AI runs the agent session that receives a response. Both pickers are Forms' own drop-downs rather than the ones your computer draws, so their open list follows the app's look in every theme; arrow keys and typing move through the list, Enter or Space picks, Escape closes without changing anything, and a screen reader reads the control as a drop-down and announces the row you are on. "Use Omniscio's default" is always first and says what it resolves to; an engine that is not set up is greyed; under each picker the plugin says where that engine keeps your text (China-hosted engines, Qwen run by Alibaba from Singapore, OpenRouter passing it on to the model's company). A model Omniscio no longer offers still shows under its own name rather than being swapped for another. On an Omniscio without engine choice the door offers the default only and says Forms uses Omniscio's default AI there; a choice saved earlier stays on screen, marked as not used on that version, and is never rewritten. A choice is saved by the plugin's own background worker; if the save fails your previous choice stays and the screen says so, and if the worker is from before this was added it asks you to reload Forms.

AI words carry no em dashes. Everything the AI writes for you to read, from a Wizard step or an AI door reply to a critic's note, a suggested title or a world's name, uses commas, colons and full stops instead of em dashes and en dashes, with a plain hyphen only in a range such as 4-6. Your own words are never changed, even when the AI repeats them back.

Every way into a form offers a World. The New form screen says how each door offers one. In the Editor, a plain form with questions shows one "Give this form a World" card, and Choose a World opens This form's settings at the World row. The Wizard makes one World for the form by itself when its look step opens, from what you agreed in the earlier steps, and shows it first, marked "for you": it is made once per run, and Make another asks for one more. In the AI chat, once the AI has changed your form, one "Propose a World for this form" suggestion appears, and you can also ask in words, such as "make it gothic". A World the AI proposes always arrives as a card with a picture of your form, Apply and Undo: nothing changes until you press Apply, and Undo puts back the look you had. Each form is offered a World once: putting the offer away in the Editor or the chat puts it away in both.

The AI chat's "Revert everything this session did" takes back only the AI's work. It returns the form to how it was just before the AI's first edit, so questions you typed yourself before that edit stay. If you change the form by hand after the AI's last edit, even after leaving the AI tab and coming back, it asks first and writes nothing until you choose "Revert anyway". It keeps working after New conversation, and again for later AI edits after a revert. How it works, for anyone changing it: the "Data integrity: the Consult revert baseline and its fingerprint" section of src/plugins/forms/CLAUDE.md.

An AI edit keeps every question, however long the form. The AI chat, the editor's AI add and the Wizard can each add at most 40 new questions in one go, but they never drop questions you already have. If the AI ever answers with more than that, your form stays exactly as it was. How it works, for anyone changing it: the "Data integrity: the AI field cap bounds additions, never the maker's form" section of src/plugins/forms/CLAUDE.md.

The Wizard has two modes, and both avoid needless clicks. In Autopilot you describe the form in one box and press Start; it then runs all nine steps by itself, showing the step, a clock and a Stop button, and you check the finished form at the end (the screen where you would normally approve each step is skipped on purpose). If it stops, for any reason, it says why, offers one Carry on button and raises one inbox alert for stops you did not cause. In Guided, every question shows clickable A, B and C answers with the recommended one marked and a one-line reason, plus a box to type your own answer; clicking an answer moves on and the last click sends. Guided still asks you to approve each step.

A finished Autopilot run has a way back. "Undo this run" sits inside the "Not quite right?" note on the finished screen, and beside Try again on the stopped screen. It asks first: the box names how many questions the form had before the run, lists what goes back (the questions, title and intro Autopilot wrote, and the look it picked) and what stays (answers people have already sent, and your live link if the form is published), and warns you when the form has changed since the run, because those changes go back too. Undo returns the WHOLE form to how it was before the run started, not just Autopilot's part, and it cannot be redone, though you can run Autopilot again whenever you like. If you opened the AI chat after the run, the way back is gone: the screen hides the button and says why rather than offering one that does nothing. It is never offered while a run is still working, because a run that has written only its first steps can only be partly undone.

How the way back works, for anyone changing it: each run keeps its OWN copy of the form as it was before the run started, stored per form under the run-snapshot key in src/plugins/forms/src/cloud-shared/form-local-state.ts. It is deliberately separate from the AI chat's session copy. The chat's copy keeps whatever older copy already exists, so if the chat had edited the form before a run, Undo would land on the chat's older starting point instead of the run's; and clearing the chat's copy when a run starts would break the chat's own revert. So the run takes a copy it owns and replaces it every run, and the chat clears the run's copy when it starts its own fresh baseline, which is why the button then disappears with a reason. The run also records a fingerprint of the form as it left it (afterHash on RunBaseline in src/plugins/forms/src/ui/lib/ai-edit.ts), written once when the run settles; it is empty while the run is still going, and for a run whose page closed before it could settle. That fingerprint is what lets the confirm box say honestly that the form changed since the run: comparing against the before copy alone cannot tell a hand edit from the run's own writing, because the run always moves the form away from its before copy.

Leaving while the AI works. Switch to another Forms tab (Editor, AI, Wizard) or to Settings while the AI is working and it keeps going: come back and you see it still working, then the result, with nothing asked or paid for twice. While the Wizard reads your answers it says "Reading your answers..." in place of the questions. Opening another plugin, popping Forms out or the phone layout closes Forms entirely, and the AI's reply is lost. When you come back, Forms reopens the form and the tab you were on and says so honestly ("This step did not finish", "Your last message did not get a reply", "That request did not finish") and keeps your answers or words, but it never sends again by itself: you press "Try this step again", "Send again", "Propose" or "Ask AI". An AI door change that lands after you edited the form elsewhere is not applied, so your own edits are never overwritten. "Start over" in the Wizard and "New conversation" in the AI door wait until the AI has finished.

Long AI runs always show they are alive, and a stop is never silent. Under every AI step (the Wizard, the AI chat, the design gallery, the critics, the background picker, the World maker) a line says "Working: <what>", how long it has taken (counting up each second) and the usual time. Past twice the usual time it says "Still waiting" and when Forms will stop waiting. The AI gets four minutes per call. If it does not answer, or the host refuses (a missing key, a spent daily cap, a retired model), the line says "Stopped", the reason in plain words and what to do next, and one alert appears in the Omniscio inbox; nothing is asked again unless you ask. A finished answer that landed while you were away is kept until you see it, so a Forms page that was closed and reopened shows it instead of paying again. When a run of twenty seconds or more finishes while you are looking elsewhere, Omniscio shows one notification. Publishing and the other cloud steps show the same counting line while they wait. If this Omniscio build offers a run signal, Forms uses it to keep a busy screen alive; if it does not, nothing is claimed that is not true.

A response is never quietly dropped on its way to your rules. Before a sync saves a new response it writes the response down, then offers the saved ones to your auto-send rules one at a time, so one fault cannot stop the rest. Anything not handed over is offered again at the start of the next sync (a repeat never starts a second agent for the same rule and response). Each new answer is stored once, even when two copies of Forms pull it at the same moment; answers saved twice before that fix are left as they were, never deleted. After three failed tries the response is marked stuck and one inbox alert a day says how many. When a rule's agent session cannot be started, one alert per rule per day gives the host's own reason. Sending many responses at once shows "Started N of M", checks a send that was lost track of against the response's stored session before saying it "may or may not have started", and if Forms was closed mid-send, the Responses screen says on return how many started, with a Dismiss.

Since Forms 0.15.0:

  • Publishing asks who a form is for: adults or a general audience, teens aged 13 to 17, or children under 13. A form for children under 13 cannot be published, and an agent's publish is refused until you have answered.
  • A form can wear a designed world (Atmospheres): one of eight, chosen in This form's settings or the Wizard's design step and tuned with two sliders, ambience and ornament. The AI can also propose one from a description, which changes nothing until you choose it.
  • Answers leave the cloud after 90 days unless you choose 6 months, 1 year or 2 years under "Keep answers for" in This form's settings. Your own copy of every answer stays on your computer.
  • Publish, Publish changes and Reopen first check Forms' background worker. If an update left it on the previous version, or it does not answer, they refuse and ask for a restart rather than publish the form without its world. Close and Unpublish are never held.
  • A World counts as published only once the cloud says it kept it. If a publish reaches a Forms cloud that does not store the World or background, the form reads "Live, unpublished changes" and Publish stays, so you can send it again once the cloud is updated. A form published to such a cloud before this fix still reads up to date: change anything small and publish once more. An agent's POST publish reply names what the cloud did not keep in notKept.

Since Forms 0.15.1:

  • The version shows beside the Forms title at the top of your forms list, with New form beside it (under it since 0.16.0), and nowhere else. A warning appears under it only when Forms' background worker is out of date or not answering.
  • One button per job. New form lives in the forms list, New rule and Refresh in their panel bars, and an empty form shows a single palette headed "Add your first question".
  • The Wizard says where you are in words: "Step 2 of 9" and "Question 2 of 4", with "Previous question" to go back to an earlier answer. Its questions come first, with at most one short sentence above them.
  • AI text reads as formatted text, and a long reply folds behind "Show all". Each auto-send rule shows its instructions, the words its agent is given, before you arm it.
  • The AI door's own heading now matches its New form card, "Talk it through with AI" (its tab still says AI), and every control you can click shows the hand cursor.
  • AI work survives leaving and coming back, and Forms reopens on the form and tab you were on (see "Leaving while the AI works" above).

Since Forms 0.15.2:

  • Describe your own world accepts ordinary ideas. An ordinary description such as "a wedding fair" or "a beach cafe" gets a world: a colour that would be hard to read moves to the nearest readable shade of itself, so the world keeps its look, and a description is turned down as hard to read only when no shade of its colours can be read.
  • AI words carry no em or en dashes (see "AI words carry no em dashes" above), and the words you type are never changed.

Coming in the next Forms release:

  • Describe your own world never ends in a dead end. Whatever you type, you get a World card: the AI's own World when it reads well, otherwise the closest of the eight designed Worlds with one quiet line on the card saying why (the AI could not be reached, it did not describe a world this form can draw, or its own world would have been hard to read). Apply and Undo work as always. In the Wizard the line points at that designed tile among the ones already there. Only an empty description is still turned down, before anything is asked.
  • An AI World is repaired rather than refused. A part name the model spelled its own way is read, a slot it got wrong is filled from the closest designed World, body and small text never use a script or blackletter face, and a border that would vanish into the card is moved to a visible shade. Colours are repaired a quarter point past each readability floor, because the built page draws pixels a little darker than the palette says.
  • Worlds are proved on awful descriptions. A browser proof draws 35 awful descriptions (empty, one word, hostile, contradictory, extreme colours, three languages, junk) on the real public page at phone and desktop, in every layout, light and dark, and checks readability, overflow, tap targets, faces, borders and the security policy; see the plugin's developer notes.

Since Forms 0.16.0:

  • Every way into a form offers a World (see "Every way into a form offers a World" above), and This form's settings calls its look row World instead of Atmosphere.
  • The form's header has three rows, and they follow the space Forms has, not the window. The title, which you edit in place, with its status under it (Draft, Live, Live with unpublished changes, or Closed); then Preview, Share, the one coloured action (Publish, Publish changes or Reopen) and Form actions, the three-dot button; then Editor, AI and Wizard, with Responses and Rules beside them.
  • When the header is narrow, controls move rather than shrink. Responses and Rules move into Views; with larger text, AI and Wizard move into Assistants, and on the smallest layout Navigate holds both. Preview, and Share when a coloured action is showing, move into Form actions. Editor is always in view, and no label is ever cut off. At 560px of width or less the phone layout below takes over instead.
  • The forms list has one Status drop-down (All statuses, Live, Draft, Closed) under the search, in place of the four status chips.
  • New form is a full-width button under the Forms title and version.
  • Forms settings is at the bottom of the forms list, not a tab. It holds the choices that apply to every form and opens even with no form selected, without creating one. This form's settings, inside the Editor, is still where one form's look and behaviour live.
  • The forms list sits beside your form only when Forms is at least 960px wide. Narrower, the list fills Forms until you open a form, then opens over it from Back to your forms at the top left. Your search and filter come with it.
  • Responses shows its total inside the view; the Responses button carries no number.
  • Your own words wrap in the Editor. A question, its description, an option, a scale's end labels and the welcome, button, ending and "Who is asking" words grow onto more lines instead of running off the edge. Enter adds no line break, and a pasted one becomes a space.

Phone and drawer layout (Forms 1.1.0). At 560px of width or less, measured on the space Forms actually has and never the window, every screen takes a layout made for a thumb. Wider than 560px nothing changes.

  • The form's header is two rows. The title with its status under it, Publish and Form actions share the first row; Editor, AI, Wizard, Responses and Rules are all in the second, with no Views menu. Publish changes reads Publish, and the amber "Live, unpublished changes" line stays under the title. Preview lives in Form actions. Share stays beside Publish down to 431px and moves into Form actions at 430px and below. With larger text the header keeps its Navigate layout.
  • Only one destination looks selected. While Responses or Rules is open, no Editor, AI or Wizard tab is lit as well. This holds at every width.
  • The Editor has Questions, This form and Preview tabs in place of the pinned This form's settings bar and the docked preview. Questions keeps your open cards and typing while you look at the other tabs. Question cards run the full width, every button on them is 44px, and Move up and Move down buttons reorder a question without dragging.
  • AI has Chat and Preview tabs. The typing box stays under the chat, and a dot appears on Preview when the AI changed your form while you were reading the chat.
  • The Wizard has less padding, 44px buttons, and a thin bar showing the step you are on.
  • Responses are cards, not a sideways table. Tap a card to open the answer; tick cards to send them to agents from the same bar.
  • The forms list puts New form beside the title and the search and Status on one line; rows, Archived and Forms settings are 44px. New form is a tighter card that fits without scrolling.
  • The share panel shows the whole link, wrapped onto more lines instead of cut off, and says the form is live once, in its title.

Two settings, named by what they cover (Forms 1.1.1). Forms has two settings doors and each now says its scope in words, so neither can be mistaken for the other.

  • Forms settings is the door at the bottom of the forms list. It reads "Forms settings" with "Applies to all your forms" under it. Its panel opens with the same title and a scope chip, and holds the AI model, the AI that handles incoming responses, and your data in Omniscio's cloud.
  • This form's settings is the button in the editor. It reads "This form's settings" with "Applies to this form only" under it. Its panel is titled the same, with the scope chip and the form's name beside it (no name is shown while the form has none), then the look, layout, wording and "Keep answers for" choices. On a phone there is no button: the third editor tab is called This form and opens that same panel.
  • The collapsed forms strip shows the same door as "Forms settings" on hover.
  • Where the words live: every one of these strings goes through the plugin's rendererT copy path (keys rail.settings, scope.allForms, scope.thisForm, builder.formSettingsTitle, builder.tabLook), and the shared scope chip is ScopeChip.tsx. The tab's key keeps its old name; its stored value look and its element ids did not change.

The crash screen is ready for translation. When the maker hits an unexpected error it shows "Something went wrong" with a plain recovery sentence, a line saying the details went to the log, and a Reload button, and never the error or its stack. Those four texts now go through the plugin's rendererT (keys errorBoundary.title, errorBoundary.body, errorBoundary.logNote and errorBoundary.reload, with the product name filled in), so a catalog can translate them. The English is unchanged, and tests/ui/error-boundary-detail.test.tsx proves both the wording and that each text reads through the seam.

Settings search finds the cloud data controls. Typing "erase", "disconnect" or "cloud data" in Omniscio's Settings search now finds Forms: three entries, "Your data in Omniscio's cloud", "Disconnect Forms from Google" and "Erase all cloud data", are declared in the manifest under ui.settingsSearch. Choosing one opens Forms, shows Forms settings and puts focus on the cloud data card. Opening a result only shows the card: it never disconnects, never erases and never opens the erase confirmation. The two AI pickers were already found through the manifest's settings list. If you have unsaved changes, the same "Your changes are not saved" question appears before Forms leaves the editor. An older Omniscio without this field simply does not list the three entries.

Editing fields replaces the question list. When a form is updated, the field list is replaced whole rather than merged. Removing a question you did not ask to remove is refused; removing one on purpose means leaving it out and naming it as a removal.

The assistant can point at Forms' controls. The manifest lists twenty-one controls in uiAnchors (New form, search, the status filter, Forms settings, the three start cards, the form title, Preview, Share, Publish, Form actions, Add a question, the AI chat box, the public form link, the two AI selects and the cloud data section with its Disconnect and Erase buttons), and the page marks each with data-ui-anchor. On a narrow window Preview and Share sit inside the open Form actions menu and are marked there. Omniscio shows the assistant only the listed words and the control's position, never text from the page. A control that is not on screen, or not listed, cannot be pointed at. The Erase button is described as erasing the data of the connected Google account only. tests/ui/ui-anchors-manifest.test.tsx, tests/ui/ui-anchors-states.test.tsx and tests/ui/ui-anchors-cloud.test.tsx keep the manifest and the markup in step.

Escape closes one thing at a time. In Forms, one Escape press closes only the topmost open layer: the preview, a confirmation, the run-undo list, the send-to-agent dialog, the publish panel or a dialog. Holding Escape closes one layer, not several. An Escape that cancels input-method typing (Japanese, Chinese, Korean), or that a control inside already used, such as clearing the forms search box, closes nothing. Nothing about how Forms looks changed.

How plugins are found, installed and enabled is on Plugin marketplace, and how a plugin adds a sidebar row like Forms is on Plugin UI access. Where a plugin's own options live is on Plugin settings panel, and the CLI-route surface these routes appear in is Plugin CLI discovery.

Last verified 2026-11-03