Feature request: “My AI Team” — persistent named specialists with roles and avatars
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
The issue names no files, tests, or repository entry point; first confirm whether the ChatGPT Work/Codex Work interface belongs in this terminal Codex repository. A contribution would need an accepted design and scoped implementation plan covering persistent specialist instructions and context, sidebar identity, and pause or archive behavior.
Written by the indexing model from the issue text.
Description
What variant of Codex are you using?
ChatGPT Work in a web browser (Codex Work mode)
What feature would you like to see?
I would like to propose a feature called “My AI Team” for ChatGPT Work / Codex Work.
Many users work with several long-running chats at the same time. Each chat gradually develops its own responsibilities and context, but visually the chats look almost identical. This makes it difficult to remember which chat is responsible for which task, and users may accidentally write to the wrong chat or repeatedly explain the same requirements.
The proposed feature would allow a user to create persistent digital team members and:
- choose a name and avatar for each team member;
- define their role and responsibilities;
- specify what they should and should not do;
- set the expected working style and quality standards;
- preserve each member’s own instructions, working history, and context;
- display the member’s name, avatar, specialization, and current assignment in the sidebar;
- edit the instructions, pause the member, or archive the role.
For example:
- Nyusya — questionnaires and client materials;
- Lyusya — website content;
- Marusya — images and visual design;
- Petya — testing and quality control.
This is more than adding avatars to chats. Names, faces, roles, and persistent context would allow users to build and manage a recognizable team of specialized AI assistants.
The feature could reduce repeated explanations, prevent tasks from being mixed between chats, and make parallel work much easier to manage. It could be especially valuable for business owners, managers, older users, non-technical users, and anyone working on several long-term projects.
If this request belongs to another OpenAI product area, please route it to the team responsible for the ChatGPT Work / Codex Work interface.
Additional information
I previously managed a team of approximately 50 people, so I naturally began organizing my ChatGPT chats as employees with different responsibilities.
Today I accidentally wrote a sentence in the wrong chat. Because the assistant responsible for that task had already been given the name “Nyusya,” I immediately noticed the mistake and remembered where the message belonged.
This showed me that names and avatars are not merely decorative. They act as visual and mental landmarks: the user immediately recognizes who they are working with, what has already been discussed, and what that particular specialist is responsible for.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- Avg merge
- 1m
- Merged PRs (30d)
- 1k
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openai/codex
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug CLI windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
macOS sandbox blocks hw.optional.arm64 sysctl, causing Flutter to misdetect Apple Silicon as x64 Openbug CLI sandbox
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug CLI TUI
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
CLI config enhancement skills
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
A-linter
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oxc-project/oxc#26863 ·