openai / openai/codex

[Feature Request] Codex Pet Companion — chat, affinity, interactions, mini-games, task management and task map

Open
#45,451 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app enhancement pets
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

I think Codex Pet could be much more useful if it became a small companion interface instead of only being a desktop animation.

A few features I’d like to see:

  • Pet chat — click the pet and open a small chat bubble without switching to the full Codex window.
  • Affinity / friendship — chatting, completing tasks, petting it, or playing with it could increase affinity and unlock animations, dialogue, expressions, accessories, etc.
  • More interaction — pet, poke, drag, feed, sleep, celebrate, and different reactions depending on whether Codex is working, blocked, waiting for input, or finished.
  • Mini-games — small games like coding quizzes, find-the-bug, guessing output, text adventures, etc. Some could optionally use normal Codex model usage, as long as the usage is clearly shown.
  • Task management — quickly see what is running, blocked, waiting for review, or completed, and jump directly to the related task/thread.
  • Task / project map — generate a mind map or dependency graph of the current project, showing tasks, subtasks, dependencies, progress, and blocked items.

The main Codex app would still be used for serious work. The pet would just be a quick way to ask things like:

“What are you working on?”

“Is anything blocked?”

“Show me the current tasks.”

“Show me the project map.”

Or just chat and play with it for a while.

I think this would make Codex Pet feel less like decoration and more like an actual companion for using Codex.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. First narrow the request to one companion capability and identify the relevant Codex Pet and desktop-interface entry points. Done should be defined as one bounded feature with a clear interaction, behavior, and validation criteria.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.