People often misunderstand the workspace organization or totally forget about it. There's many ways to skin that cat and it's great you highlighted an efficient path!
The Claude Cowork vs Claude Code is slightly misleading. You can do most of the Claude Code work in Cowork. I build my entire .com and push to Github from Cowork and have it test the deployment on Cloudflare. Not having a separation is actually advantageous because you keep everything into one context and one "nice" UX. I also built and deploy my Make.com workflows from Cowork.
Cowork workspaces (projects) have CLAUDE.md too and it is a best practice to setup one locally. I have one for every workspace. Just no hooks :-(
Thanks! How did you manage to make Claude Cowork read Claude.md at the start of every session (like Claude Code would)? I tried global instructions and projects but it sometimes reads it and sometimes doesn't
And, yes, Cowork is great. Whenever I hit a wall with Cowork, I switch to Claude Code, though
Excellent article!
People often misunderstand the workspace organization or totally forget about it. There's many ways to skin that cat and it's great you highlighted an efficient path!
The Claude Cowork vs Claude Code is slightly misleading. You can do most of the Claude Code work in Cowork. I build my entire .com and push to Github from Cowork and have it test the deployment on Cloudflare. Not having a separation is actually advantageous because you keep everything into one context and one "nice" UX. I also built and deploy my Make.com workflows from Cowork.
Cowork workspaces (projects) have CLAUDE.md too and it is a best practice to setup one locally. I have one for every workspace. Just no hooks :-(
Thanks! How did you manage to make Claude Cowork read Claude.md at the start of every session (like Claude Code would)? I tried global instructions and projects but it sometimes reads it and sometimes doesn't
And, yes, Cowork is great. Whenever I hit a wall with Cowork, I switch to Claude Code, though