The home page knows you're signed in
When you are signed in, the home page shows your hero, or your GitHub photo, beside Continue your game, one click back to the game. Visitors who are not signed in see the page as before.
What’s new in Omni Loop
Every PRD the loop ships, in plain words. Newest first.
Week of 28 Sep 2026 · 71 releases · 71 PRDs
Omni Loop on its own domain
Omni Loop now has its own domain, omni-loop.xyz. Search engines and link previews keep it, and the site has a robots file and a sitemap. Signed pull requests and new installs link to it. The old address keeps working, and the guide says how to switch an installed repository.
The home page shows the loop, your customers and the game
The home page draws the loop as the docs do, shows how your business, products and personas steer the agents, and invites your team to build a fleet and climb the leaderboard, with real counts as proof. The sections about the loop's internals are gone.
Dashboards that sit in cards instead of floating
Every panel on the Home, Fleet, Workspace and Engineering boards now sits in a card like the tiles. Cards side by side end on one line, and tile figures line up even when a label wraps. On a phone the cards stack, and tables scroll inside their card.
Fewer unchecked shortcuts, and a limit that only goes down
The code now holds 222 places that tell the compiler to stop checking, down from 552, and each one says why. A check counts them per part of the repository and fails if a count rises, so the number can only go down. Nothing changes for people using the loop.
Pick your app when you sign up: the board or the Arcade
Signing up from the home page now opens a select screen: the Omni app for the board, or the Arcade for the game. The pick decides where you land, and Remember my choice skips the screen next time, with a change link under the button to pick again.
The whole loop is now checked by a compiler
The kit, the game and the GitHub App are now strict TypeScript, type-checked on every pull request, and data read from outside is checked against a schema that names the wrong field. Nothing changes for people using the loop: same commands, same output.
Join a repository that already runs the loop in one step
Setting up the loop on a repository that already has it now only installs the plugin and signs you in. It opens no install pull request, and it tells you whether the knowledge base still needs filling or only a refresh.
Product constituents: the rules every agent reads first
Owners give each product a Statement and a Never list on Settings › Business, with a history of who changed what. Every Claude session reads them first, even offline, and the inbox check flags a spec that breaks one, judged by Jev once switched on.
Connect any editor's agent to your business
Settings › Business makes a read-only link for Cursor, Claude Code or any MCP client, so your editor's agent reads who you sell to and cites claim ids. A question no claim answers lands on the page to answer once. Jev can set junk questions aside.
Phase-0 PRs now check the spec against your business
Add Never lines on Settings › Business. The inbox check on phase-0 PRs gains a canon gate: a spec that breaks a Never line or misses your customer turns red, quoting the spec, with Rewrite and Change the claim buttons.
Let Jev make three decisions, one switch at a time
Settings › Jev lets an owner add a TypeSafe AI key and hand Jev three decisions: question category, outbox risk and bug risk. Each is Off, Shadow or On, with its own threshold and 30-day record. When Jev can't answer, today's answer counts.
Your personas now speak up in brainstorms
Think-big and brainstorm speak through your product's personas: the one a design misses objects once, with receipts. Each PRD page has a User voice tab showing every persona's score by stage, and Rework with this feedback.
SUPER OMNI WORLD, a platformer that opens at LV 2
A second game in the game room: SUPER OMNI WORLD, an original SNES-style platformer that opens at LV 2. Run and jump through three stages with your own hero, stomp entropy and reach the flag. The corner Game Boy lets you pick it too.
A video proving your PRD works, filmed for you
Run /omni:prove on a ready PRD and Claude films each acceptance criterion on the preview. The PR gets a ✓/✗ comment with a moving preview, and the PRD page a Proof tab with every clip. It's off by default, and it never blocks a PR.
Give your customers faces: personas on the Business page
Settings › Business has Personas: a cast per product, each with a stance, a pixel-art portrait picked from a trade's variations, who they are and how they use the product. Agents read them with omni business show.
Claude keeps your feature PR green and answers its reviews
Run /omni:pr-care on a PRD and Claude watches its feature PR until it merges: it fixes red CI and merge conflicts, fixes review comments worth fixing, and pushes back on nitpicks with a reason. The PRD page shows a health chip and a PR care tab with every thread's verdict.
Omni drafts your business from your repos, with receipts
Draft from my repos in Settings › Business reads your repositories and pasted web pages, proposes who you sell to, each fact quoted, and That's us confirms them. A weekly recheck brings what changed to the bell.
Play Entropy Invaders while Claude works
While Claude works on a PRD or a fix, its page and your /ask tab offer Entropy Invaders on a small Game Boy in the corner, under the arcade's usual rules. The game pauses when Claude asks you something, and says when Claude is done.
Tell Omni who you sell to, in a few taps
Settings has a Business tab where members tap who they sell to, where, and against which suggested rivals. Each repository can belong to a product. Think-big reads the confirmed facts and shows which ones it cited.
Readable long questions, and Claude's message beside them
Long questions now show a bold lead and fold the rest, with steps as a list. When Claude asks you to approve something it just wrote, that message shows above the question, so you no longer go back to the terminal.
A PRD in any workspace repository earns points
A PRD delivered through Omni Loop now earns points in every repository tracked in Settings → Repositories, multi-repository PRDs included. Points and XP start again from 0 the day this ships; games you already unlocked stay unlocked.
A tidier, collapsible main menu
The menu is shorter: Dashboard, Work, and one Settings entry at the foot that opens Fleets and Repositories as tabs. Shared with me and History are tabs on the Questions pages. On a computer, « folds the menu to a rail of sprites, and your browser remembers it.
Think big — a studio of agents for vast ideas
New /omni:think-big: a studio of agents draws concepts for an idea too big for one PRD, over rounds of boards and prototypes you react to. You crown one, and /omni:brainstorm --concept turns each of its areas into a PRD.
Engineering board — main-branch merges and loop health
The Engineering board now counts only merges into main, master or develop, so sub-PRs and promotions no longer inflate it. A new Loop health panel lists what the loop has stuck right now, each linked, and how often merged sub-PRs needed a fix first.
Person profile and chip links
Every person and fleet name in the app is now a link. A fleet opens its board, and a person opens their new profile: their numbers and their PRDs, fixes, pull requests and reviews. "My profile" in the avatar menu opens your own.
Faster Bug Fixes and Visual Updates
Bug Fixes and Visual Updates open at once with a placeholder list, then show their rows without waiting on GitHub. Each fix's state and labels are refreshed every 15 minutes, and again whenever someone opens that fix.
See who is who, and their fleet, everywhere in the app
Wherever the app names a person, their face shows first: their arcade hero, else their GitHub photo, else their initial. Wherever it names a fleet, its mascot shows in the fleet's colour. Home's people table is now headed Your fleet.
Snappier PRD list and dashboards
The PRD list and the dashboards show their frame at once and fill each block in as its data arrives. The sidebar moves between pages without a full reload, and the PRD list no longer waits on GitHub for its open-question counts.
An inbox check for phase-0 pull requests
Phase-0 pull requests get an **inbox** check from the Omni Loop app: green when the PRD's spec, plan, before/after, signed commits and open issue are all in place, red naming what is missing. Here, they no longer run the tests or build previews.
See each repository's own engineering stats
On the Engineering board, the top people lists show each person's face, their count in its own column and a bar against the leader. Each repository in the table opens its own page with the same stats for that repository alone.
Bug fixes and visual updates have their own pages under Work
Work now lists Bug Fixes and Visual Updates beside PRDs. Each fix has a page with its record, every round of variations a look was picked from, and a Timeline of who asked, picked, approved and merged it, and the release it went out in.
Answer Claude's questions with screenshots
When a question on the ask page needs more than words, Other now takes up to five screenshots: paste, drop or add them. They stay private to your workspace, and Claude in your terminal opens each one and sees what you see.
Real stages for every PRD, and counts of where they are
Every PRD shows seven stages, synced from the repository every 15 minutes, so a PRD in shipped reads as shipped and no page says the stage is unknown. The PRD list counts and filters by stage, and the dashboard shows how many are open, building or shipped now.
Choose the repositories you track and see how PRs move
Workspace owners add repositories from Settings, and each one is tracked by default. A new Engineering board shows pull requests opened, merged and open, time to merge per repository, and who opens, merges and reviews most. It also shows the share Omni Loop signed.
Tests and a dead-code check on every ready pull request
A ready pull request into main now runs the tests and a Fallow check for any unused or duplicated code it adds. Runs wait three minutes, so a burst of pushes costs one. Claude runs the same check before every commit and push.
A guide page for working across several repositories
The guide has a new page, Several repositories, that shows in three drawings how a feature spread over several repositories is planned in one place, built with one pull request per repository, and reviewed once, and in which order its pull requests are merged.
Dashboards for you, your fleet and the workspace
The app's menu now opens on Dashboard: Home, Fleet and Workspace. Each lists every member, even at 0 points, with PRs merged, PRDs drafted, in progress and shipped per day, repositories involved and questions answered, over 7 days, 30 days or the season. Fleets moved to Settings.
Build one feature across several repositories, one review
A feature planned across repositories can now be built from the repository that holds its plan: each repository gets its own pull request, every decision taken along the way is gathered in one place for a single review, and the plan says in which order to merge them.
A Skills section in the docs
The docs now list every Omni Loop skill by what you want to do, with a page each: what it does, when to use it, what to type, who runs it and its related skills. The docs search finds them, and /omni:help shows the same example in the terminal.
An alert when a spec, plan or before/after lands on your PRD
When a spec, a plan or a before/after page lands on a PRD you opened, the bell lists it under New documents until you open that PRD. With alerts on, you get one per PRD once its pushes go quiet for 30 seconds.
A bug report to one pull request
A new command, /omni:bug-fix, takes a bug from one line or an existing issue to one pull request: it triages the bug on its issue, shows a test failing before the fix, fixes it, adds a guard, and records what it found.
Five more fleet mascots
A fleet's owner now picks its mascot from eleven, not six: Atom Eve, a shark, a turtle, Allen the Alien and a robot join the library, and each plays its own short sound in the arcade.
One plan across repositories, reviewed in one place
A feature that spans the back-end and the front-end can now be designed once, in the repository that holds plans: each step of its plan names the repository its code lands in, and one review covers the whole feature before any code is written.
Small visual changes in one pull request
A new command, /omni:visual-fix, takes a small visual change from one line to one pull request: it shows four or five options, applies the one you pick, and records a before-and-after page.
More room in a PRD's questions
On a PRD's page, the Questions tab has more breathing room. Each round sits in more space, an unfolded answer reads as separate, taller lines instead of one dense block, and the "answered" count is set a little further from the list. On a phone the list looks as it did.
The knowledge map of every repository you set up
The knowledge map now has a Repository menu: beside Omni Loop's own, it lists every repository of your workspaces set up with Omni Loop and draws the one you pick on the same map. A link to one of its entries keeps the repository, so it can be shared.
A plan repository that knows its target repositories
A repository that holds plans can now list the repositories its features land in, with a role for each, and see which ones run Omni Loop and whose knowledge is current. One command sets it up in a single pull request.
Answer the agents' questions where you are
Answer the questions the agents leave in the terminal when a build ends, or on a PRD's Outbox tab beside its spec, where Send posts your answer on the pull request as you. The PRD list shows how many questions each PRD has open.
See what is waiting for you, on every page
Every app page now shows, without a reload, the questions and outbox items waiting for you: a count in the browser tab, counts in the menu, and a bell in the top bar listing each one. Desktop alerts and a chime can be switched on from the bell.
Lighter app pages, and clear questions left to answer
Every app page uses the full desktop width, and the top bar stands out in every theme. On a PRD's Questions tab, answered rounds fold to one line, rounds awaiting an answer stay open, and the tab counts questions: "7/10 · 3 to answer".
Retros and knowledge updates only when they teach something
Omni Loop now opens a retro or knowledge pull request only when it adds a new lesson or rule; otherwise it leaves one short comment on the merged pull request. The knowledge base no longer records how screens look.
The Omni page is open to every workspace, not only Vertuoza
No more @vertuoza.com address needed. Install the Omni App on your GitHub account or org, and its members can sign in from the terminal, push dossiers and use ask mode. Sign-in says which workspace your repository goes to, and a refusal says why.
A clearer PRD page, with Approve spec always in reach
A PRD's page opens on one header box, which stays at the top on larger screens: the title and its buttons, its stage, repository and links, then the tabs. Questions use the full width, Approve spec is readable, and outlines and later stages are easier to see in every theme.
The app has a sidebar
Every app page now has a sidebar: Home, PRDs, Questions, Knowledge, Fleets, Docs and Release notes. The top bar shows the page's title, the theme and Game mode, and your avatar, whose menu signs you out. On a phone, ☰ opens the sidebar as a drawer.
Fullscreen is your choice on desktop
On a computer, the arcade no longer switches to fullscreen when you first click or press a key. A small ⛶ button in the bottom-right corner of the page, or the F key, takes it fullscreen when you want; Esc or F brings the window back. Phones still go fullscreen on the first tap.
The PRD page shows its stage and what to do next
A PRD's page now shows where it stands, from idea to retro, with one button for what to do next: approve the spec, answer the outbox, review and merge, or read the retro. "PRD #n" links to its issue, and new Outbox and Retro tabs show the decisions and the retro.
Install the Omni Loop with one npm line and omni init
With Node, git, gh and Claude Code on your laptop, one npm line puts omni on your PATH in any shell, and omni init opens the install pull request, installs the Claude Code plugin and signs you in. The Install guide goes from twelve steps to five.
Your own fleets, or none
Fleets are now optional: pick one or play solo, and a workspace with no fleets goes straight to the game. Each workspace's owner creates, edits and retires its own fleets on the new Fleets page, with a name, colour, motto and mascot.
Omni Loop works in large repositories
Checks, brainstorms and shipping no longer crash in a repository whose list of files passes 1 MB. File names with spaces or accents are now read correctly too. Run omni update to get the fix.
Your PRDs, one click from every page
A PRDs link at the top of every page and a My PRDs card on your dashboard open the PRD list, which starts on the PRDs you opened, drafts included, with one click to the whole workspace. Claude now gives a PRD's page link whenever it answers about that PRD.
The PRD page opens on its questions and refreshes itself
A PRD's page now opens on its questions and shows each answered one as its answer alone. Quick questions are answered with one click on the list, a bigger one brings you back to the list once answered, and new questions appear with no reload.
A livelier, easier-to-read HOME poster
The HOME poster fills a desktop screen, its lines share one left edge, and its top line is cyan and easy to read. The planet turns, the crest sits under it, and Omni-man flies past every 12 seconds, except when your device asks for reduced motion.
Sign up with GitHub
Anyone can now sign up from the home page with GitHub: install Omni Loop on your organization or your own account, and get a workspace named after it. Members of an organization already on Omni Loop join it when they sign in. GitHub is now the only way to sign in.
omni on your PATH, and badges on every guide code block
The Install guide now puts omni on your PATH with one block you paste once per laptop, so omni works from any folder of a repository that has the kit. Every code block in the guide says where it goes: Terminal, Coding agent (or both), a file, or a GitHub comment.
Know which kit you run, and update it in one command
Every merge to main now publishes a numbered release of the Omni Loop kit. omni version says which one a repository runs and whether a newer one exists; omni update opens one pull request that brings it to the latest, and updates your Claude skills.
Your context and your PRD, always in view
Claude Code shows two lines at the bottom of the terminal: the model, how full the context is and the 5-hour usage, then the PRD the session works on, its stage and, while it is built, its wave and slices. Setting up the loop turns it on for everyone.
A Getting Started guide, and Release notes in the top bar
A public guide at /docs shows how to install Omni Loop, invade a repository and ship a first PRD, with fixes for common errors. The home page opens it from Getting Started. Every app page now shares one top bar, with Release notes and Docs.
The app opens on your own dashboard
The app's home page now shows your hero, your fleet, your season's points and rankings, a chart of the pull requests you got into main this week, and counts of your answered questions, settled decisions, new PRDs and the questions waiting for you.
Ask the loop how it works and where your work stands
Help explains the loop's stages, its principles and every command, in the terminal and inside Claude. Status shows how many PRDs have shipped, wait in the inbox, are being built or wait for review, a bar of delivered work, and the PRDs you worked on.
The homepage says what Omni Loop is worth
The homepage now opens with what the loop gives you: agents ship, you steer. It speaks to engineering heads, developers and product managers, shows what you see while agents work and how to get in and out, and explains every loop term it uses.
Week of 21 Sep 2026 · 6 releases · 26 PRDs
Always know what to do after a build
A build now ends by showing where its files are, which stage of the loop it has reached, and the next steps for how it ended: review and merge a finished build, answer the questions it left open, or clear what holds it up. Reworking a build after those answers ends the same way.
The app opens in Omni, with Light and Dark one tap away
The app's pages open in Omni, the homepage's own colours, and the theme switch offers Omni, Light and Dark. A saved choice of Light or Dark is kept, and anyone who had chosen System now sees Omni.
Always know what to do after a brainstorm
A brainstorm now ends by showing where its PRD's files are, which stage of the loop it has reached, and the next steps in order: review the proposal, merge it, then start the build. Planning a PRD on its own ends with its next steps too.
HOME — the Omni Loop front door, a retro print ad
Everything we ship, in plain words
Every PRD Omni Loop ships now comes with a release note, reviewed with its code and published on a public release notes page, grouped by week, with a version number that never changes. The PRDs shipped so far form the initial release, 0.0.1.
From idea to merged PR, on a loop.
The first public release of Omni Loop gathers everything shipped from 24 to 27 September 2026: the kit and its Claude Code plugin, the omni-loop GitHub App, ask mode and its question history, a knowledge base that fills itself, PRD dossiers, a design system, and the arcade that turns delivery into a game.
Install the delivery loop in any repository
The Omni Loop kit packages the brainstorm, build, review and ship loop as one command-line tool and one configuration folder, so any repository can run it without a hand-made copy of its own.
PRD 3Brainstorm, build and ship with three commands
The omni plugin for Claude Code gives the loop its commands: /omni:brainstorm turns an idea into a reviewed PRD, /omni:yolo builds it in parallel slices, and /omni:yolo-fix reworks what a reviewer disagreed with.
PRD 7Every open question, visible on the pull request
The omni-loop GitHub App adds an outbox check to every pull request. It stays red while a decision the agents took still waits for a person, so reviewers see open questions before they merge.
PRD 28Set up Omni Loop with one line
omni init installs the loop in a repository with a single command: it writes the configuration, adds the command-line tool, creates the labels the loop uses and says what is left to connect.
PRD 39A playbook that tells agents how your repo works
Each repository gets a playbook of short forms (how it tests, what a merge publishes, what must never break), filled from what the repository already documents. Agents read it at every step of the loop.
PRD 45Decision reviews with a sense of humour
Every question the agents leave for a person on a pull request now opens with a short intro and ends with a punchline, so a long list of decisions reads like a conversation rather than a form.
PRD 50Your repository's rules, found and written down
/omni:invade explores a repository and proposes its knowledge base: principles, business rules and invariants, pointing at the pages that already state them or drafted from what the code enforces.
PRD 68Answer Claude on a page, not in a terminal
Ask mode shows the questions Claude asks during a session on a clean web page, with options and previews side by side. It is switched on per checkout, and the terminal takes over whenever the page cannot answer.
PRD 71Every delivery comes with its own retrospective
When a PRD merges, the Omni Loop app counts what went wrong during its delivery and opens a retro pull request with findings, evidence and proposed lessons. It runs again 14 days later.
PRD 72Every decision lands in the knowledge base
When a PRD merges, the decisions taken while building it are sorted into the knowledge base as decision records, rules or invariants, with who answered and who merged. One pull request carries them all.
PRD 82The arcade, in your pocket
On a phone, the Omni Loop arcade appears as a handheld console with readable text and real buttons; on a computer, the screen alone fills the window. The game itself does not change.
PRD 94Omni-man signs the loop's work
Every commit, pull request and issue the loop makes carries Omni-man's signature, and a new command, omni credits, counts his contributions across the organisation.
PRD 99One loop, many teams
Everything the game holds now belongs to a workspace, with its own members, fleets, repositories and colours. Vertuoza is the first workspace, and others can join without seeing each other's data.
PRD 100One look for everything Omni Loop
A single design library holds the Omni Loop logo, colours, fonts and pixel sprites. The arcade and every reading page draw from it, and a catalogue page shows each piece.
PRD 141Every terminal gets its own tab
Ask mode keeps one session per Claude Code terminal. The page shows each terminal as a tab, so questions from sessions running side by side no longer overwrite each other.
PRD 142No answer is ever lost again
Every question Claude asks is kept for good, with its repository, branch, PRD, cost, category and who answered. The whole workspace can browse the history, and a live question can be shared with a teammate.
PRD 144See your knowledge base as a galaxy
Each domain of a repository's knowledge base appears as a star system of its principles, rules and invariants, in the arcade and on a plain reading page.
PRD 149Shipping now levels you up
Every point earned by delivering also counts as experience that never resets. Levels unlock games in a new game room, starting with Entropy Invaders at the very first point.
PRD 160A signature that links back home
Pull requests and issues made by the loop end with "Omni-man by Omni Loop ©", linking to the Omni Loop home page. The hero's name and the link are set once in the configuration.
PRD 215Every PRD gets a home the whole team can read
Each PRD's spec, plan and before/after page are kept on the Omni page with every version, next to the questions that shaped them, for the whole workspace to read.
PRD 216Jump between work and play in one tap
A Game mode button on every app page and an App mode switch in the arcade move you between the reading pages and the game, with a confirmation before each switch. The app gets its own home page.
PRD 238