ChatGPT shareable profiles: Codex usage, Sites and skills
This research library uses AI-assisted source research and drafting. Linked sources support product claims; analysis and proposed exercises are our interpretation. Unless an article documents a test and its results, do not read it as a hands-on review or an independently verified benchmark.
ChatGPT shareable profiles give every account a page at chatgpt.com/profile that shows your usage, your top plugins and the Sites you choose to display. OpenAI launched them at DevDay on 29 September 2026, and the shareable profiles help article lists what appears and who can see it. For developers the notable part is that the profile shows Work and Codex token usage and activity streaks, next to Sites you may have started from a Codex project.
What a ChatGPT shareable profile shows
The help article lists these items on a profile:
| Item | On a shared profile? |
|---|---|
| Chat message counts | Yes |
| Work and Codex token usage | Yes |
| Activity streaks | Yes |
| Top plugins | Yes |
| Sites | Yes, up to 12 that you choose |
| Conversation titles | No |
| Conversation content | No |
The article does not list repositories, prompts or code as profile items. If that changes, the help article is the place it will show up first.
Profiles are listed for Free, Go, Plus, Pro, Business and Enterprise in the DevDay recap. The help article says shareable profiles for Enterprise are coming soon, so Enterprise users may not see sharing yet.
Share your ChatGPT profile, or keep it private
Visibility depends on the account type:
- Personal accounts start private. Nobody sees your profile until you share it.
- Business accounts are shared within the workspace by default. Admins control this under Workspace settings > Permissions & roles > Member profiles.
Shared links use the format https://chatgpt.com/u/your-username, and viewers must be signed in to ChatGPT to open one. If you use Codex heavily on a Business plan, your colleagues can already see that token count unless your admin changed the default. Run this short checklist before you share the link:
- Open chatgpt.com/profile and read it as a stranger would.
- Check the Work and Codex token numbers and the streak. Decide whether you are fine with the audience seeing them.
- Review each Site you display and confirm its own audience setting.
- Share the
chatgpt.com/u/link only with people who have a ChatGPT sign-in.
What Codex token usage on a profile tells you
Token usage and streaks are activity data. They show that someone uses Codex often and in volume. They do not show whether the work merged, whether the tests passed, or whether a reviewer had to rewrite it.
That matters because a visible number invites comparison. A developer who runs long Codex sessions on a hard migration will show more tokens than one who fixed three bugs with short, precise prompts. Neither number says who did better work. Treat your own profile figures as a rough check on habits, for example whether you reach for Codex daily, and not as a score.
If your team wants to compare Codex use, compare outcomes instead: pull requests accepted after review, rework after the first review, and time from task to merge. We teach teams to measure that way in our Delegate, Review, Own method, because the diff and the review are where quality shows.
Put Sites built from a Codex project on your profile
A profile can display up to 12 Sites. ChatGPT Sites, in public beta on eligible Plus, Pro, Business, Enterprise and Edu plans, can start from an existing Codex project. That gives a practical route for internal tools: build a small dashboard or a docs page with Codex, publish it as a Site, and put it on your profile so colleagues can find it.
Each Site keeps its own publishing choice: selected people, your workspace, or public. The docs do not say that adding a Site to your profile widens its audience. Still, check the Site's audience before you add it, especially for a tool that reads internal data. On Business, Enterprise, Healthcare and Edu, Sites can also host supported ChatGPT plugins, and teammates use them with their own connected data and permissions.
Share a skill with your workspace
Profiles let teammates discover shared skills, and that sharing is limited to your workspace. Before you share one, know which kind of skill you have. The skill controls docs separate three paths:
| Skill type | Where it lives | Who controls it |
|---|---|---|
| ChatGPT workspace Skill | Shared or installed through ChatGPT workspace features | Workspace skill permissions and lifecycle |
| Local filesystem skill | Repository, user, admin or bundled location, used by Codex CLI | Filesystem distribution and local configuration |
| Plugin | Bundles skills with connectors, MCP servers, hooks and metadata | Plugin availability plus each bundled capability |
Profile discovery is described for shared skills in the workspace. The docs do not say it covers a skill that lives only in a repository for Codex CLI. They do state that moving a skill between paths does not transfer ownership, sharing, role assignments, plugin installation state or connector authorization. Plugins work in Codex in the ChatGPT desktop app and in the Codex CLI plugin browser, but not in the IDE extension.
For a team, the repo skill is often the better home for coding workflows, because it goes through code review with the rest of the repository. Share the workspace version when people outside the repo need the same workflow.
Pick one internal tool you built with Codex, publish it as a workspace Site, and add it to your profile after you have run the checklist above.