Did FLEXUS say Dear Passengers used generative AI?
No. In a developer-tagged Steam discussion, FLEXUS stated that Dear Passengers was created without generative AI.
Source check
Did Dear Passengers Use AI? FLEXUS Statement Explained
FLEXUS says Dear Passengers was created without generative AI. Here is the original statement, what Steam asks developers to disclose, and a practical way to judge any new evidence.
Developer statement FLEXUS said no generative AI was used to create Dear Passengers. It described the old job posting behind the concern as marketing work for other mobile projects. Not independently verified This is a developer-tagged primary source, not an independent asset audit.
The record
What FLEXUS actually said
The original source is a Steam Community thread titled "AI? No thanks." A player linked the game to a generative-AI job listing and said they planned to remove it from their wishlist. FLEXUS answered from an account carrying Steam's developer label: no generative AI was used to create Dear Passengers, and the studio offered to share work-in-progress and development screenshots.
FLEXUS then posted the answer marked by the thread author. It said the old listing concerned marketing assets for some mobile projects, had nothing to do with Dear Passengers, and that this game was created without generative AI. The player accepted the explanation and said they had added the game back to their wishlist.
The useful conclusion is specific rather than universal: FLEXUS has publicly denied generative-AI use in Dear Passengers and separated this game from the older hiring description. Because the reply is developer-tagged and attached to the game's own discussion hub, it carries more weight than a repost or unattributed screenshot.
The limit
What readers still cannot verify
The thread does not expose the studio's source files, contractor agreements, tool logs, asset history, or Valve review notes. No independent reviewer is identified. FLEXUS offered development screenshots, but the checked thread does not contain a complete, third-party provenance review of every texture, sound, animation, line of text, and marketing asset.
That does not cancel the reply. It defines its strength. A first-party statement can establish what the developer claims; it cannot certify the entire production pipeline from outside the studio. The accurate wording is therefore “FLEXUS says,” not “an audit proved.”
The statement also belongs to a date and scope. It addresses Dear Passengers as discussed in July 2026. Later DLC, trailers, localization material, store artwork, ads, or outsourced assets would need to be assessed against whatever evidence exists for those materials. Readers do not need to assume a future problem, but they should avoid treating a current reply as a permanent guarantee about work that does not yet exist.
Platform rules
How Steam's AI disclosure works
Steam's process helps frame the question, but it is not a public asset audit.
Steamworks requires developers to complete a Content Survey before submitting a store page and product build for review. The survey includes generative AI used during development or built into the product. Valve says the focus is content that ships with the game and is consumed by players, such as artwork, sound, narrative, and localization. General efficiency features inside modern development tools are not the focus unless they help create that shipped content.
| Pre-Generated content | Content made with the help of generative-AI tools during development and shipped for players to consume. Steamworks says developers must describe the implementation, while Valve reviews the output under the same legal and content promises applied to other game material. |
|---|---|
| Live-Generated content | Content created with AI tools while the game is running. Steam requires the same disclosure and also asks the developer to describe guardrails intended to prevent illegal output. |
| Built-in efficiency tools | Steamworks distinguishes tools that improve workflow from generative systems used to create player-facing content. A job listing or a tool name therefore needs product, asset, and production-stage context before it answers the disclosure question. |
This distinction matters for Dear Passengers. A company-wide hiring description may concern concept work, advertising, another game, or content that never ships. It becomes evidence about Dear Passengers only when it can be tied to this product and to a relevant asset or live feature.
The public Steam page is still only one view of the process. Visitors cannot inspect the developer's complete survey answers, Valve's internal review notes, or production files. A visible disclosure would be important evidence if one appears; the lack of a visible disclosure is not, by itself, proof that every asset was independently examined. For the current question, the developer-tagged reply remains the clearest product-specific public source.
Why it spread
Why the old listing caused confusion
The confusion came from connecting a broad studio hiring signal to a specific unreleased game.
The initial argument joined three facts: FLEXUS develops Dear Passengers, FLEXUS had a hiring listing that mentioned generative AI for concept creation, and Dear Passengers therefore used generative AI. The first two facts can make the question reasonable, but they do not establish the third. A studio can run several products and separate its playable assets, internal concepts, and mobile marketing work.
PC Gamer later described the backlash and repeated FLEXUS's response. That report is useful because it preserves the public context and links the listing controversy to the Steam discussion. It remains secondary evidence for the studio's position; the developer-tagged Steam posts are the direct source.
A better check is to ask four narrower questions: Which product is named? Which asset or feature is involved? Was the material made for players to consume, for internal development, or for marketing? Does the evidence come from its original page? Those questions prevent a studio-level clue from being presented as product-level proof.
Dated source record
What the checked sources show
This record keeps direct evidence, context, and limits apart.
| Steam discussion opened | A Steam user raised concern about generative AI and an apparent hiring listing. This is the question that prompted the developer reply. |
|---|---|
| FLEXUS replies | The developer-tagged account denied AI use, offered work-in-progress screenshots, and identified the old listing as marketing work for other mobile projects. The thread author marked the explanation as the answer. |
| PC Gamer context | PC Gamer reported the listing confusion and repeated FLEXUS's Steam response as part of a broader article about the game's fast wishlist rise and public discussion. |
| guide and platform check | The sources were checked against the current Steam store page and Steamworks Content Survey documentation. No later product-specific disclosure or independent asset audit was found in the sources reviewed for this page. |
Evidence ladder
How much weight should each source carry?
Specific, original evidence should outrank repetition and visual guesswork.
| 1. Product-specific primary source | A developer-tagged post, official product update, current platform disclosure, or named production record tied directly to Dear Passengers. The Steam reply belongs here: it is direct and attributable, although it is not independent. |
|---|---|
| 2. Verifiable production evidence | Dated work-in-progress files, credited artists, asset histories, contractor records, or a documented third-party review. These materials can support or challenge a studio statement when their origin and scope can be checked. |
| 3. Named secondary reporting | A reputable outlet that links original material, contacts identified people, and distinguishes reporting from allegation. PC Gamer provides context at this level but does not independently inspect the game's assets. |
| 4. Leads, not conclusions | Cropped job listings, anonymous posts, reposted screenshots, and claims that an image merely “looks AI.” These may identify a question worth checking; without provenance and product-specific detail, they do not answer it. |
Reader checklist
Check a new claim in seven steps
- Name the product. Confirm that the source refers to Dear Passengers rather than another FLEXUS game or a company-wide role.
- Open the original. Find the live post, archived listing, store disclosure, video, or credited document instead of relying on a cropped repost.
- Identify the material. Separate playable assets from concepts, internal references, advertisements, trailers, social posts, and store capsules.
- Identify the claimed use. Ask whether the allegation concerns Pre-Generated player-facing content, Live-Generated gameplay, or a workflow tool outside Steam's stated focus.
- Check authority and date. Look for a developer tag, named author, publishing date, edits, and a connection to the production phase being discussed.
- Look for testable detail. Files, artists, vendors, dates, and production stages are more useful than a general visual impression.
- Compare later corrections. A newer, specific primary source can supersede an old listing or report; a recycled screenshot cannot.
Update threshold
What would change the answer?
This page will change if FLEXUS publishes a materially different statement, Steam displays a relevant product disclosure, verifiable production records emerge, or named reporting connects new evidence specifically to Dear Passengers. The direct answer, evidence label, source record, and FAQ should all change together.
An accusation based only on visual style would not be enough. Neither would a listing that cannot be connected to the game, a summary that omits its original link, or a claim about a mobile advertisement presented as proof about PC gameplay assets. Those items can start an investigation, but they cannot complete one.
The opposite standard matters too: not finding a public audit is not evidence of misconduct. Most unreleased games do not publish a file-by-file provenance report. Players can reasonably decide that the developer statement is sufficient, or wait for stronger documentation. This guide's job is to show exactly what supports the current answer so that readers can set their own threshold.
Passenger questions
AI use FAQ
Quick answers about the developer statement, its limits, and where to check future updates.
Does Steam require developers to disclose generative AI?
Steamworks says developers must complete a Content Survey before store-page and product-build review, including details about pre-generated or live-generated AI content used in the product.
Does the lack of a visible Steam AI disclosure prove that no AI was used?
No. A public store page is useful evidence, but visitors cannot inspect the developer's full survey answers, Valve's review notes, or the game's production files.
Why did an old job listing cause confusion?
The listing referred to generative AI for concept creation. FLEXUS said it concerned marketing assets for some mobile projects and had nothing to do with Dear Passengers.
What evidence would change this page's current answer?
A later FLEXUS statement, a relevant Steam disclosure, verifiable production records, or named reporting tied specifically to Dear Passengers could change the answer.
Is this page affiliated with FLEXUS?
No. Dear Passengers Guide is an unofficial fan guide and is not affiliated with FLEXUS.
Sources and corrections
Sources used for this explainer
Primary sources come first. Secondary reporting is used only for public context.
The developer-tagged Steam discussion is the primary source for FLEXUS's answer. The official store page identifies the product, while Steamworks documentation explains Valve's current disclosure categories. PC Gamer is included only as secondary reporting about the public controversy. For corrections, broken links, source updates, or accessibility issues, email support@dearpassengers.org. This is a guide contact, not official game support.
- Steam Community discussion: AI? No thanks.
- Official Dear Passengers Steam store page.
- Steamworks Documentation: Content Survey.
- PC Gamer: A new friendslop game is already Steam's 12th-most wishlisted game a mere week after it was announced.
Unofficial fan guide; not affiliated with FLEXUS.
Continue briefing
Read next
Pair this statement with the broader source checklist and current official game information.