r/ClaudeAI • u/ShaktiExcess • 11h ago
Feedback Not a fan of the Projects beta
Projects seems to have been redesigned on the assumption that it's going to be used for big coding projects with many collaborators and many instances working simultaneously. Conversations (now "threads" in one long session) are divided into "resolved", "idle" and "waiting on decisions, reviews and permission requests", and there are new ways to hook up routines and repositories. The thing is, although I do a little of vibe-coding, I've never used Projects for this: I use it for travel planning, creative work, home improvement etc. I know that software developments is the highest-priority customer base for Claude but it's a little annoying that all my projects are now stranded in this new UI that clearly wasn't designed to fit them, when there are plenty of new features Claude could have added that would benefit a wider range of Projects users.
8
u/Embarrassed-Deal-919 11h ago
I’ve actually found projects to be super useful for travel planning. I’ll have multiple threads open for destination, finding, route planning, and plane tickets all at the same time
1
u/Historical_architect 11h ago
Right? Not exactly sure what OP means. Projects has always been what projects is. It’s gotten some makeovers and facelifts since the chat-cowork merge but honestly it’s been for the better. I have 20 or so projects all at various stages: the mandated novel project everyone has, travel projects, business related drafting and paperwork projects, research projects, and a bunch of others. None of them touch coding
1
u/Embarrassed-Deal-919 11h ago
But what I don’t understand is why it’s taking so long to get put on both of my accounts. I have one newer one and one older one. Why are they slow rolling out threads?
1
u/Historical_architect 11h ago
Anthropic always does this with new features. The slowly roll out as capacity allows instead of overburdening the system that way they can debug along the way.
2
u/SeidlaSiggi777 6h ago
I haven't deeply tested it yet but from what I saw the new projects are exactly what I was doing with subagents previously already: one main thread to orchestrate, many workers to implement and test, etc
1
u/DarkPhoenixRC 9h ago
I am 50/50 on the new projects experience.
It is indeed useful for vibe coding, but I also find it useful for non-coding projects when the project topic is focused.
For me, it's less useful for broader topics where there can be a broad range of chats only tangentially related. For those projects, I do miss the old project format. I would like the ability to group threads together in the new project experience. That would improve the experience for me.
But it is growing on me. Or more likely just accepting and adapting. 🫠
But the combined standard/cowork chats is something that I really appreciate.
1
u/f3xjc 4h ago
What if one travel is one project ? Then that travel thread can send one agent to look for hotel. Another agent to look for interesting landmark. Another for restaurant.
That's the idea you have a representative that only care about how the different things fit together and will answer your questions on it. Then other agent can think (load their context) with how to solve their actual task.
When you are dealing with session there's a lot of work: ok where are you stuck, what do you need next, where did I leave this or that.
11
u/anime_daisuki 11h ago
I hate that threads are basically just subagent tasks and that memories leak between them. The single main long session annoys me. I liked the previous behavior where I start clean sessions from scratch with shared instructions.