I have an idea to let MedGemma become the specialized local engine, MCP becomes the interface, and Claude/ChatGPT becomes the high-level reasoning/orchestration layer. First, this laptop is good enough to deploy the 1.5B MedGamma transformer on CPU.
The 4 Common OAuth/auth Patterns for MCP Servers
1. Standard OAuth 2.1 (MCP spec-compliant) Who uses it: Remote/hosted MCP servers (e.g., a server on Fly.io, Cloudflare, etc.) How: Full OAuth 2.1 flow — the MCP server is a resource server, a separate auth server (Auth0, Okta, Keycloak, etc.) issues tokens. Client discovers auth server via /.well-known/oauth-protected-resource, opens browser with PKCE, exchanges authorization code for access token. Example: An MCP … Continue reading The 4 Common OAuth/auth Patterns for MCP Servers
How AI Agents Browse the Web: From Fetch to Click
An AI agent can reason, write code, and call tools. But the web is where most real-world information lives. So how does an agent actually use a web page? The answer has evolved through three distinct generations, and which one your agent uses determines what it can and can't do. Generation 1: Fetch and Parse The simplest approach. The agent makes an HTTP request, … Continue reading How AI Agents Browse the Web: From Fetch to Click
How Coding Agents Manage Context
Context and Memory Management are difference: Context management = per-turn. "What fits in this prompt right now?" Deals with the model's finite window this request. Memory management = cross-turn/cross-session. "What should the agent remember for later?" Deals with persistence beyond the current request. Context management keeps the prompt usable now; memory management keeps knowledge alive later; summarization is the bridge where they overlap. why … Continue reading How Coding Agents Manage Context
How Coding Agents Manage Memory
Coding agents primarily utilize file-based rules along with in-session compaction; however, some agents like Claude Code and Cursor also depend on embedding-based cross-session memory. Although they can occasionally feature self-editing blocks, this approach is generally excessive unless the agent operates in long-lived sessions. First, same codes of in-session approach — no persistence, no embeddings. It's what most … Continue reading How Coding Agents Manage Memory
How an AI Coordinator Agent Can Fix Pickleball Court Utilization
An AI court coordinator watches your existing booking calendar (e.g., CourtReserve), compares real-time headcounts against ideal capacity for each session, and proactively messages the right group of players — organized by skill level — when a session needs more players or when a full session's waitlist could be redirected to an open slot elsewhere. It … Continue reading How an AI Coordinator Agent Can Fix Pickleball Court Utilization
Pickleball Court Coordinator Agent
A proposal to build an AI-driven scheduling and matchmaking coordinator Executive Summary The club runs 6 courts and an active, level-organized player base, but court time still goes underused: some sessions sit below a good headcount while others fill up and generate waitlists — even when a similar session nearby has open spots. Today, closing … Continue reading Pickleball Court Coordinator Agent
Planning on My AI Coding Workstation
I want to establish a simple and repeatable workflow for how I set up and use my Windows machine. The goal is not to install every developer tool available, but to create a fast, clean environment where AI can take care of much of the mechanical work while I focus more on architecture, problem solving, … Continue reading Planning on My AI Coding Workstation
Is RAG Fading Away?
RAG was very popular a few years ago, especially when companies were scrambling to build their own internal Q&A systems. The idea was straightforward: collect all your internal documents, split them into chunks, generate embeddings, put them into a vector database such as ChromaDB, retrieve the relevant chunks, and then let an LLM answer the … Continue reading Is RAG Fading Away?
Claude’s Sample Skill – Web Artifact Builder Skill
web-artifacts-builder is a Claude skill for producing richer interactive web artifacts—typically multi-component React interfaces—with a workflow that develops normally and then bundles the result into one self-contained HTML artifact. It is most useful for dashboards, multi-step tools, and polished UI prototypes rather than a tiny static page. First, let's see how it can be used, … Continue reading Claude’s Sample Skill – Web Artifact Builder Skill