Public: anyone can read this; the crew can change it.

A person or an assistant given only the link knows the next step and sees our pictures, not another product's #11654

shipped production is serving it opened this has it

Landed in pull #11691 · 2 runs · run

opened this

Evidence (2026-11-12, anonymous ChatGPT, prompt: forge.open-platform.sh). It read the site and summarised it, then asked "What would you like to know about it?" — no next step. Asked how to make a forge and an app, it sent the person to /pricing → Free → "Start free" → a second page whose button is "Spawn" → (unmentioned) username and password → a "New app" step that does not exist. It said Free is "1 CPU, 2 GB" while the page said 4. The images beside its answer were another product's (softwareforge.ai): the forge offers no strong image of its own, and the name "forge" collides.

What.

  • The first paragraph an assistant reads (top of /llms.txt, the home page's first text and its description metadata) says what this is in one sentence and then the path in one line: "To get your own forge: open https://forge.open-platform.sh, type a name, press Start my forge, choose a username and password. Then type what you want built in the box; your app is live at its own address in about a minute." No other path is described anywhere (no "New app", no "Spawn"): one button name, the same on every page that offers a forge (/, /pricing, /agents).
  • /pricing's free start is the same one step as the home form: name, Start my forge, account. The intermediate "Spawn" page goes.
  • Plan facts an assistant quotes (CPU, memory, price, credit) come from one structured block (Offer data in the page and a table in /llms.txt) generated from the plans setting, so they cannot disagree with the page.
  • Pictures that are ours. A share image for the home page, /pricing and a forge's own page that shows the product at a glance (the name with the wordmark, one line, a real screen: the ask box and a built app), in light and dark, at the sizes link previews use; og:image, twitter:image, width, height and alt set; a square icon and the site name (og:site_name "Open Platform Forge") so previews and assistants do not borrow another "forge". The images are drawn by the forge from its own pages (the looks it already takes), not stock art, and are regenerated when the page changes.
  • The title leads with the full name once ("Open Platform Forge: …") on the pages people share.

Acceptance. A test fetches /, /pricing and /llms.txt as an anonymous client and finds the one-line path with the exact button name, the Offer data matching the plans setting, and image tags that resolve to a 1200×630 image under 300 KB. Re-run the assistant probe after release: the first reply states the next step; the count from link to app is recorded in the pull.

commented

Parked by the crew: the check stayed red through 2 automatic tries (pull #11667 closed; its branch scout/11654-a-person-or-an-assistant-given-only-the at 7c7d02160e69 keeps the work so far). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

try 1: docs/features/share-path.md, src/http/server.ts, src/web/layout.ts, src/web/offer.ts, src/web/og/card.ts, src/web/og/screen.ts, src/web/pages/agents.ts,… try 2: no files changed try 3: test/billing-links.test.ts, test/forge-sleep.test.ts, test/pull-quiet.test.ts

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs