Skip to content

Thursday, March 12, 2026

Daily picks

15

articles scored

#1 GOLDReleaseClaude Blog

Advancing Claude for Excel and PowerPoint

  • Claude can now share information across multiple Excel and PowerPoint files in one conversation, so it remembers context when you switch between them and doesn't make you re-explain things
  • Instead of manually bouncing between Excel and PowerPoint, you can do complete workflows (like pulling financial data, building analysis tables, dropping results into slides, and drafting emails) without switching tabs or repeating yourself
  • "Skills" let you save common workflows as one-click actions—so if someone figures out the best way to run financial analysis or build a pitch deck using your company's template, the whole team can instantly use that process
  • The update includes pre-built starter skills for common tasks like checking spreadsheets for errors, building financial models, cleaning up messy data, and reviewing presentation decks for consistency
  • Claude for Excel and PowerPoint now works across Amazon, Google, and Microsoft's cloud platforms, making it available no matter which system your company uses
#2 SILVERUpdateClaude Code Releases

v2.1.74

  • The `/context` command now gives you specific tips on how to optimize your setup, like pointing out which tools are using too much memory and suggesting fixes
  • There's a memory leak fix that was causing the app to slowly eat up more and more RAM when streaming responses got interrupted — this was especially bad for npm users
  • A bunch of security and permission fixes: managed policy rules weren't being respected, voice mode wasn't asking for microphone permission on macOS, and OAuth authentication would hang or never re-prompt when tokens expired
#3 BRONZEBug ReportReddit r/ClaudeCode

Claude Code eats 80+ MB/min of RAM sitting idle. Here's what's actually happening.

  • Claude Code has a memory leak problem where it uses 38MB+ of RAM per minute even when doing nothing—your fans spin up because it's eating memory, not because it's working hard, and the leak is hidden in native memory that the garbage collector can't see
  • There are at least 4 different bugs causing this across Mac, Linux, and WSL, with a temporary fix being to restart your session every 1-2 hours, disable statuslines, or downgrade to an older stable version (v2.1.52)

Made with passive-aggressive love by manoga.digital. Powered by Claude.