Renee Sullivan

Hey all - hope you’re enjoying the summer season and whatever festivities you enjoy. Been watching some FIFA World Cup here :) Question specifically for those who continue learning, growing and sharpening their AI skills with : - Claude Cowork Or - Claude Code Or - something else? - Answer the poll & Share why you make your choice. Totally personal opinion - Claude Cowork is awesome - and still I lately rarely use it because Claude Code is that much better. For me, it’s my AI Chief of Staff and runs / routes tasks to my 145+ AI agents as needed. Which is kinda crazy because Claude Cowork is also so incredibly powerful when you know how to use it - and you actually don’t really need to be technically at all to use it. Claude Code - it definitely helps to be more technical. BUT frankly once you get over the learning curve of connecting with a GitHub repository from the Claude Desktop and pair it with an AICOS Atlas Folder, and if you’re willing to learn a *little bit* about how to use it in Terminal, Obsidian, and other tools like Cursor… It makes Cowork look like child’s play. Which must then mean that regular Claude Chat is like an infant baby by comparison. Which is quite aligned with its relationship with Cowork. Cowork is like Claude Chat’s slightly older brother who figured out how to do a lot more and Chat is still in diapers always forgetting where it left its toys. AKA AI amnesia. Cowork is already figuring this out once you take the time to train it. Like you would a new hire. But (IMO) it’s still looking up to its bigger older smarter better brother Claude Code. Who’s can run laps around Cowork when it’s focused and not distracted building new shiny toys that it can sometimes make on its own or if left without proper direction. But - and this is a serious caveat - a lot of people do not really need to be using Claude Code. Especially when they are getting started. Just getting good and comfortable with Claude Cowork is often far more than enough to do what the majority of people need - obviously this depends heavily on the person or company goals.

Poll

13 members have voted

New comment Aug 1

Claude Mastery Poll: Would you rather? (And WHY?)

Renee Sullivan

1 like • Aug 1

Claude Code all the way although they are for two entirely different things. I use Claude Code to build the tthis and Claude Co-work to complete the task/workflow. For instance I'll use Claude Chat to toss ideas back and forth and then Opus will produce two briefs. One for co-work - I needed it to use the browser specifically to go through a few hundred links and pull relevant data on a new project I'm researching. I let it go for three hours while I was at work. It downloaded all the data necessary for the build, collated it into folders, and wrote manifests, logs, and structured findings and analysis in a handover for Fable (I have a co-work brief skill that Opus uses). And Claude Chat will also produce the design brief for Fable (I have another skill for this). Fable then can use all the research gathered by co-work for the build. Note that not all research will need to be done by co-work. Sometimes it's much cheaper to get fable to spin up cheap minions but if you need some reasoning and analysis to go into it then co-work is a good answer. Fable's brief specifies: - the human problem - my vision for what I'm trying to achieve - what done looks like - gives it some edge cases that need to be accounted for - reminds it that it is the architect and not the bricklayer so it can orchestrate and delegate tasks as necessary to the most suitable agent, with consideration to required output and token economy. And then I give it room to do what it does best, which is come up with the best solution to my problem and build it.

1-1 of 1

Level 1

4 points to level up

Renee Sullivan

@renee-sullivan-9025

I never get tired of hearing new perspectives, learning new things, and meeting new people.

Active 41d ago

Joined Jul 31, 2026

Contributions

Followers

Following