{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiejk7wq3qctpwmabckssuavocfsuxr32fwgnhrnl54rsq7vjsbuha",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3molsbhqzbbd2"
  },
  "path": "/t/codex-app-vs-cli-missing-threads/1384087#post_1",
  "publishedAt": "2026-06-18T21:41:28.000Z",
  "site": "https://community.openai.com",
  "textContent": "I’m on windows 11, codex pro lite, codex /app latest. Mostly using via cli inside jetbrains ide terminal.\n\nNoticed this thing:\n\nWhen starting a thread in cli and the first user message starts with /goal, the thread never gets into the list of threads for the project inside codex app conversations for the project.\n\nAlso if thread was started from cli, then switched to app, the cli does not sync (ok, understandable), but if you close terminal and start with codex resume, it points to where you’ve left in cli and ignores the messages sent/received via the app.",
  "title": "Codex app vs cli: missing threads"
}