John Lindquist johnlindquist

Vercel AI Gateway OIDC Authentication Failure in Workflow DevKit

Executive Summary

When using the Vercel AI SDK with Workflow DevKit, AI Gateway authentication fails with GatewayAuthenticationError even when VERCEL_OIDC_TOKEN is present in the environment. The root cause is that the @vercel/oidc package requires Node.js fs module for token validation/refresh, which is not available in the workflow sandbox.

Environment

AI SDK Version: 6.0.50 (also tested with 5.0.76)
@ai-sdk/gateway: 3.0.23

Vercel AI Gateway OIDC Authentication in Workflow DevKit

Problem

When using the Vercel AI SDK with Workflow DevKit and vercel dev, OIDC authentication fails with:

GatewayAuthenticationError: Unauthenticated request to AI Gateway.

To authenticate, set the AI_GATEWAY_API_KEY environment variable with your API key.

Twitter Thread: Correct - Quick Announcement (ACCURATE)

Tweet 1 (Hook)

Workflow v4.0.1-beta.49: Custom class serialization.

Pass an Order to start() - arrives as a real Order. Return an Order from a step - workflow receives it with all methods.

Your business logic stays in classes, not scattered across plain objects.

Custom Class Serialization in Workflow v4.0.1-beta.49

The Problem: Losing Your Domain Logic

Before Workflow v4.0.1-beta.49, building durable functions meant making a painful choice: either flatten your domain objects to plain JSON, or manually reconstruct them in every step.

Before: The Manual Approach ❌

class Order {

Fast Key Repeat Settings for macOS

These settings make keys repeat much faster than the default System Preferences allows.

Current Settings

# Key repeat rate (lower = faster, default is 2)
defaults write NSGlobalDomain KeyRepeat -int 1

WezTerm Power User Config

A modular WezTerm configuration that combines the best of tmux, Zellij, and iTerm2.

Highlights

Zellij-Style Auto-Layouts

No more manual splitting decisions. Set a layout mode and let WezTerm figure out the rest.

| Key | Action |

WezTerm Power User Guide

A guide to WezTerm workspaces, pane management, and productivity tricks for users coming from iTerm2.

Modular Config Structure

The config is split into logical modules for maintainability:

~/.config/wezterm/

OpenCode Plugin Logging Infrastructure

What We Did

Added comprehensive session-based file logging to all 8 OpenCode plugins in .opencode/plugin/. Each plugin now logs every hook invocation, whether it triggered an action or was skipped.

Files Created/Modified

.opencode/lib/logger.ts - Shared logging utility
All 8 plugins - Added logTriggered() and logSkipped() calls to every hook

OpenCode Plugins Guide

A comprehensive guide to writing plugins for OpenCode that extend agent behavior with hooks, custom tools, and event handling.

Quick Start

Create a TypeScript file in .opencode/plugin/ (project) or ~/.config/opencode/plugin/ (global)
Export a named plugin function
Restart OpenCode

	#!/bin/bash
	# BSP Split: Find largest pane IN CURRENT TAB and bisect it

	# Get current pane from environment (set by WezTerm for shells running in panes)
	if [ -n "$WEZTERM_PANE" ]; then
	CURRENT_PANE="$WEZTERM_PANE"
	else
	# Fallback: use the pane passed as argument
	CURRENT_PANE="$1"
	fi