{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreie4kgt3spatiz6apdpeyy3x3thta7cvu3uwx62fkrwumunkaw5kx4",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mmrfv4u3fox2"
  },
  "path": "/t/subject-feature-suggestion-same-conversation-screen-app-context-for-specialized-workflows/1381827#post_1",
  "publishedAt": "2026-05-26T16:03:24.000Z",
  "site": "https://community.openai.com",
  "textContent": "I would like to suggest a ChatGPT feature that allows users to share screen or app context directly inside the same active conversation.\n\nThe issue is not simply “screen sharing.” The issue is continuity.\n\nFor long technical workflows, the current chat may already contain hours or days of important context: project goals, file paths, logs, debugging history, system architecture, prior decisions, failed fixes, successful fixes, and domain-specific language. If the user has to open a separate voice or screen-sharing session to show the assistant what is happening, the assistant may lose the specialized context from the existing thread.\n\nThis puts pressure back on the user. The user has to restate the whole project, explain what matters, copy logs, paste screenshots, describe what is visible, and rebuild the context manually.\n\nA better feature would be:\n\n“Share screen/app context with this conversation”\n\nor:\n\n“Attach current app state to this chat”\n\nThe important part is that the visual/app context attaches to the current thread, not a separate disconnected voice session.\n\nThis would be especially useful for specialized workflows like:\n\n  * coding and debugging\n\n  * market analysis\n\n  * trading-system monitoring\n\n  * terminal and log review\n\n  * IDE/Codex coordination\n\n  * dashboards\n\n  * app troubleshooting\n\n  * multi-agent workflows\n\n  * long-running technical projects\n\n\n\n\nFor example, if a user is building a trading system, the current chat may already contain the logic for order posting, ledger reconciliation, sizing, entry quality, inventory, sell-high thresholds, and risk rules. If the assistant could also see the current market chart, Coinbase order screen, terminal log, or Codex patch state inside that same conversation, it could help much more accurately without the user having to manually translate everything.\n\nSuggested feature behavior:\n\n  * user-controlled and opt-in\n\n  * share current screen, selected app, or selected window\n\n  * attach context to the existing conversation\n\n  * allow short session capture or one-time context packet\n\n  * include screenshot, visible text, app name, timestamps, logs, terminal output, or error state when approved\n\n  * allow user review/redaction before sending\n\n  * no hidden background capture\n\n  * no root/admin phone access required\n\n  * clear indicator when sharing is active\n\n\n\n\nThis would not just help one type of user. Many users likely run into the same issue: the assistant has the conversation context, but not the current app context. The user becomes the bridge between the screen and the chat.\n\nThe goal is to reduce that burden.\n\nIn short: ChatGPT needs a same-conversation screen/app context feature, so users can keep the full reasoning history of the current chat while adding live or captured visual context from the apps they are working in.\n\nThis would make ChatGPT much better for real-world technical work, market analysis, debugging, and long-running specialized projects.",
  "title": "Subject: Feature Suggestion — Same-Conversation Screen/App Context for Specialized Workflows"
}