Pat Bergstresser

13.5K posts

Pat Bergstresser banner
Pat Bergstresser

Pat Bergstresser

@PatThePM

I help Product Managers write with clarity to build trust, drive alignment, and focus on building. | Product @ Zillow | Building https://t.co/SQCmX1MYOI

Somewhere in the backlog Katılım Haziran 2022
420 Takip Edilen5.3K Takipçiler
Aakash Gupta
Aakash Gupta@aakashgupta·
Google just gave your AI agent a way to access every Workspace API that doesn’t eat half your context window. Here’s the problem everyone’s been hitting. The standard way to connect Claude Code or Cursor to Gmail, Drive, and Calendar is through MCP servers. Google ships official ones. They work. But MCP has a structural tax that gets worse the more tools you connect. One developer measured his Google Workspace MCP setup: 142 tools. ~37,000 tokens loaded into context. That’s 19% of a 200k context window consumed before the agent even starts thinking about your task. Another developer reported MCP tools eating 98,700 tokens total, nearly 50% of their entire context, and asked Anthropic for help. Cursor hard-caps you at 40 MCP tools because the problem is so bad. The CLI approach sidesteps this entirely. Your agent reads a lightweight skill file, calls gws drive files list via shell, parses JSON back. The tool definitions never enter the context window. Same capabilities, fraction of the overhead. But the architecture goes deeper. This CLI reads Google’s Discovery Service at runtime and builds its entire command surface dynamically. Google adds a new Workspace API endpoint, the CLI picks it up automatically. Every static MCP server is permanently one version behind. Google’s own blog post announcing managed MCP servers admitted the previous state was developers “identifying, installing, and managing individual local MCP servers, often leading to fragile implementations.” This CLI is Google’s answer to their own problem. One npm install. 100+ agent skills. Encrypted credentials. And if you still want MCP as the transport layer, gws mcp starts a server over stdio. The real signal: as agents get smarter, the bottleneck is shifting from “can it access the tool” to “how much context does accessing the tool cost.” CLIs win that math every time.
Addy Osmani@addyosmani

Introducing the Google Workspace CLI: github.com/googleworkspac… - built for humans and agents. Google Drive, Gmail, Calendar, and every Workspace API. 40+ agent skills included.

English
33
36
569
126K
Pat Bergstresser
Pat Bergstresser@PatThePM·
@stuholden I can’t speak to whether this exists or not. But if you build it yourself you’ll want to use something like @Replit @boltdotnew @Lovable . With a few prompts you can get a prototype running that works perfectly for you. No code needed at all.
English
1
0
2
66
Stu Holden
Stu Holden@stuholden·
Via Claude, Gemini, ChatGPT, etc. Thanks for reading and contributing— kind of excited to pull this together and experiment for next Summer!!
English
4
1
9
4.6K
Stu Holden
Stu Holden@stuholden·
Interested in open sourcing this and see where it goes: After the last World Cup, I transitioned my broadcast boards / notes from Paper Stickers to Digital. For the last few years I’ve used combinations of GoodNotes, Google Sheets, Slides, etc and nothing quite fits what I want…
English
1
1
21
10.2K
Pat Bergstresser
Pat Bergstresser@PatThePM·
@_Logor @Replit Haha true but I figure I would have done all the same steps anyway. Just faster and more efficient now
English
0
0
0
18
Prajeen Vijayan
Prajeen Vijayan@prajeenv·
@PatThePM This is real.. It is not about hustle, it is about mental ownership. When the product becomes part of your thinking, everything you do starts sharpening it ..
English
1
0
1
37
Pat Bergstresser
Pat Bergstresser@PatThePM·
"PMs need to work 60+ hours a week to be successful." It's bullshit. What isn't bullshit? PMs need to *think* about their product 80+ hours a week. When you do this, your 40-50 hour work weeks become much more optimized than everyone else who's slogging 60+ hours.
English
1
0
5
555
Parv
Parv@ParvSondhi·
@PatThePM 100% but so freaking hard to do. lol. so easy to get sucked into that envy loop
English
1
0
1
82
Parv
Parv@ParvSondhi·
Been thinking about this tweet a lot recently
Parv tweet media
English
4
3
63
7.3K
BasedBigTech
BasedBigTech@BasedBigTech·
@aakashgupta They’d also be sandboxed, not choosing tools on their own (v0, etc). No way it would be choose your own adventure. So something is off.
English
1
0
1
62
Pat Bergstresser
Pat Bergstresser@PatThePM·
@carlvellotti IMO the EM should be running these frankly. If they aren’t, influence that change. Worst case, PMs should be there to answer questions and ensure the user POV is maintained.
English
1
0
5
269
Carl Vellotti 🥞
Carl Vellotti 🥞@carlvellotti·
Running grooming meetings can be stressful for PMs, especially if you aren't technical. Here's an excellent template spotted on Reddit.
Carl Vellotti 🥞 tweet media
English
8
12
140
14.9K
Pat Bergstresser
Pat Bergstresser@PatThePM·
Why are so many vibe coded products just regurgitations of things that already exist? - Habit tracking - To do lists - Fitness - etc. Where’s the creativity?! Non-technical people now have the ability to actually be creative and so many aren’t actually being creative.
English
1
0
2
356
Pat Bergstresser
Pat Bergstresser@PatThePM·
@aakashgupta Personally fan of these types of cases. (Albeit cases are imperfect) In the end, PMs are evaluated on impact. And usually that’s measured through a metric. Being able to connect the dots between a product, the needle it moves, and how that impacts the business = foundational.
English
0
0
2
247
Aakash Gupta
Aakash Gupta@aakashgupta·
If you're preparing for PM interviews in 2025, there's one question type you cannot afford to mess up: Metrics. Here's the history of how it over took product hiring and why it's the silent killer of PM dreams:
Aakash Gupta tweet media
English
4
3
68
10.8K
Pat Bergstresser
Pat Bergstresser@PatThePM·
Also FWIW, average Reddit CTRs for ads is 0.2-0.4%. So all 3 were within a normal range.
English
1
0
0
199
Pat Bergstresser
Pat Bergstresser@PatThePM·
My take on next steps: - Speed is the winner - Having 1 leading val prop enables positioning clarity - Overall all 3 were close - Lead copy with speed, but leverage other two val props as supporting
English
1
0
0
230
Pat Bergstresser
Pat Bergstresser@PatThePM·
In order to better understand how to position Vibe Updater relative to PM pain points, I ran a positioning test on r/ProductManagement. Which do you think won? Creatives in the first reply (can't attach to poll). Answers in the second reply.
English
1
0
0
431