New UI results in unclear expectations in large monorepo where the task you actually want to run (at the very end) is hidden at the very bottom

[NullVoxPopuli]

Verify canary release

• [X] I verified that the issue exists in the latest Turborepo canary release.

Link to code that reproduces this issue

https://github.com/NullVoxPopuli/limber/

What package manager are you using / does the bug impact?

pnpm

What operating system are you using?

Mac

Which canary version will you have in your reproduction?

n/a

Describe the Bug

Simulation of the average VSCode-terminal user

Some questions people have had:

• what did I run?
• what am I waiting on?
• did it freeze?
• why isn't it doing anything?

these questions have lead to a lack of trust in the UI and reverting to disabling the new UI entirely (thanks for enabling that!)

---

This occurs in any repo with > 10 packages -- could shrink terminal height to simulate larger repo.

Because of the order of the tasks listed in the UI, the task you actually want is at they very bottom, or hidden entirely.

For example, here:

What task did I run? If I don't have cache, I may have forgotten as its not printed anywhere. (here I ran pnpm turbo _:lint)

And here, if ❯ pnpm turbo run start, with multiple start process, they're still all hidden at the bottom (and imagine the terminal is smaller, such as what is common for folks who use the vscode terminal) -- this is a surprising decent example for how a "flat list" is suboptimal, because I didn't initially see that there are some start tasks in the middle of the list as well. Mixing "end tasks" with "dependency tasks", is misleading / confusing.

Here I'm running for a specific app -- what command did I run? I ran:

❯ pnpm turbo --filter ./apps/repl/ start

Expected Behavior

The top of the UI shows

• what was ran
• what the end-task is, if we're waiting to start it (such as a persistent start / dev task)

To Reproduce

run any command with > 10 dependencies

Additional context

No response