Anton Gilgur

> * locks and parallelism will generally have different use cases. Is this entirely accurate? You might have seen more use-cases than me, but a lot of users do in...

Yea I generally agree on cluster-level parallelism. Workflow/template-level parallelism can blur the lines a lot, especially as that is user controllable just like semaphores. I'm wondering if maybe we split...

Was working on it last night, should be done soon

Oh looks like you made some changes while I was mid-review. No IRL synchronization 😅

I made the [two](https://github.com/argoproj/argo-workflows/pull/13393#discussion_r1739804849) [remaining](https://github.com/argoproj/argo-workflows/pull/13393#discussion_r1739805932) changes myself as one is broken syntax and the other is purely formatting. Since you set auto-merge I assume that's fine

Recently discovered [`mprocs`](https://github.com/pvolok/mprocs), which seems to do exactly this TUI-style filter

> * Mark one task as "main" and that is the one that is logged. Ostensibly this issue would be for this feature, but being able to do so interactively/dynamically

As an alternative to a _browser_-based UI, I might suggest a terminal-based UI, like [k9s](https://github.com/derailed/k9s) or [lazydocker](https://github.com/jesseduffield/lazydocker), using [`gocui`](https://github.com/jroimartin/gocui), [`tview`](https://github.com/rivo/tview), or similar tools. That would also fit nicely within Kit's...

Discovered [`mprocs`](https://github.com/pvolok/mprocs), which is basically what I suggested above

Interactive control: - Filter logs by task #56 - Dynamically start, stop, restart any configured process - Interactively add, duplicate, or rename processes (I'm not sure the use-case of this,...