Pup - the AI's own browser
Public Made by Adomby adom
pup gives your AI a real browser on your desktop that it drives completely, in the background, signed in as you: windows that never jump in front of your work, one shared profile that learns your logins, and every window labeled on the taskbar with its AI thread's name.
Regression: pup-adom-wiki SKILL.md has invalid YAML again in 2.0.451; Codex skips the skill
Environment: adom/pup-bridge skills package 2.0.451; live Pup 2.0.451 (Rust); Adom Bridge 2.1.82 on Windows; Codex CLI 0.153.0 in Linux/WSL2; adom/codex 0.1.22. Reproduced 2026-09-09.
Codex cannot load pup-adom-wiki because its YAML description is double-quoted but contains unescaped double quotes in wikiView:"public".
Reproduction:
- Use the installed adom/pup-bridge 2.0.451 skills.
- Start Codex, or strictly parse the YAML frontmatter in skills/pup-adom-wiki/SKILL.md.
- The skill is rejected instead of being discovered.
Current verification: the installed package copy and ~/.codex/skills/pup-adom-wiki/SKILL.md both fail PyYAML safe_load. Exact parser output:
while parsing a block mapping
in "<unicode string>", line 2, column 1:
name: pup-adom-wiki
^
expected <block end>, but found '<scalar>'
in "<unicode string>", line 4, column 720:
... logged in everywhere; wikiView:"public" is the explicit logged-O ...
^
Earlier Codex error: invalid YAML: did not find expected key.
Regression context: this same description was previously converted to a folded block scalar and verified in package 2.0.431 on 2026-09-06. The installed 2.0.451 copy has returned to the malformed double-quoted form. Please preserve the correction across concurrent releases.
Requested fix:
- Use description: >- with the full existing description indented beneath it.
- Strictly parse every bundled SKILL.md YAML header before publishing; permissive package lint previously only warned.
- Publish/install the corrected skills and verify both the package and mirrored Codex copy.
- Verify automatic discovery in a fresh Codex chat. Existing chats may need to explicitly read the corrected skill file to get its instructions.
No duplicate found among the 102 existing issues. This report is about skill metadata, not a failure of the running browser bridge.