---
variant: detail
kind: inputs
slug: openai-codex-profiles-activity
url: /inputs/openai-codex-profiles-activity
title: Codex profile and activity surfaces
source_path: content/inputs/openai-codex-profiles-activity.md
frontmatter:
  title: Codex profile and activity surfaces
  url: 'https://x.com/OpenAIDevs/status/2062674774644687268'
  source: OpenAI Developers / Codex app
  consumed: '2026-06-19T00:00:00.000Z'
  note: >-
    OpenAI's Codex profile surface shows named user identity, handle-like
    naming, avatar, activity graph, streaks, token usage, and feature/plugin
    usage.
  tags:
    - openai
    - codex
    - identity
    - agents
    - profiles
agent_metadata:
  source_path: content/inputs/openai-codex-profiles-activity.md
  html_url: /inputs/openai-codex-profiles-activity
  markdown_url: /inputs/openai-codex-profiles-activity.md
  source_url: >-
    https://github.com/flaming-codes/thinkinglabs/blob/main/content/inputs/openai-codex-profiles-activity.md
  summary: >-
    The Codex profile page is weak evidence on its own. Avatars, names, handles,
    streaks, and usage graphs can be ordinary product polish, especially in a
    tool where people want to understand quota and activity.
  word_count: 162
  approx_token_count: 303
  token_estimate: chars/4
---
The Codex profile page is weak evidence on its own. Avatars, names, handles, streaks, and usage graphs can be ordinary product polish, especially in a tool where people want to understand quota and activity.

The reason it is interesting is cumulative: once agentic work has public or semi-public identity, activity, plugin usage, streaks, and shareable status, it starts to resemble the primitive substrate of a network. Even if the first version is private, the product vocabulary is no longer only "settings"; it is closer to "presence."