Universal Paperclips in browser

Game files

No own files requested before making clips

Controls

Pointer-based controls

Account

No sign-in in checked entry

Mobile gameplay

Not tested

Full session

Not tested

HTTP link check

HTTP 200; 0 redirects (2026-10-16)

Basis: project instructions and limited desktop entry observation. Observations: Oct 16, 2026. Conditions organized: October 16, 2026.

Five Make Paperclip clicks raised production from 0 to 5 and used five inches of wire. No sign-in or own files appeared before this path; automation, later phases, saves and touch input were not tested.

Project type: Native browser game

Frank Lantz's own games page links the original web clicker separately from mobile editions. Playing the role of an AI is its theme, not evidence of AI-generated content or an emulator.

Classification organized October 16, 2026 from the recorded source and check notes; not a new gameplay test.

This Universal Paperclips browser guide follows Frank Lantz's own games page to the original release. The linked landing page offers a continue-to-web-version route, whose exact target is index2.html. We opened that target and made five paperclips using the displayed button. Total production rose from zero to five and wire decreased from 1,000 to 995 inches. That is an observed opening interaction, not a completed strategy, an automation test or evidence of later phases merely because their labels exist in a document.

The check and source review are dated October 16, 2026. The author's page identifies a 2017 web release and separate mobile editions, but we did not establish an exact publication day. Its AI theme describes the player's role in the game; it does not show that the text is generated by AI or that a generative system was tested. Our public image is the actual opening interface after the five clicks, including the remaining wire and fictional business counters.

Guide published 2026-10-16. Source reviewed 2026-10-16. Author release-page publication: Not established. The author's games page gives the year 2017 but did not establish an exact first publication day for this browser release.

Game files

No own archive, ROM, installation package or uploaded game data was requested before the production button and its response. We used the original online document and did not download a mobile edition. The browser still loaded the game's own resources. No disconnected visit, cache inspection or transfer measurement was performed, so the file label is not an offline guarantee. The author's landing page and exact game document serve different roles: one identifies the route and editions, while index2.html is the path actually exercised. This directory hosts neither an executable copy nor a saved state for a later game phase.

Controls

We clicked Make Paperclip five times. The total changed from Paperclips: 0 to Paperclips: 5, with wire falling from 1,000 to 995 inches. Opening inventory then sold automatically; a later view showed zero unsold clips and $1.25 in game funds. Those counter changes support pointer input for the opening action. We did not press lower or raise, purchase wire or marketing, or unlock an automatic clipper. A short-lived clips-per-second display around manual input is not a verified autonomous production rate. The screenshot later showed zero automatic production, and no automation performance claim follows from this sample.

Account

The opening game required no registration, password, email or payment before the five clicks. We created no account and submitted no personal information. Its Available Funds label represents fictional game currency, not a bank balance, checkout or investment account. We opened no gift-shop or mobile-store link. This narrow account condition does not describe every outside destination linked from the page. The guide's own Save control only bookmarks this project; it does not store a Paperclips run, synchronize counters or connect to the author. Save recovery and persistence were not exercised in the original game.

Mobile gameplay

Not tested. The original landing page explicitly says the web version was not designed for phones and points to separate mobile editions. We keep that source warning distinct from our desktop result. We did not open those store links, test phone taps, rotate a device or inspect a mobile save. A readable small-screen guide is not a mobile-game compatibility check. The five desktop button presses should not be presented as proof that later interfaces, smaller controls or background behavior work on a phone, and the existence of an app does not establish progress transfer between editions.

Full session

We stopped in the initial business and manufacturing interface after five clips. No later project, automatic production system, investment interface or ending was reached. The visible opening counters changed while we watched: sales could reduce unsold inventory without another click, so a screenshot's inventory need not equal total clips produced. That is why the observed totals and wire use are stated separately from transient sales figures. No refresh, browser restart, import, export or recovery test followed. The author describes a broader experience, but this guide does not borrow its later events or completion time as if we had played them.

HTTP link check

An independent HTTPS request to the exact decisionproblem.com/paperclips/index2.html address returned HTTP 200 with zero redirects on October 16, 2026. Certificate validation stayed enabled. The author's landing page had separately identified that exact web-version target; the stored link does not silently substitute a similarly named mirror. The document response only establishes the checked address. The button-and-counter observation is separate evidence that the opening game initialized. Neither result proves every later system loads, future visits succeed or browser-local progress survives a cleared cache. No warning, login gate or security control was bypassed.

The author describes the player as a paperclip-making AI. That framing identifies the subject of the original clicker rather than the technology that generates its content. This directory therefore keeps it among original browser projects and does not use the theme as evidence of AI-assisted development or generated stories. Similarly, fictional prices and funds are gameplay counters. We did not test later investment systems or make any real transaction. Read the original author page for context, and distinguish its broader description from the five opening clicks verified here. No walkthrough of unvisited phases is inferred from hidden or initially unavailable controls.