• Home
  • Technology
  • Gaming
  • Entertainment
  • World & Business
  • Science
  • Sports
  • AI
HomeTechnologyGamingEntertainmentWorld & BusinessScienceSportsAI
    • HomeTechnologyGamingEntertainmentWorld & BusinessScienceSportsAI
    • Home
    • Technology
    • Gaming
    • Entertainment
    • World & Business
    • Science
    • Sports
    • AI
    AI

    Every Executive Uses Codex Threads for Work

    Every COO Brandon Gell relies on persistent Codex threads for all workstreams instead of one-off chats.

    DS
    BG
    2 Sources, 29d ago, first seen 29d ago

    TLDR

    Brandon Gell, COO of Every, posted that he and nearly everyone at the company now structure work around ongoing Codex threads. He avoids one-off chats and compaction concerns. Gell listed OpenAI improvements he wants, starting with folders to group chats and an emoji selector. The post includes a screenshot of the Codex sidebar. No other details or responses appear in the packet.

    Combined views

    72K

    2 Sources, first seen 29d ago

    Combined views

    72K

    2 Sources, first seen 29d ago

    499 likes
    499 likes
    63 comments
    555 saves
    31 reposts

    Sentiment

    Positive——Negative

    Summary

    Not enough discussion yet.

    No sentiment analysis available yet.

    63 comments
    555 saves
    31 reposts

    Sentiment

    Positive——Negative

    Summary

    Not enough discussion yet.

    No sentiment analysis available yet.

    Today's Rank

    —

    Not ranked yet

    Today's Rank

    —

    Not ranked yet

    2 Sources

    @bran_don_gellThis is how I work now. Actually it's how almost everyone at @every works. Every workstream has an ongoing thread in Codex. I never make one off chats and I never worry about compaction. There's SO MANY THINGS OpenAI can do to make this better. A few ideas: 1. Folders. Let me group chats together 2. Emoji selector. It's a design bummer but it's visually so much more appealing and easier to find pinned threads 3. Remove the chat bubble icon ya'll just launched. Nothing in the UI should be repetitive like that IMO. 4. Enable me to fork convos much more easily. Those should be worktrees that live inside of each chat like a folder would work. 5. SHARED CHATS with easily forked convos that all have the same context. Killer feature and makes Codex multiplayer. 6. Make HQ a feature. It's my ongoing to-do list but it's just not built for chat. I need a kanban board or something that i can kickoff codex sessions from.
    @danshipperRT @bran_don_gell: This is how I work now. Actually it's how almost everyone at @every works. Every workstream has an ongoing thread in Cod…

    2 Sources

    @bran_don_gellThis is how I work now. Actually it's how almost everyone at @every works. Every workstream has an ongoing thread in Codex. I never make one off chats and I never worry about compaction. There's SO MANY THINGS OpenAI can do to make this better. A few ideas: 1. Folders. Let me group chats together 2. Emoji selector. It's a design bummer but it's visually so much more appealing and easier to find pinned threads 3. Remove the chat bubble icon ya'll just launched. Nothing in the UI should be repetitive like that IMO. 4. Enable me to fork convos much more easily. Those should be worktrees that live inside of each chat like a folder would work. 5. SHARED CHATS with easily forked convos that all have the same context. Killer feature and makes Codex multiplayer. 6. Make HQ a feature. It's my ongoing to-do list but it's just not built for chat. I need a kanban board or something that i can kickoff codex sessions from.
    @danshipperRT @bran_don_gell: This is how I work now. Actually it's how almost everyone at @every works. Every workstream has an ongoing thread in Cod…