Codex Pet Visibility Checklist
See the expected surface, setting, and activity state currently held in the browser.
Diagnose visibility
Codex Pet Not Showing
A missing floating pet can be caused by the selected product, a tucked state, a setting, a local custom-pet boundary, or an unrelated package problem. Use the environment triage to separate display-state checks from file checks before reinstalling anything. Start with the local, reversible action described by this codex pet not showing checklist; its evidence boundary remains visible.
LOCAL TOOLYour local result appears here
Use the first control. No sample output is presented as evidence.
Result before explanation
Codex Pet Not Showing workspace
Select the expected surface and the first visible symptom. The result keeps display state separate from package validity. This page cannot observe the user's desktop or prove a product defect. It provides explicit checks and preserves Unknown where the environment is not supplied.
The workspace reports the selection, current local result, source category, and remaining limitation without presenting an empty field as proof.
Bounded result
Read one conclusion from the visible inputs.
Next evidence
See which record or test remains missing.
Four practical benefits
Why this workflow stays bounded
This tool handles one page decision, keeps processing local, and exposes evidence limits, next links, and corrections.
Check the visible state
Confirm whether the pet is tucked, disabled, blocked behind another window, or expected on a different surface.
Separate local and web
Do not assume a locally created custom pet automatically appears on the web.
Validate only when needed
Open the file checker after the settings and surface checks indicate an input problem.
Preserve evidence
Record version, environment, and the first failed step before changing the installation.
Facts before assumptions
Evidence map before action
This page cannot observe the user's desktop or prove a product defect. It provides explicit checks and preserves Unknown where the environment is not supplied. Before anyone acts, keep that boundary in plain view.
Settings selection
Current official guidance describes choosing Pets in Desktop settings.
/pet control
Current official guidance describes /pet as a wake or tuck control.
Four visible states
Running, Needs input, Ready, and Blocked describe activity, not validation severity.
Local storage boundary
Custom pets stored locally are not automatically synchronized to web.
Package uncertainty
Community package paths and formats need named evidence rather than inference.
Meaning and boundary
Codex Pet Not Showing: evidence boundary
Use the environment triage to separate display-state checks from file checks before reinstalling anything. Keep local facts separate from cited guidance, named profiles, dated observations, and unseen companion cause.
Visibility diagnosis begins with the place where the companion was expected, because Desktop, Web, terminal, and IDE behavior differ.
The Pets setting and documented wake-or-tuck control can explain absence before any custom resource is inspected.
A Blocked activity label describes task state and should never be reported as proof that the character package was rejected.
Local custom resources are not automatically synchronized to web, so another surface can legitimately show a different selection.
The current product version belongs in the observation because interface controls and supported behavior can change over time.
Deterministic
Repeat the same check with the same visible input and compare the results.
Documented
Cite the first-party source and date behind a display observation.
Community profile
Name the non-official profile, version, and publisher.
Running
Active work; not verification of display observation.
Needs input
A request for attention; not evidence about unseen companion cause.
Ready
An activity state; not installation or rights confirmation.
Blocked
Interrupted visibility check; not resource rejection.
Surface-specific limits
Codex Pet Not Showing across products
Desktop, Web, CLI, and IDE create different evidence needs for this visibility check. Product facts below were checked on 2026-07-26.
Name the intended product and environment before relying on a result.
| Context | Evidence and limitation |
|---|---|
| Desktop | Check the Desktop Pets setting, selected companion, wake-or-tuck state, and product version before opening custom files. |
| Web | A local custom companion will not automatically appear on web; inspect the web image selection and official constraints separately. |
| CLI and terminal | For terminal absence, identify emulator graphics support and remove tmux or Zellij from the test before blaming the resource. |
| Windows, WSL, and IDE | Name the exact Windows or WSL surface; an IDE extension is not expected to show the Desktop floating overlay. |
Local capability
Codex Pet Not Showing without hidden submission
This local diagnosis control creates a display observation without changing browser history or resolving the unseen companion cause.
Choose
Supply only the needed expected surface, setting, and activity state.
Run locally
Create the display observation in this tab.
Read scope
Compare the result with its stated limitation.
Continue
Open the matching evidence route.
Reset
Clear local input without changing history.
Four reversible steps
Codex Pet Not Showing workflow
Preserve the original input and current environment before changing a file, setting, or install state. Make one observable change at a time and record the result before continuing.
Keep diagnosis, implementation, verification, and correction as separate stages.
- 01
Confirm the surface
Identify where the pet should appear and whether that surface currently supports the expected behavior.
- 02
Check settings and state
Review the Pets setting and use the documented control without modifying local files.
- 03
Compare another known state
Observe whether state changes affect visibility before blaming a package.
- 04
Inspect the input last
If a custom resource remains implicated, validate a preserved copy and record the result.
Evidence checklist
Codex Pet Not Showing: evidence review
Useful evidence names the claim, resource, version, method, date, result, and limitation.
| Context | Evidence and limitation |
|---|---|
| Expected surface | The report names Desktop, Web, CLI, or IDE. |
| Pets enabled | The current setting has been checked. |
| Wake or tuck checked | The documented state control has been tried. |
| Version known | The product version is recorded or Unknown. |
| Custom or built-in | The selected pet source is distinguished. |
| Input check scoped | File validation is used only after display checks. |
| Source category | Label official, community, test, report, or Unknown. |
| Checked date | Date time-sensitive evidence. |
| Version | Record affected product and resource versions. |
| Limitation | Name what remains unproven. |
| Correction route | Keep a path for evidence challenges. |
| Privacy review | Remove secrets, personal data, and private paths. |
Four evidence tracks
Sources and evidence tracks
Official facts, community profiles, tests, and unknown claims stay separate.
This evidence track cites the strongest source and leaves missing facts visible.
Official documentation
Use current first-party Pets guidance for product behavior and workflow facts.
Read current sourceCommunity profile
Name the non-official format source, version, and checked date.
codex pet formatFirst-hand test
Record a reproducible environment, method, outcome, and limitation.
codex pet compatibilityUnknown or disputed
Route missing, stale, or contested evidence to verification and contact.
contact codex petsQuestions before action
Codex Pet Not Showing FAQ
These visible answers describe current behavior and limits; no FAQ structured data or search appearance is promised.
Why is my codex pet not showing after I select it?
Confirm the intended product surface, Pets setting, and wake or tuck state. Then record the version before checking custom files.
Will a local custom pet appear on the web?
Current official guidance says local custom pets are not automatically synchronized to the web experience.
Does Blocked mean the pet package failed?
No. Blocked is an activity state. It is not a package-validation result.
Should I delete the existing pet files?
No. Preserve the original state and make reversible checks before removing or replacing anything.
Does this page upload local input?
No. Your input stays in local browser state while this page creates the display observation.
Does this page represent official OpenAI guidance?
No. This independent visibility check cites first-party documentation only for the specific product facts it describes.
What does Unknown mean?
Unknown means the available evidence is not sufficient to support a conclusion for the current context.
When should I recheck the result?
Recheck the display observation after its product, environment, source, permission, or review method changes.
Continue by intent
Relevant evidence and next steps
Every link reaches a real P0 route with descriptive anchor text and a matching intent.
One bounded next step
Build visibility checklistCodex Pet Not Showing: start with the local tool
Return to the first control, add only the expected surface, setting, and activity state, and compare the display observation with its limit.