Dated Codex Pet Compatibility
See the surface, environment, version, method, and date currently held in the browser.
Compatibility needs a test
Codex Pet Compatibility
A pet can be visually correct and structurally valid while remaining untested in the product, operating system, terminal, or version a user actually runs. Select a surface and environment to see the minimum evidence required for a reproducible compatibility claim. Start with the local, reversible action described by this dated codex pet compatibility record; 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 Compatibility workspace
Select a product surface and environment to generate the required evidence fields. The matrix never converts an untested combination into Supported. Missing evidence is displayed as Not tested or Unknown.
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.
Multi-axis context
Record product, product version, operating system, OS version, and terminal or runtime.
Method attached
State what was installed, opened, observed, and removed.
Date attached
Compatibility can expire when products or packages change.
Limit attached
Static-only, partial-state, reduced-motion, or terminal restrictions remain visible.
Facts before assumptions
Evidence map before action
The matrix never converts an untested combination into Supported. Missing evidence is displayed as Not tested or Unknown. Before anyone acts, keep that boundary in plain view.
Desktop
Use first-party guidance for the floating companion and current settings behavior.
Web
Local custom pets do not automatically synchronize to web.
CLI
Checked 2026-07-26: official guidance requires iTerm2 3.6+ or a terminal with Kitty graphics or Sixel support; tmux and Zellij are not supported.
IDE
Checked 2026-07-26: the IDE extension does not provide the Desktop pet picker or floating overlay.
Community package
Every runtime profile needs its own source, version, and reproducible result.
Meaning and boundary
Codex Pet Compatibility: evidence boundary
Select a surface and environment to see the minimum evidence required for a reproducible compatibility claim. Keep local facts separate from cited guidance, named profiles, dated observations, and untested environment.
Compatibility belongs to a named product version and environment rather than to a character or package in the abstract.
The method records every setup condition another reviewer needs to reproduce the same observation.
Pass means the stated result occurred under the stated conditions; it does not promise future or universal support.
Fail describes an observed mismatch and should include the expected behavior, actual behavior, and safe diagnostic detail.
Unknown remains appropriate when the version, resource identity, environment, or reproducible method is missing.
A user report can suggest a test case but stays separate from a controlled first-hand observation.
Terminal records include emulator graphics support and multiplexer state because both can change the visible outcome.
Web image acceptance records file type, transparency, exact dimensions, byte size, and the date official guidance was checked.
Desktop observations distinguish built-in behavior from a community resource that lacks a documented package profile.
IDE testing asks only what the extension implements and does not borrow expectations from the Desktop floating overlay.
A new product release requires a new record rather than silently replacing the environment attached to an earlier result.
Deterministic
Repeat the same check with the same visible input and compare the results.
Documented
Cite the first-party source and date behind a compatibility observation.
Community profile
Name the non-official profile, version, and publisher.
Running
Active work; not verification of compatibility observation.
Needs input
A request for attention; not evidence about untested environment.
Ready
An activity state; not installation or rights confirmation.
Blocked
Interrupted reproducible test; not resource rejection.
Surface-specific limits
Codex Pet Compatibility across products
Desktop, Web, CLI, and IDE create different evidence needs for this reproducible test. 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 | A Desktop record names application version, pet source, activity state, method, observed behavior, and anything left untested. |
| Web | A web record checks the published transparent-image constraints and does not extrapolate from a local Desktop resource. |
| CLI and terminal | A terminal record includes iTerm2, Kitty graphics, or Sixel details and explicitly notes tmux or Zellij use. |
| Windows, WSL, and IDE | Host, subsystem, editor extension, and Desktop application each receive separate observations rather than one combined verdict. |
Local capability
Codex Pet Compatibility without hidden submission
This local compatibility control creates a compatibility observation without changing browser history or resolving the untested environment.
Choose
Supply only the needed surface, environment, version, method, and date.
Run locally
Create the compatibility 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 Compatibility 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
Choose the combination
Name the exact surface, versions, operating system, and runtime.
- 02
Identify the resource
Record pet version, package identity, and integrity value when supplied.
- 03
Run the method
Follow one documented install and state-observation procedure.
- 04
Publish the result
Store Passed, Failed, Partial, or Not tested with date and limitations.
Evidence checklist
Codex Pet Compatibility: evidence review
Useful evidence names the claim, resource, version, method, date, result, and limitation.
| Context | Evidence and limitation |
|---|---|
| Product | The consumer surface is explicit. |
| Product version | The tested version is recorded. |
| Operating system | OS and version are recorded. |
| Runtime | Terminal, shell, IDE, or other runtime is named. |
| Method | The test procedure is reproducible. |
| Outcome | The result and known limitations are explicit. |
| 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 verificationUnknown or disputed
Route missing, stale, or contested evidence to verification and contact.
contact codex petsQuestions before action
Codex Pet Compatibility FAQ
These visible answers describe current behavior and limits; no FAQ structured data or search appearance is promised.
What does codex pet compatibility prove?
It proves only the named resource was tested with the named method in the named environment on the recorded date.
Does a validator Pass prove compatibility?
No. Static checks and runtime behavior are separate evidence tracks.
Why is an empty matrix cell not marked Failed?
No test is not a failure result. It remains Not tested or Unknown until evidence exists.
Can one Windows result apply to WSL?
No. Native Windows and WSL are distinct contexts and need separate records.
Does this page upload local input?
No. Your input stays in local browser state while this page creates the compatibility observation.
Does this page represent official OpenAI guidance?
No. This independent reproducible test 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 compatibility 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 compatibility recordStart with the local evidence tool
Return to the first control, add only the surface, environment, version, method, and date, and compare the compatibility observation with its limit.