OpenReview-Score-Watcher: The Scoreboard Hidden in a Paper Page

A Chrome extension that reads OpenReview review notes, averages the ratings, and keeps the result in a floating window that follows the reader.

6 min read • View on GitHub • More from wanshuiyin

A browser window showing an OpenReview paper page with a floating score panel layered over the text. The illustration shows how the extension keeps review scores visible inside the reading flow instead of hiding them in a separate dashboard.
The whole idea fits in one frame. Review scores stop being a separate destination and become part of the page itself.
Key Takeaways

A scoreboard inside the paper page

Most OpenReview tools ask you to leave the paper and visit a dashboard, spreadsheet, or export. This extension does the opposite. It leaves the paper in place and drops the score state on top of it, so the review number stays in your line of sight while you read, compare, or refresh.

That choice matters because it changes the unit of work. The repo is not trying to give you a broader analysis suite. It is trying to keep one paper's review state visible long enough that you stop hunting for it.

OpenReview is not a document. It is a graph.

The technical move is small but smart. The extension pulls the paper's forumId from the OpenReview URL, follows the review notes attached to that forum, and reads the structured rating field instead of trying to infer scores from page text. That gives it clean input for an arithmetic mean, plus a last-updated timestamp when new notes arrive.

The extension is easiest to understand as a graph. It reads one paper node, gathers child review notes, computes a score, and persists the result as a floating UI layer.

The UI is the product

The floating window is not decoration. It is the interface contract. It stays visible while you move around the page, it can be dragged out of the way, it can be removed, and its tracked state lives in chrome.storage so the layout and watchlist survive beyond a single tab session.

A close view of the floating score panel with a drag handle, a highlighted current paper marker, and a compact list of review scores. The image explains that the panel is persistent and movable, not a temporary popup.
The closer you get, the clearer the design intent becomes. This is an instrument panel, not an extension popup.

That is why the repo feels bigger than its footprint. A few DOM hooks, a little storage, and a lightweight fetch path are enough to make the browser feel like a live monitoring surface. The design solves a specific problem: review anxiety is not about data volume, it is about constant context switching.

本插件自动追踪 OpenReview 上任意论文的分数变化,并以全局浮窗实时展示评分、均分与更新时刻。

wanshuiyin, Project Creator and Sole Contributor · OpenReview-Score-Watcher README

Why this exists in the first place

The repo reads like a tool built for a very specific academic workflow, then shared because it happens to be useful to others in the same situation. It uses the Chrome extension install path that skips marketplace friction, which makes sense for a narrow utility that matters most during a concentrated review cycle.

That narrowness is a feature. It does not need to become a platform, because the whole point is to remove one repetitive ritual: rechecking whether a paper's score changed yet again.

What it beats, and what it does not

The comparison is not about ambition. It is about where the information lands. Batch tools can cover whole venues, Google Sheets can organize assignments, and Zotero integrations can archive notes, but this extension wins when the user is already on the paper and wants the score visible now.

FeatureOpenReview-Score-WatcherOpenReviewTrackerOpenReview AC Workflow AutomationOpenReview Fetcher for Zotero
Primary userReader tracking one paperResearcher analyzing a venueArea Chair managing assignmentsZotero user archiving reviews
Delivery formatFloating browser overlayPython analysis scriptsGoogle Sheets workflowZotero notes and attachments
Live vs batchLiveBatchBatchBatch
ScopeSingle paper in the active tabVenue wideAssigned papersLibrary items
Setup frictionLow, load unpackedMedium, Python environmentMedium, credentials and sheetsMedium, plugin setup
Best use caseKeep one score visible while readingStudy aggregate trendsCoordinate review workflowStore reviews with references

That table tells the real story. This repo is not the most powerful OpenReview tool in the set. It is the most immediate one, and in a narrow workflow, immediacy is often the only feature that matters.

A narrow tool with a precise job

The best small tools do not try to solve the whole category. They show up exactly where the pain is sharpest and remove one repeated action with almost no ceremony. OpenReview-Score-Watcher does that by turning a paper page into a live scoreboard, then getting out of the way.