And Cloud Functions for Firebase no longer needs "onFlow". There's direct support for Genkit in the new "onCallGenkit" function, which automatically turns a Flow into a Callable Function. Callable functions have always supported features like AppCheck natively.

For Next.js we'll use the firebaseContext middleware to enforce App Check and type safe client API. Again, if your flow supports streaming, so does the handler:

You can host this on any express path you want now. Streaming is automatic, and auth/context middleware is platform agnostic. Here, we use the "apiKey" middleware which stores, and optionally validates, an API key.

No matter where you want to deploy Genkit (on or off of Google Cloud) we can start with the following (streaming) Genkit code:

Last week, @firebase.com Genkit Node went 1.0/GA! Despite "Firebase", in the name we did a lot of work to ensure no risk Google lock-in (models or infra).

With Genkit you iterate quickly w/ high level abstractions. A property change lets you change models for flows or tools.

I like to take people along my (volatile) emotional journey while coding:

My wife got me a 43” 4K HDR USB-C monitor for Christmas. It’s so big that I can now see grain in my 4K RAW photos. And just in time Adobe Lightroom has AI tools to remove it! (At the cost of 10s/photo). For scale, that’s a 16” MBP next to it.

Nothing says "I might have fun paying bills this month" like a receipt for transferring $NaN.

Though moving is a pita, I have a feeling I’m going to like my morning coffee from the balcony

The Dyson after we spot cleaned the carpet that was supposedly professionally cleaned

When non-handy people get cheap. Looks like the last tenants decided to patch the wall everywhere to keep their deposit. They patched *over* screw anchors 😩

During COVID I moved to SoCal and leaned into scuba. Easy access to the Channel Islands was 🤌

Experimenting with what gets engagement here. Here’s a picture of manta rays in Kona

Brad Fitzpatrick chooses Route53 over Google Domains.