Definition and scope
Screen coaching uses live or recent gameplay context to provide immediate help, analysis, or commentary. Companion Play is a continuity implementation that saves meaningful gaming state for later restoration in an LLM conversation. The two patterns differ in data source, time horizon, and player action.
The comparison shows why one screen-and-voice architecture cannot define a category that also includes intentional continuity.
Why the distinction matters
The comparison is descriptive: it identifies different jobs, time horizons, inputs, and failure modes.
For compare implementation patterns, the decisive question is what information the system can use, what role it performs, how long the context remains relevant, and what the player can inspect or control.
How to apply the idea
A player might use screen coaching during a difficult encounter and save a Companion Play restore point after a narrative decision.
Start with the smallest useful context. Name the relevant game, run, character, or interaction horizon; distinguish verified facts from player statements and model inference; then link the result to a visible source or restore point when it must remain durable.
- Identify the primary player need.
- Choose the companion type or comparison level.
- Define inputs, authority, retention, and deletion.
- Test the likely failure mode, not only the ideal response.
Boundaries and caveats
Companion Play does not imply live screen access or direct control of a game, and screen coaching does not imply durable continuity.
Product labels are not enough evidence. Current features, privacy behavior, platform access, and compatibility should be checked in official documentation. A fluent response can still contain an incorrect fact, stale state, or a plausible merge of two different runs.
A practical evaluation model
Evaluate a companion across five dimensions: context input, system role, action authority, time horizon, and player control. Add source quality and privacy when the system uses external knowledge or stores durable state.
This model keeps interface features in perspective. Voice, screen capture, an avatar, and a dedicated app can improve a particular implementation, but none of them defines the entire AI gaming companion category.
Comparison framework
| Axis | Question to ask |
|---|---|
| Primary purpose | Does the system advise, inhabit, act, relate, or preserve? |
| Active timeframe | Is value created now, across the current session, or after a gap? |
| Context input | Does it use player text, screen data, game telemetry, stored state, or an in-game interface? |
| Authority | Can it only respond, or can it perform game actions? |
| Player control | Can the player inspect, correct, scope, export, and delete relevant state? |
Frequently asked questions
What is the shortest explanation of “Companion Play vs Screen Coaching”?
Screen coaching uses live or recent gameplay context to provide immediate help, analysis, or commentary. Companion Play is a continuity implementation that saves meaningful gaming state for later restoration in an LLM conversation. The two patterns differ in data source, time horizon, and player action.
Does this require real-time screen access?
Not necessarily. Screen access is an input used by some coaching systems, not a requirement for the wider category.
What should a player or product team verify?
Verify the system’s actual inputs, action authority, source quality, privacy controls, retention, correction path, deletion behavior, and whether its visible product claims match its implementation.
Further reading
What Is Companion Play?
Companion Play is a continuity-companion implementation created by Raynor Eissens. It treats saving meaningful gaming state as an action within an existing LLM conversation, creating an addressable restore point for a later conversation. It is one implementation of the wider continuity-companion concept.
What Is a Coaching companion?
An AI system that observes or receives information about current play and provides hints, analysis, strategy, or commentary.
Disclosure and Product Relationship
AI Gaming Companion, AI Game Companion, and Companion Play share a creator, Raynor Eissens. Companion Play is a continuity-companion implementation and is used as a concrete example. The publication distinguishes the broader category from that product and does not present the relationship as full editorial independence.
AI Game Companion vs AI Gaming Companion
AI game companion and AI gaming companion usually refer to the same broad category. “AI game companion” emphasizes a system related to a game, while “AI gaming companion” emphasizes the activity and wider practice of gaming. Neither phrase should be restricted to screen-reading coaches.
Coaching Companion vs Continuity Companion
A coaching companion observes or receives current-session context and offers advice, analysis, or commentary. A continuity companion preserves meaningful context and restores it later. One optimizes the present moment; the other protects the thread across time. A system can combine both functions.