hatch-pet Recovery Checklist
See the skill source, expected state, and observed absence currently held in the browser.
Check the workflow boundary
hatch-pet Missing
A missing creation skill can be caused by an outdated session, incomplete skill installation, product version, or a workflow assumption copied from another surface. Capture the hatch-pet missing context and follow current official creation guidance before attempting a manual substitute. Start with the local, reversible action described by this practical hatch-pet missing 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
hatch-pet Missing workspace
Select what happened and which refresh steps were completed. No skill files are installed or downloaded. This page cannot inspect installed skills or change a Codex environment. It provides a safe sequence and links to the current first-party Pets documentation.
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.
Confirm the intended workflow
Start from the current first-party Create your own pet guidance.
Check session state
Separate a stale session from a missing bundled capability.
Avoid fake replacement files
Do not invent a skill bundle or community package to hide the failure.
Escalate with context
Capture version, session, surface, and exact observed message.
Facts before assumptions
Evidence map before action
This page cannot inspect installed skills or change a Codex environment. It provides a safe sequence and links to the current first-party Pets documentation. Before anyone acts, keep that boundary in plain view.
Creation workflow
Current official guidance describes a bundled hatch-pet skill in the custom-pet workflow.
Reload boundary
The documented flow includes reloading skills and opening a new chat.
Session evidence
A hatch-pet missing result in one session does not prove a global product defect.
Manual package risk
The hatch-pet missing symptom is not repaired by substituting an unrelated community archive.
Current documentation
Time-sensitive workflow claims should be checked against the official Pets page.
Meaning and boundary
hatch-pet Missing: evidence boundary
Capture the hatch-pet missing context and follow current official creation guidance before attempting a manual substitute. Keep local facts separate from cited guidance, named profiles, dated observations, and unverified hatch command.
Hatch-pet is the bundled OpenAI skill used by the documented Desktop Create your own pet workflow.
Recovery begins by preserving the existing project and configuration state before rerunning, reinstalling, or deleting anything.
The note identifies where the skill came from and which version or revision was expected to create the pet.
A missing result can mean the step never ran, wrote elsewhere, failed silently, or targeted another product surface.
The published local output contract uses ${CODEX_HOME:-$HOME/.codex}/pets/<pet-name>/ with pet.json and spritesheet.webp.
Command history can contain secrets and unrelated work, so only the necessary invocation and safe context should be retained.
Deterministic
Repeat the same check with the same visible input and compare the results.
Documented
Cite the first-party source and date behind a recovery checkpoint.
Community profile
Name the non-official profile, version, and publisher.
Running
Active work; not verification of recovery checkpoint.
Needs input
A request for attention; not evidence about unverified hatch command.
Ready
An activity state; not installation or rights confirmation.
Blocked
Interrupted hatch-pet recovery; not resource rejection.
Surface-specific limits
hatch-pet Missing across products
Desktop, Web, CLI, and IDE create different evidence needs for this hatch-pet recovery. 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 | The bundled skill writes the documented local two-file pet folder; refresh Settings > Pets after a completed run. |
| Web | Desktop-created pets do not auto-sync; upload the compliant 1536×1872 spritesheet separately when Upload pet is available. |
| CLI and terminal | Terminal rendering still requires a supported graphics path after any hatch-pet artifact has been located. |
| Windows, WSL, and IDE | Record whether the workflow ran on Windows, in WSL, or through an IDE task before searching the corresponding project boundary. |
Local capability
hatch-pet Missing without hidden submission
This local diagnosis control creates a recovery checkpoint without changing browser history or resolving the unverified hatch command.
Choose
Supply only the needed skill source, expected state, and observed absence.
Run locally
Create the recovery checkpoint 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
hatch-pet Missing 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
Check official guidance
Confirm the current workflow and supported surface before changing anything.
- 02
Record the environment
Capture product version, session type, and the exact missing-skill message.
- 03
Follow the documented refresh
Use only the current product-supported reload or new-chat sequence.
- 04
Report reproducibly
If still missing, submit environment, steps, expected result, observed result, and date.
Evidence checklist
hatch-pet Missing: evidence review
Useful evidence names the claim, resource, version, method, date, result, and limitation.
| Context | Evidence and limitation |
|---|---|
| Correct surface | The workflow is being attempted in the product described by current guidance. |
| Version known | The product version is recorded. |
| Skill list refreshed | The documented refresh step has been completed. |
| New session checked | A new chat or session has been tested when documented. |
| Exact error captured | The report records the visible message without sensitive data. |
| No substitute invented | No unsupported manual bundle is presented as an official fix. |
| 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
hatch-pet Missing FAQ
These visible answers describe current behavior and limits; no FAQ structured data or search appearance is promised.
What should I do when hatch-pet missing appears?
Confirm the current official custom-pet workflow, reload skills as documented, open a new chat when instructed, and record the version if the skill remains absent.
Can I download hatch-pet from this site?
No. This independent site does not distribute or impersonate an official bundled skill.
Does a new chat always fix the problem?
No. It is a documented workflow step, not a guaranteed repair for every environment.
What evidence belongs in a support report?
Include product version, session context, exact steps, exact visible message, date, and whether the documented refresh was completed.
Does this page upload local input?
No. Your input stays in local browser state while this page creates the recovery checkpoint.
Does this page represent official OpenAI guidance?
No. This independent hatch-pet recovery 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 recovery checkpoint 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
Show skill checklisthatch-pet Missing: start with the local tool
Return to the first control, add only the skill source, expected state, and observed absence, and compare the recovery checkpoint with its limit.