
Chrome Extension foundation with a health indicator and retry queue
Phase 1 establishes the foundation: a health indicator, retry queue and capture history make the Chrome Extension reliable and transparent in everyday use.

Phase 1 establishes the foundation: a health indicator, retry queue and capture history make the Chrome Extension reliable and transparent in everyday use.

When I received "Ollama is not reachable", I faced a real architectural decision: install Ollama on the host or run it as a Docker container? The answer changed my entire deployment strategy.

A Chrome Extension has no "main.js". It has three completely isolated runtime contexts that must communicate through a strict message protocol. Understanding this distinction is what makes extensions robust rather than fragile.

I could have built Ollama directly into the backend. I could have built OpenAI directly into it. Instead, I built an abstraction layer that allows both, and understood why this is not overengineering but the only strategically sound decision.

Learn how we use Pagefind and Astro to deliver fast, static full-text search without expensive backend infrastructure.

How to combine performance and dynamic data synchronization in Power Pages. An architectural analysis of bypassing server-side caching with the Power Pages Web API.
Describe your workflow. Together, we will identify the right next step.
Discuss your workflow