My terminal tabs used to become a task-management system by accident.One tab contained a Codex session fixing a UI problem. Another was analyzing an API. A third was waiting for permission to run a command. When I remembered an extra requirement, I first had to find the right terminal, read enough history to confirm the task, and then add the message.The work itself was automated. Managing the automation was not.The new Codex Agents Dashboard changes that. It provides one terminal view for local tasks, while codex queue lets me send an instruction to a session without opening it first.See it in action:https://youtu.be/O_OCwzKPAHY?embedable=trueOne command center for several agentsThe dashboard starts with:codex agentsIt groups tasks by project and separates them into states that answer the question I actually care about: where is my attention needed?Need input means the agent is blocked on me. Working means I should usually leave it alone. Ready means there is something to review.That is a better model than “which terminal tab changed most recently?”When I open a task from the dashboard, I get its complete transcript. When I am finished, /agents returns me to the command center.Names turn sessions into manageable workThe feature became much more useful after I started renaming tasks.An automatic title such as “Please inspect the project and fix...” is difficult to scan and difficult to target from a command. A short name works better:checkout-regressionmobile-navigationdatabase-migrationPress Ctrl+R in the dashboard, or run this inside the session:/rename mobile-navigationThe transcript does not disappear. Only the saved name changes.The command that removes terminal huntingNow imagine that mobile-navigation is still running and I remember another requirement. From any terminal, I can send:codex queue \ --thread "mobile-navigation" \ --message "Also test keyboard navigation and the 320px layout."I do not have to open the session first.For a one-off message, the exact task name is convenient. For a script, the session UUID is safer:codex queue \ --thread "01a01234-abcd-7890-1234-123456789abc" \ --message "Run the full test suite and summarize failures."The UUID is available from /status inside the task.Images can become instructions tooSome requirements are easier to show than describe. codex queue accepts an image attachment:codex queue \ --thread "mobile-navigation" \ --message "Match the header spacing to this reference." \ --image "/path/to/header.png"That makes the command useful for visual bugs, design references, and screenshot-based review feedback.The workflow I now useI start with the dashboard, not with a search through terminal tabs.Run codex agents.Rename important tasks.Open everything marked Need input.Review Ready work.Leave Working sessions alone unless they need a new constraint.Send quick additions through codex queue.Use UUIDs for automated messages.This does not make parallel work free. More tasks still mean more decisions and more output to review. What it removes is the unnecessary navigation cost.A small interface with a larger implicationAs coding agents become more autonomous, developers need tools for supervising work, not only starting it.The Agents Dashboard is an early example of that shift. The primary interface is no longer a single conversation. It is a queue of active, blocked, and completed tasks competing for human attention.codex queue completes the pattern by separating task communication from task navigation. A person or script can add context without first taking over the session UI.The most useful habit is still human: give every important task a clear, unique name.