Samuel Attard (@MarshallOfSound) profile picture

Cowork at @AnthropicAI | Former Desktop at @SlackHQ, Eng @ @NotionHQ | Creator of GPMDP | Helping build @electronjs | Contributing to Node, Chromium and OSS

Vancouver, British Columbia
Joined September 2013
Photo by Samuel Attard (@MarshallOfSound)Photo by Samuel Attard (@MarshallOfSound)Photo by Samuel Attard (@MarshallOfSound)Photo by Samuel Attard (@MarshallOfSound)Photo by Samuel Attard (@MarshallOfSound)Photo by Samuel Attard (@MarshallOfSound)Photo by Samuel Attard (@MarshallOfSound)Photo by Samuel Attard (@MarshallOfSound)Photo by Samuel Attard (@MarshallOfSound)Photo by Samuel Attard (@MarshallOfSound)
Samuel Attard retweeted
Today is a big day! We're launching a ~ new ~ version of Claude Code in the desktop app. It's been redesigned from the ground up for parallel work and is a lot faster. It's been my main way to use Claude Code for the last few weeks.
611
436
172
9,725
956,525
Samuel Attard retweeted
Excited to announce Claude for Open Source ❤️ We're giving 6 months of free Claude Max 20x to open source maintainers and core contributors. If you maintain a popular project or contribute across open source, please apply! claude.com/contact-sales/cla…
572
1,361
353
12,312
1,771,797
Samuel Attard retweeted
We just pushed out another Cowork update! It's mostly dozens of little fixes to papercuts, bugs, and performance issues - but we also support Macs with Intel processors now! Thanks to everyone who wrote in asking for it, your feedback really helps us prioritize 🙇‍♂️
25
7
247
13,454
Samuel Attard retweeted
Cowork on Windows! Early days, we're actively developing, so expect a lot of improvements and changes. Grab it at claude.com/download and let me know what you think! Some nerdy below-the-hood technical details in thread →
56
26
9
557
70,457
Building Cowork has been a little bit crazy, Felix explains it all quite well here. Now the preview is out we'd love to hear any feedback on how it's working for you, how it isn't, it's early and it's just going to get better.
Claude Code doesn't just resonate with developers anymore. Non-technical people are using it to build things. Technical people are using it for non-technical work. The line is blurring. I'm by far not the first to think about this. Multiple teams at Anthropic have been working on "agentic experiences" for months - Claude not just as a chat partner, but as something that helps you do real work. @bcherny nudged me: can we take what we've built internally and ship an early, scoped-down version in a few days? So we took a small team, set an aggressive deadline ("Monday sound good?"), and got to work. @claudeai wrote Cowork. Us humans meet in-person to discuss foundational architectural and product decisions, but all of us devs manage anywhere between 3 to 8 Claude instances implementing features, fixing bugs, or researching potential solutions. For native code, we use local Git worktrees on our local machines. For smaller or web-code only changes, we just tell Claude to go implement it. When someone reports a bug in Slack, we often just @-mention Claude and tell it to fix it. A human (and another Claude) reviews all code before it's merged, but we're now spending most of our time orchestrating a fleet of Claudes and making decisions than artisanally writing individual lines of code. We're releasing Cowork early. It has rough edges. But figuring out what to build is increasingly the hardest part of software engineering - and we think getting feedback early and hearing what users actually need is how we build something truly good.
1
3
787
Samuel Attard retweeted
Introducing Cowork: Claude Code for the rest of your work. Cowork lets you complete non-technical tasks much like how developers use Claude Code.
2,486
8,161
6,882
85,150
49,865,742
Samuel Attard retweeted
Claude Desktop is now generally available. New on Mac: Capture screenshots, click windows to share context, and press Caps Lock to talk to Claude aloud.
264
764
275
8,524
1,120,291
When is GitHub going to step up as the current stewards of npm and enforce 2FA globally. This keeps happening, and the answer is always "developers should enable 2FA" and not "the registry needs to change drastically". There are steps that be taken very quickly to make npm safer
🚨 Active supply chain attack on #npm: Multiple Prettier tooling packages were compromised through the phishing campaign we published about just hours ago. Watch out for more compromised accounts and malicious packages. Follow-up post: socket.dev/blog/npm-phishing… #nodejs
1
3
9
2,171
Who do I need to talk to to make any of these happen @martinwoodward? Heck if you sign me up as a contractor for $1 I'll build some of them for you.
1
2
270
The fact this keeps happening is great for @SocketSecurity, what @feross & team have built is amazing. But surely as an ecosystem we can be doing more to stop this kind of token compromise from even starting. GitHub owns the registry and the majority source of publishes (GHA)...
1
2
3
1,222
I don't know who needs to read this, but it isn't remote code execution if you have to run a command in a shell to do it.... That's physically local, and in the majority of cases is not a critical CVE. Good reference from the Chrome security team chromium.googlesource.com/ch…
1
9
1,042
Samuel Attard retweeted
Earlier today, the Electron team was alerted to several recent CVEs filed against an Electron Fuse setting. These reports are incorrect, and seem to be filed in bad faith. More information here: electronjs.org/blog/statemen…
2
8
4
36
9,027
Who do I talk to about 500kb of undici taking up 2MB in the node executable @ArrowoodTech 👀
4
3
1,080
This is important for anyone building electron apps to read. * Make sure you're up to date * Don't turn the sandbox off
3
10
2,313
Samuel Attard retweeted
Thinking of starting a YouTube channel in which I review PC cases from the perspective of "cat comfort" - how easy it is to get on top of, comfort while atop, airflow despite a cat blocking fans, safety of power button, etc.
9
6
1
54
M1 Max is gamechanging for people doing excessive amounts of compilation (read "work on Chromium"). My old fully specced out i9 macbook took 23 minutes to build Electron from source (using our distributed build + cache). The M1 Max does the same thing in 9 minutes flat...
4
11
3
58