Thanks for participating in the discussion Felix. A big issue for me - not sure if others suffer from this - is that it’s next to impossible to track work in pr

Thanks for participating in the discussion Felix. A big issue for me - not sure if others suffer from this - is that it’s next to impossible to track work in progress, especially with when there are artefacts involved or reports etc. Things that require multi-day work of back and forth and reflection. Chat is a horrible interface for this, having to scroll up and down across lengthy conversations to try and pick up a thread. I’m really sorry but I really fail to understand why this massive push to “chatify” everything. A task with its own context and multiple chats feel like a much better approach to work. Even if the work is spawned from a main chat window - eg “Claude we need to work on XYZ” and it creates a task to track this piece of work. Further, recurring tasks again are really really hard to manage with a chat interface - which of the 10 chats has that question that the recurring task raised?! And of course all this UX debt will likely stand in your way of building reactive items - ie spawning a task in response to some outside event. Think an inbound email being handled by a prompt that triggers a task and creates a draft response ready for my review and approval. Very hard to do with chat windows.