ConversationDeck
A FEW STEPS TO GET GOING

Setup & support

Install ConversationDeck, set up your Inbox, and pin tasks to keys.

Before you start

You’ll need macOS 13+, Stream Deck 7.3+, and a compatible local Codex desktop installation. Some compatible builds are named ChatGPT on your Mac. ChatGPT Classic and web-only tasks are not supported.

No separate Node installation, plugin account, API key, browser extension, or Accessibility permission is required. The plugin uses keys, not dials.

Install ConversationDeck

  1. Open the supplied .streamDeckPlugin installer and accept Stream Deck’s installation prompt.
  2. Open the Codex desktop app and create a local task on this Mac.
  3. Find ConversationDeck in Stream Deck’s actions list.

Set up Attention Inbox

  1. Drag Attention Inbox to an empty key.
  2. Finish a new task in Codex. Its new completion appears on a blue DONE key. Older completions are hidden during initial setup.
  3. Press the key to open the task. Once macOS accepts the open command, that completion leaves the Inbox.

Add more Inbox keys to show more tasks. They fill left to right, then top to bottom. Errors come first, followed by input requests, unread completions, and confirmed active work. Pressing rotates within a priority level; errors and input requests remain until resolved in Codex.

Reading a completed task directly in Codex clears its Inbox item when compatible desktop read status is available. Working keys can be pressed repeatedly to cycle through active tasks. After restarting Stream Deck, open your Inbox page once to activate monitoring.

Pin a task

  1. Drag Task Status onto a key.
  2. Search for a task under Task on this key and select its row. Wait for Saved.
  3. Optionally enter a short Button name and leave the field to save it.

The key follows the task’s ID, so renaming a task keeps its assignment intact. Press it to open the task.

Know the limits

Monitoring covers the newest 300 unarchived top-level local tasks, with up to 64 live subscriptions. Archived tasks, sub-agent tasks, and older catalog entries are excluded. New task discovery can take about 15 seconds; recorded status refreshes roughly once per second.

Long or unreadable histories and incompatible desktop versions can limit coverage. Live approval and working status depend on an internal desktop connection that may change with updates. A completion means a recorded turn finished, not that its tests passed or its objective was achieved.

Common questions

Why are there no tasks in the picker?

Open the compatible desktop app, create a local task, and select Refresh in key settings. Check for a plugin update after a desktop update. Do not edit the task database.

Why hasn’t a completion appeared?

Initial setup hides older completions. Allow 15 seconds for new tasks, open the Inbox page after a Stream Deck restart, and check settings for limited coverage. Errors and input requests take priority; add more keys to show completions in spare slots.

Why does a task remain after I open it?

Errors and input requests remain until resolved. A blue completion remains if the macOS open command fails. A later completion in the same task is a new Inbox item.

Can I include completions from VS Code?

In Inbox settings, expand Completion sources and enable “Include completions outside the desktop Inbox.” This applies to all Inbox keys. In this mode, use Inbox key presses or the reset control to clear completions; reading tasks manually in Codex will not clear them.

How do I start with a clean Inbox?

Expand “Start with a clean Inbox” in settings and choose “Mark completions as seen.” This preserves pinned assignments and Codex history, and does not erase Stream Deck backups.

How do I check the physical display?

Select a ConversationDeck key and click “Preview red error on this key.” It displays TEST ERROR for 15 seconds, then restores live status. Pressing ends the preview without opening a task or marking anything seen.

Need a hand?

Email support@verdinstudio.dev with your plugin, macOS, Codex, and Stream Deck versions; your device model; and the steps to reproduce the problem.

Please redact sensitive task names and screenshots. Do not send full databases, transcripts, session files, or API keys. See our privacy policy for how local task data is handled.