Omniscio

Mission Control (new)

Mission Control (new) is the rebuild of Mission Control while it is being built, for testing only. It stays hidden until you turn on its Lab switch, and it starts empty. Your current Mission Control is not touched.

On this page

What it is

A separate copy of Mission Control that is being rebuilt from scratch. It has its own storage and starts with no boards. Right now it does the basics: make a board, add items and columns of five kinds (text, status, number, date or people), put items in groups, type into a cell, say who is on an item, delete an item, set the board rules (which status label means Done, which group means Done, which number column holds effort, which date column holds the due date), save filters that narrow the board, export the board as a CSV file, and publish the board as a web link.

Where to find it

  • Settings → Lab → Mission Control (new). Off by default. While it is off, nothing about the new copy appears anywhere.
  • With the switch on, a Mission Control (new) row appears in the Productivity group of the sidebar, right beside Mission Control. Open it to see your boards.

How it behaves

  • It is in progress: boards, items, columns, groups, people, the board rules, saved filters, the CSV export, the question box, bringing boards over, Omni's approval cards and the Your data page with its confirmed delete exist so far. Boards are kept on this computer for the signed-in Omniscio user, and you need to be signed in to use it.
  • The board is one table. Each group is a section row with its items under it; the Item column and the header row stay put while the rest scrolls sideways, so a board with many columns never widens the window. Every column starts at a width that fits its kind; drag the right edge of a column header to resize it, and the board keeps that width for everyone who opens it. Double-click the edge to restore the default width, or focus the edge and press the left or right arrow key.
  • The tool strip beside the board name holds Filter, Group, Column and Rules, each opening one panel under the strip (pressing another closes the first), and Export CSV.
  • Column kinds. Open Column in the tool strip and pick the kind beside the new column name: Text, Long text, Status, Number, Date, People, Checkbox, Rating, Link, Email or Phone. A status column holds the labels an item moves through; a number column holds a number such as hours or points; a date column holds one day, picked from a calendar, and can be left empty; a people column holds who is on the item. Long text keeps its lines and edits in a multi-line box (leaving the box saves, Escape cancels). A checkbox ticks or clears with one click. A rating is five stars: click a star to set it, click the lit star to clear it. A link opens in a new window and the pencil beside it edits the address; an address that does not start with http:// or https:// is refused on the spot and never saved. Email and phone are text that brings up the matching keyboard on a phone. Every kind is stored as one piece of text, which is what the CSV export, the published page, the filters and Omni's facts show: a checkbox is yes or empty, a rating is 1 to 5 or empty, a link is its address or empty. Checkbox, rating, status, priority and dropdown columns can be filtered; a blank cell passes every filter, as always. On the command line, column.add takes columnKind as any of text, long-text, status, priority, dropdown, tags, checklist, number, progress, date, timeline, week, world-clock, country, location, people, checkbox, rating, link, email, phone, created-time, last-edited-time, item-id, created-by or last-edited-by, and cell.set takes the stored text (the server refuses a wrong shape as not saved). The rest of the current copy's column types follow in the next runs of this step.
  • Timeline, Week and World clock columns. A timeline cell is a start and an end date field side by side; once both are set the cell saves them together as one span (the earlier day first, whichever field it was typed into), and clearing either field clears the cell. Under the fields the cell says how the span stands against today: "3d left", "Today", or "2d late" in red. A week column is the same cell under its own name, as in the current Mission Control. The cell stores the span as YYYY-MM-DD/YYYY-MM-DD, which is what the CSV export, the published page and Omni show; a span whose days are out of order or not real days is refused and never saved. A world clock cell is a searchable pick of the time zones this computer knows, each shown as its city with the current time there (refreshed every half minute); the pick saves the zone name, such as America/Chicago, which is what every reader shows; a zone the computer does not know is refused. None of the three can be filtered on, as in the current copy. Boards brought over carry a source timeline or week as the span when both days are real (a half span comes over empty) and a source world clock as its zone when the computer knows it. On the command line, cell.set takes the span or the zone name as the stored text.
  • Country, Location and Tags columns. A country cell is a searchable pick of every country, each shown as its flag and its name in the app language; the pick saves the two-letter country code (such as US), which is what the CSV export, the published page and Omni show, and a code that is not in the list is refused. A location cell shows its place with a map pin; clicking it opens a field that searches OpenStreetMap while you type (after a short pause, up to five places listed under the field) and picking one saves that place name, while Enter or leaving the field keeps exactly what you typed and Escape cancels; when the lookup cannot be reached the cell says so in plain words and the typed text still saves. The lookup runs in the main process (GET /mc2/places?q=, IPC mc2:find-places): only the typed text, the json format, the five-place limit and the app User-Agent are sent, the query is never logged, and repeats within five minutes are answered from a small in-memory cache. A tags cell holds any number of tags as chips, each tinted by its own name so the same tag is the same color everywhere; the plus opens a typed field (Enter adds, Escape closes) and lists the tags already used on this board that the item does not carry; each chip has a remove control. Tags are stored as a list like a dropdown cell ({ texts } through cell.texts.set), a plain cell.set on a tags column is refused, and the CSV shows them joined with commas. None of the three can be filtered on, as in the current copy. Boards brought over carry a source country as its code when the list knows it, a source location as its label, and source tags as the list. On the command line, cell.set takes the code or the place text and cell.texts.set takes the tags.
  • Checklist columns. A checklist cell holds a list of steps, each a short text with a done tick. The cell shows a small progress bar with how many steps are done out of how many (or Add steps when there are none); clicking it opens the list: tick a step to mark it done, edit its text (Enter or leaving the field saves, an emptied text removes the step, Escape puts the old text back), take a step off with its remove control, or type a new step in the field under the list and press Enter (Escape closes the list). Every change saves the whole list at once, each step text once per cell, at most fifty steps. The CSV export, the published page and Omni show the progress as done/total (for example 2/3); a checklist never counts toward the board's Done rule and cannot be filtered on, as in the current copy. Boards brought over carry a source checklist's items as steps (an older label reads as the text). On the command line, cell.checklist.set takes the list as steps: [{ text, done }]; a plain cell.set on a checklist column is refused.
  • Progress, Created time, Last edited time and Item ID columns. A progress cell is a bar with a small percent field: type a whole number from 0 to 100 (a trailing percent sign is fine) and press Enter or leave the field to save; a blank clears; anything else shows "Enter a whole number from 0 to 100" and saves nothing. Every reader shows the saved number as 42%. Created time, Last edited time and Item ID are filled in by the board and cannot be typed into: a created time is the moment the item was made, a last edited time is the latest of its creation, its group move and any cell change, and an item ID is the item's number on its board (counted from 1 in creation order, padded to three digits, never reused after a delete). On the screen the two times read in your own language, date and time zone; the CSV export, the published page and Omni carry them as UTC timestamps and the ID as the padded number. None of the four can be filtered on, as in the current copy. Boards brought over keep a source progress as the whole number; a source created time, last edited time or item ID is not carried, because the new copy fills those from its own items (so a brought-over item's created time is the moment it arrived). On the command line, column.add takes the four kinds, cell.set takes the progress number, and a cell.set on a filled column is refused.
  • Created by and Last edited by columns. Both are filled in by the board and cannot be typed into. Created by is the person who made the item; Last edited by is the person whose cell change on the item is the latest, or the creator when no cell has been changed (a group move does not count, because the new copy does not record who moved an item). On the screen each reads as You when it is you, as Former member when that person was erased, and otherwise as the person's id; the CSV export, the published page and Omni carry the id (or Former member). Neither can be filtered on, as in the current copy. An item made before this run has no creator on record and shows an empty cell rather than a guess. Boards brought over do not carry a source created by or last edited by: the new copy records who brought the items over. The creator is a place on the privacy map: erasing a person leaves Former member as the creator of their items, and Your data counts "Items you created". On the command line, column.add takes created-by and last-edited-by, and a cell.set on either is refused.
  • Dropdown columns. A dropdown column holds a list of options and an item can carry any number of them at once. A new dropdown column starts with no options; add them with Edit labels in the Column panel, where a dropdown shows no color pick (its options are plain). The cell shows each chosen option as a chip with a remove control, and its plus lists the options the item does not have yet, each a button that adds the option and saves at once; when every option is already on the item the list says so. The cell stores the chosen option names as a list, so the CSV export, the published page and Omni show them joined with commas, the filter choices list each option once, and a filter rule keeps an item when any of its options is in the rule (a blank cell passes, as always). Renaming an option through Edit labels renames it inside every cell that holds it; removing one leaves its cells reading the old name. A board brought over from the current Mission Control, or from an outside place, arrives with each dropdown column's options and each cell's chosen options. An agent that sets a dropdown cell waits for a person like any other cell change, and its card names the options. On the command line, cell.texts.set takes itemId, columnId and texts, a list of up to fifty option names; a plain cell.set on a dropdown column, or cell.texts.set on any other column, is refused as not saved, and the board read carries the cell as { texts }.
  • Labels on status and priority columns. A status or priority column carries its own list of labels, each a name and a color. A new status column starts with Working on it (orange), Done (green) and Stuck (red); a new priority column with Critical, High, Medium and Low in the current copy's colors. A cell in such a column is a colored chip: click it to pick one of the column's labels or No label, and the pick saves at once. The cell stores only the label's name, so the CSV export, the published page, the filter choices and Omni's facts show the same words they always did. In the Column panel every status and priority column has an Edit labels button opening the editor: rename a label, pick its color from twelve named colors (Done green, Working orange, Stuck red, Bright green, Egg yolk, Sunset, Purple, Indigo, Bright blue, Aquamarine, American gray, Brown; a color that came from elsewhere is kept and shows as Other color), remove one, or add one, up to fifty per column; Save labels sends the whole list as one change, and a label with no name or two labels with one name stop the save before anything is sent. Renaming a label renames it in every cell that held it and in the board's Done rule; removing one leaves its cells reading the old name until you change them, and such a cell still shows that name on its chip. A status or priority column whose list is empty (one made before labels existed) keeps the typed field. In Rules, once the chosen Done column has labels, the Done label is picked from them instead of typed. A board brought over from the current Mission Control, or from an outside place that exports label settings, arrives with each column's labels, and its first import also sets the Done rule from the label the current copy marks as done. On the command line, column.labels.set takes columnId and labels, a list of { text, color } with color as #RRGGBB; a label that also carries was with its old name is a rename and rewrites the cells. A list on any other kind of column, a repeated name or a bad color is refused as not saved, and the board read lists labels on every column.
  • Board rules, behind Rules in the tool strip. Choose a status column and type the label that means Done (only that exact label counts), choose the group that means Done, choose a number column that holds effort with how it is shared when an item has several owners, and choose a date column that holds the due date. Not set is an answer: a board with no Done label says so instead of guessing.
  • Filters, behind Filter in the tool strip, which also shows how many are saved. Each filter picks a status, number, date or people column and ticks the values to keep; the choices are the values that column already holds on any item (for a people column, the people on the board), so there is nothing to type. Add filter adds another row, Save filters keeps them for the board, and a filter with nothing ticked cannot be saved. Saved filters show as chips under the tool strip, and the x on a chip removes that filter at once. An item passes a filter when its cell holds a ticked value or is blank (for a people column, when any ticked person is on it or nobody is); a filter on a column you cannot see, or the board no longer has, changes nothing. Values compare exactly as stored, so a number typed as 3 and one typed as 3.0 are different values.
  • Export CSV, in the tool strip. It saves a file named after the board holding exactly the rows and columns on screen, each cell as stored (a blank stays blank, 1.25 stays 1.25). When the saved filters leave nothing, the board says "There is nothing to export" instead of saving an empty file. The command-line tool gets the same file from GET /mc2/boards/:boardId/export as JSON with fileName and csv, and answers 422 nothing-to-export when there is nothing.
  • The summary line under the board name starts with "Showing N of M items" whenever a filter is saved, then says how many items are done, or that no Done label is chosen yet, the effort total, and, once a due date column is chosen, how many items are due today and how many are overdue; the done, effort and due figures describe the items on screen. The total counts in hours when the column title says hours (or hrs), otherwise in points, and it says how many items were not estimated. A blank or non-number effort cell counts as zero and is marked Not estimated. Once three items have finished in the last eight weeks (the day the status cell became the Done label, or the item entered the Done group), the line ends with the board's pace, "Finishing about N items a week (early read, last 8 weeks)": finished items per work day over the window, said per five-day week, with how settled the read is; with fewer than three it says nothing, and today it always reads as an early read because the board does not yet know when its people started.
  • The done mark. An item whose status cell carries the Done label shows a check mark beside its name.
  • Due today, overdue and gone quiet. With a due date column chosen, an item shows "Due today" in red under its date on that day and "Overdue by N days" in bold red after it, counted in whole days in your own time zone (a date is never overdue on its own day). An item that is due today or within the next seven days, not late and not done, and that nobody has touched (no cell changed, no group move) for five work days shows "Quiet N work days" in amber beside those words; work days are Monday to Friday for the people on the item, so a weekend never counts, and done items and far-off items are never quiet. The three marks are plain colored text, no icons or pills (Kaylin's choice, Nov 13). Upcoming items and done items show no due words. A date that is not a real day cannot be saved.
  • Groups. Group in the tool strip adds a group; the first group created on a board takes in the items the board already has. Each group is a section row showing its name, a Done group badge when it is the Done group, how many items it holds, an Add item button that adds an item into that group, and a menu with Rename. A board with no groups is a plain list of items with an Add item field under it. Each item has a menu at the end of its row with Move to each other group, and Delete. An item in the Done group counts as done; moving an item into the Done group gives it the Done label, and moving it out puts the other label back. On the command line the same changes go to POST /mc2/changes with kind set to group.create, group.rename, item.group.set or board.done-group.set, and the board read, GET /mc2/boards/:boardId, lists groups, each with the ids of its items on screen.
  • Ask about this board. The question box above the board answers from the board's own facts: how many items and how many are done, how many are due today and overdue (naming each overdue item and how late it is), and the effort total with how many items are not estimated. Every number in the answer comes from the board; a sentence whose number the board does not hold is held back and never shown. Anything the answer could not read, such as a column you may not see, is listed under "I couldn't check" with the reason, never counted as nothing. The "Based on" line says which board the answer used and as of when, and opens to list what was read. When Omni's AI is on and your AI comfort level is Medium or High (the same switch and level as the current Mission Control), Omni reads your question and writes the answer from the board's counts alone, never its text; every sentence is checked against the board first, a sentence the board does not hold is dropped and the card says how many were dropped. The pill at the top of the card says who answered: Omni, with the Omni icon, or Facts only with the reason (Omni's AI off, a Low comfort level, or an Omni answer that did not hold up). The setting that turns the "Based on" line off and the "fix it in a session" button come with later steps. On the command line the same answer is GET /mc2/boards/:boardId/answer?question=...&timeZone=....
  • Shown and hidden columns. The Column panel starts with a Shown columns checklist, one box per column in board order; its tool label says how many are hidden. Unticking a column tucks it away from the board, the CSV export and the published page, because those show exactly what you see. It is tidiness, not privacy: the cells stay, a saved filter on that column still applies, the summary counts still include it, and Omni can still read it. Tick it again to bring it back. On the command line, a column is hidden or shown with a column.hidden.set change at POST /mc2/changes (columnId, hidden true or false), and the board read lists hiddenColumns beside columns.
  • Published links. Publish in the tool strip opens a panel. Publish a link freezes exactly what the board shows you at that moment, saved filters applied and private columns left out, into a web page anyone with the link can open: the board name, "Published from Mission Control · as of (date and time) · N items", the items as a table with a row per group, the cells as stored, and a footer saying the page is a snapshot. It carries no quiet or due words, because those are about today and the page is about one moment. The panel lists every link of the board with a Copy control, who published it and when (in your own clock), Update link when you published it (the same address, replaced with what the board shows now and a new "as of"), and Publish a new link for a second address. When the saved filters keep no item the panel says there is nothing to publish; when Shares cannot take the page it says nothing changed and to try again; a link removed from Shares cannot be updated and says to publish a new one. On the command line: POST /mc2/boards/:boardId/links publishes (201 with the link; 422 nothing to publish), GET /mc2/boards/:boardId/links lists, and POST /mc2/links/:linkId/update refreshes the same address (403 for anyone but the publisher, 404 when the link is gone). Your data counts the links you published, and Delete my data removes their records.
  • Omni asks before bigger changes. When Omni (or any agent working for you) wants to change a board, your settings decide: a status change runs on its own, while moving a due date, assigning a person or deleting an item waits for you as a card under Needs your OK at the top of the panel and, at the same moment, as a card in your Inbox under the Mission Control (new) section (one card per waiting change, Approve and Deny on the card; "Approve and remember" is on the board only; a card decided on either surface leaves both), in plain words ("Omni wants to set "Due" of "Record the demo" on Launch plan to "2026-11-14"."). Approve makes exactly that change, once, and only what you yourself could do on that board; a second click says it was already decided. Approve and remember also stores a permission for the one thing the change names, so the next such change on that item or person runs on its own; it never appears on a delete. Deny drops the card. The same change sent again while it waits makes no second card, and a 26th waiting change is told "too many" and makes none. Omni settings, beside the panel title, shows the table of what Omni may do on its own (status, comments and reminders run; due dates, assigning, archiving, deleting, access and messaging outside the team ask first; owners and admins move a row), your own Always ask me first list (starts with deleting, access, messaging outside the team, archiving and assigning; a ticked kind asks you even when the table says it runs; if you had chosen Only suggest in the current Mission Control, every kind starts ticked until you save the list), and What you told Omni to remember, each permission with Revoke. A change of a kind the table does not know (text cells, new items, groups, columns, filters, rules) always waits. On the command line an agent proposes with POST /mc2/proposals (agent and change; 202 while it waits, 429 when too many wait), reads GET /mc2/waiting, decides with POST /mc2/waiting/:changeId/decide (decision: approve, approve-and-remember or deny), and the settings are GET /mc2/autonomy, PUT /mc2/autonomy/:kind, PUT /mc2/always-ask and DELETE /mc2/permissions/:permissionId.
  • The Omni panel. On a desktop-width window with the AI Project Manager feature on, the same collapsible Omni panel the current Mission Control docks on its right edge sits on the right of Mission Control (new) too: a thin rail with the Omni icon when collapsed, and when open the Omni session pane with New session and Open the full page. A Show Omni / Hide Omni button in the page header toggles it (the rail and its chevron work as well), and it remembers the same width and collapsed state as in the current Mission Control, because it is the same panel. Omni itself keeps its own sidebar entry and is not rebuilt inside Mission Control (new); its suggestions about these boards arrive as the Needs your OK cards above.
  • My work calendar. The My work calendar button beside Omni settings and Your data opens a form saved for you only: the days you work (seven toggles, at least one on), your time zone (your computer's zone unless you pin one), your days off one at a time as a full or half day, and the day you started. The board uses it quietly: "quiet" counts only your work days and skips your days off, "Due today" and "Overdue" follow your pinned zone on every computer, and once you have finished three or more items you are on over at least ten of your work days the summary says "You finish about N items a week" with a certainty that grows from your start day (early read under 30 days, firming up under 60, nearly settled under 90, then settled); items with nobody on them keep the standard Monday to Friday week. On the command line: GET /mc2/calendar reads it and PUT /mc2/calendar saves it (400 for a day that is not real, an unknown zone, no work day or a repeated one). Your data says whether a calendar is saved, and Delete my data removes it.
  • Your data. The Your data button beside Omni settings opens a page that counts what the new copy holds for your account: boards, items and cells, the cells you last changed, the items you created, the people columns naming you, and your Omni settings. Nothing in the copy names you by name or email; it stores your Omniscio id, and your boards sit under an opaque workspace id that never contains it. Delete my Mission Control (new) data is its own step on that page, never a side effect of the Lab switch: it says what goes (every board, item, cell, group, import record, Omni setting, permission and waiting card for your account on this computer), that your current Mission Control is not touched, and that there is no undo. Type "delete my mission control data" to turn the button on; a near miss deletes nothing. A receipt says what was deleted, by count. On the command line the same step is DELETE /mc2/my-data?confirmation=... (the typed phrase or delete-my-mission-control-data; the server reads no body on a DELETE, so the phrase travels as the one query key), GET /mc2/my-data reads the counts, and POST /mc2/erasures erases the signed-in person the way a former member will be erased once boards are shared: every place that named them gets one fixed "Former member" marker, their own settings and cards are deleted, the erase is recorded as a salted digest so a restore keeps it, and the log never names them.
  • Bring my projects over. The button under the board list opens three steps. Step 1, where are they now: a tile for each place the current Mission Control can already import from (Monday.com, Trello, Asana, Jira, Linear, Notion, ClickUp, Airtable, Google Sheets, Excel and CSV), each saying what it needs (an API key typed into the fields shown, a sign-in, or a file chosen through the normal file window), and a last tile for the current Mission Control on this computer, which needs nothing. Step 2, which projects: "Next: show my projects" connects once and lists every project the place names, whatever the source calls it, with its kind: a board-like project (a board, list, database, base, table or sheet) is ticked and comes over now; a kind the new copy cannot hold yet (a document, form, goal, portfolio, sprint, dashboard, whiteboard, or a kind only the source knows) is shown as "Document: coming" and so on, can still be ticked, and is kept on the record rather than dropped. If the place will not connect, its own words are shown and you stay on step 1. Step 3, what arrived: each project with "Complete: N items", or "Import incomplete" with the kinds not brought over yet or why the listing stopped, and "Finish import" where that helps. A board comes over with its groups, its columns (status and priority become Status, numbers and rating become Number, date stays Date, people stays People, everything else becomes Text), its items in their groups and each cell's text (people cells come over empty for now). A key is used for that one run and never stored; a chosen file is handed over as a short-lived token, never a path. A board whose import stopped before every item arrived, or that still has a kind coming, is marked "Import incomplete" in the board list with the kinds named under it, and "Finish import" adds only what never arrived and never changes or removes what is already here. A board brought over completely is never brought over again, so running it twice doubles nothing. The current Mission Control tile is the one place the new copy reads the current Mission Control's own storage; it never writes it, and the outside places are read through its import framework without touching its import jobs. On the command line: GET /mc2/import-places lists the places, POST /mc2/import-places/:place/connect (credentials or fileToken in the body) lists the projects (422 when the place will not connect, 404 for a place nobody offers), POST /mc2/imports/projects (place, the same input, and projects as sourceId, name, kind) brings the chosen ones over, POST /mc2/imports/bring-over brings every current board over, and POST /mc2/imports takes a board payload from any other source (a source name and boards with their groups, columns and items by source id) under the same rules.
  • People columns. A people cell shows a chip per person: You for yourself, Former member for someone who was erased. The x on a chip takes that person off the item, and the plus opens a picker listing who can be put on it, which for now is the board owner alone, and the picker says so. Only someone who can open the board can be added. The CSV export shows the person ids for now. On the command line, add a column with columnKind: "people" and set who is on an item with kind: "cell.people.set" and personIds.
  • A change shows at once with a "Saving..." marker. If it does not save, it goes back and says so in one line, with a Try again button when trying again can help.
  • Deleting an item asks first, and a deleted item is hidden from the board.
  • It never reads or changes the current Mission Control, its boards or its settings.
  • Turning the switch off only hides the row.
  • Mission Control — the current Mission Control, which stays exactly as it is.

Last verified 2026-11-12