Samy Pessé

GitBook hosts 30,000 sites on a single Vercel deployment, and over 40% of their traffic is from AI agents. How they solve multi-tenant caching at scale ↓ vercel.com/blog/how-gitbo…

@steren What is the lifecycle for these instances? Is it possible to have them auto-stop when not receiving traffic?

Announcing Cloud Run Instances: A New Primitive to manage individual Cloud Run instances instead of through predefined resource types, starting in seconds. Designed for asynchronous, long running, background agents needing isolated, on-demand compute. Priced at $5.70 / month for 1 CPU (shared) + 1 GiB

In 2025, the number of Cloud Run external monthly active developers and applications doubled. If you are running AI Agents, vibe coded apps, AI inference, or scalable apps, there's something new for you at Next ‘26:

The State of Docs Report 2026 is live — insights from documentation experts across the industry on AI's growing role, how teams are measuring success, and where there are still gaps. Read the full report here: buff.ly/yMjIIsX

AI now accounts for 41% of docs readers — up from 9% at the start of 2025. That’s a 500%+ increase in AI readership in one year. Docs aren’t just read by humans anymore. They’re read for humans, by AI. Read more about what this shift means for docs: buff.ly/bZEhG8O

ICYMI — right before the holidays, we shipped smarter buttons in GitBook. Buttons can now trigger actions like search, open the GitBook Assistant, or even handle user input via the new input type. See what’s new at: buff.ly/tuQANjG

@yagiznizipli @Cloudflare The Google Cloud SDKs (Firebase/Firestore, Tasks, Storage)

Is there any npm package that isn’t supported by @cloudflare workers? (Except native addons)

@BenjDicken Right now a vector query crashes when going through hyperdrive

@BenjDicken Hyperdrive still lacks support for Planetscale Vectors; main blocker on our side to combine both

Guess what database pairs perfectly with Hyperdrive?

We’ll be in San Francisco this week for Ship AI’25! Book some time with our team here: gitbook.com

RT @vrenkema: @jh3yy this was fun, built a version of it into our new toolbar here at @GitBookIO

@clokehead @GitBookIO Hey Andy, We have changed our mind and we just released a site-level option for it: #discussioncomment-13542806" target="_blank" rel="nofollow noopener">github.com/orgs/GitbookIO…

So @GitBookIO thinks users can no longer be trusted with... Links that open in a new tab. Yeah, really. There are so many valid use cases for this, such a normal and expected part of the web. And Gitbook used to have them. @SamyPesse please fix this.

@makwarth 👀 Coming soon! Let's chat on Slack; I believe we can get this done for Bucket within a week

When onboarding new users, I sometimes create a personalized 5-step quickstart guide for them to get going quickly. We have a getting started guide on our docs but it's pretty generic and catch-all. I wish I could ask our documentation to create a personalized 5-step guide, based on our docs (all the information is in there, somewhere), that's tailored to 1) the user's stack and 2) the user's pilot use case - and share it with a link. (It's already possible to ask the documentation questions, which is fine, but it's not quite the same) Can I haz @GitBookIO @mintlify @readme?? 😺

✨ It's here! The State of Docs Report 2025 is live — packed with insights from industry experts on key trends, AI’s impact, and actionable advice to level up your docs strategy. Dive in and see why docs matter more than ever 👉 buff.ly/m6LHKS5

From open source to Times Square. We’re honored to be featured alongside @ThePledge - and grateful to everyone building and documenting in the open.

Manually documenting APIs: 😵‍💫 Auto-generated API docs in @GitBookIO : 🏄‍♂️✨ Just wrote a guide here → docs.gitbook.com/guides/product…

Back in 2023, our State of Developer Ecosystem Survey revealed that 90% of those who write documentation don't call themselves technical writers. Has anything changed? Our friends @GitBook are trying to find out in their State of Docs Report; we can't wait to see the results.

RT @chadwhitacre: @Welcome aboard, @GitBookIO! Our 33rd member company! Who else wants in?

@elithrar We moved this rule to "Log" for now (our Next.js is not exposed to this risk anyway), and we are upgrading Next at the same time. But my understanding is that any Next.js middleware making fetch() sub-requests to a Cloudflare domain will see this request being blocked now

@elithrar Appreciate Cloudflare trying to help there, but in our case, it caused a lot of false positives because our middleware in the Next.js app is making a request to our Cloudflare, and it looks like Next.js was including this heater, causing the sub-request to be blocked

We (@cloudflare) are going to deploy an automatic WAF rule that blocks requests w/ that can bypass Next.js auth middleware, including unpatched versions. You can also create a WAF rule right now on *any* plan by heading to <website> > Security > WAF > Create rule in the dash:

At @GitBookIO, we want to give doc teams the tools they need to show that documentation is more important than most teams realize. That’s why we’re collecting insights on the current state of documentation—and we need your input as help! Join the survey: stateofdocs.com