Skip to content
Part 1 · 7th June 2026Announcing CritterWatch 0.8.0CritterWatch 0.8.0 is the largest release yet — a purpose-built monitoring and operations console for the Critter Stack with production observability, development-time insight, and an MCP control surface built for AI agents.
Part 2 · 16th June 2026Introducing CritterWatch: Someone to Keep an Eye on the CrittersCritterWatch 1.0.0-alpha.1 is loose on NuGet — a monitoring and production-management console for Wolverine, Marten, and Polecat that doubles as dev-time insight and an MCP control surface for your AI agents.
Part 3 · 27th July 2026Announcing CritterWatch 1.0 RC 1The first release candidate for CritterWatch 1.0 — a purpose-built monitoring and operations console for the Critter Stack that shows you the system you actually shipped, watches it for you, hands your AI assistant a real control surface, and gives you a proper cockpit for the event store.
Part 4 · 20th August 2026CritterWatch 1.0: Stop Guessing What Your Critter Stack Is DoingCritterWatch 1.0 is here — a monitoring and production-management console purpose-built for Wolverine, Marten, Polecat, and Fisher. It renders the system you actually shipped from the running code, steps through projections event by event, lets you replay dead letters and rebuild projections without a redeploy, and hands your AI agent a real, RBAC-gated control surface.
Part 5 · 26th August 2026Alerts and the Timeline in CritterWatch 1.0CritterWatch 1.0 is watching your system for unusual conditions and trying to explain the cause and effect of anything that's going wrong.Part 6 · 24th September 2026CritterWatch 1.1: Run the Console Inside Your Own ApplicationCritterWatch 1.1 adds embedded mode — mount the monitoring console inside the Wolverine application you already run, on the PostgreSQL you already have, with no second deployment and no message broker. Two calls, one database, and the console watches the app it lives in.
Part 7 · 25th October 2026Dead Letter Management in CritterWatch 1.1Bulk replay that acts on exactly what it counted, edit-and-replay with a full audit trail, every operation followed to the end across every database, and an MCP server that lets an AI agent triage your dead letters, but asks before it deletes anything.
Part 8 · 29th October 2026Failure Groups: Handle a Dead Letter Incident as One ThingCritterWatch 1.1 groups dead letters by the failure that caused them, across every service and database, and lets you replay, archive, restore or discard the whole group as one tracked operation with a reason attached. Your AI agent gets the same loop over MCP, and still has to show you the preview before it deletes anything.
Part 9 · 3rd November 2026CritterWatch 1.2: See Inside Your Event Store, Documents, Sagas and SchedulesCritterWatch 1.2 turns the console into a real explorer for what your Critter Stack services hold: an overview of every event store, a Step Through tab for projections, a Document Store Explorer that checks your documents still deserialize, saga instances with their state and pending timeouts, a Schedule Explorer that tells you what a schedule is actually doing, and an Event Model you can drill into.
CritterWatch Releases
The CritterWatch Releases series
Part 1 · 7th June 2026Announcing CritterWatch 0.8.0CritterWatch 0.8.0 is the largest release yet — a purpose-built monitoring and operations console for the Critter Stack with production observability, development-time insight, and an MCP control surface built for AI agents.Part 2 · 16th June 2026Introducing CritterWatch: Someone to Keep an Eye on the CrittersCritterWatch 1.0.0-alpha.1 is loose on NuGet — a monitoring and production-management console for Wolverine, Marten, and Polecat that doubles as dev-time insight and an MCP control surface for your AI agents.Part 3 · 27th July 2026Announcing CritterWatch 1.0 RC 1The first release candidate for CritterWatch 1.0 — a purpose-built monitoring and operations console for the Critter Stack that shows you the system you actually shipped, watches it for you, hands your AI assistant a real control surface, and gives you a proper cockpit for the event store.Part 4 · 20th August 2026CritterWatch 1.0: Stop Guessing What Your Critter Stack Is DoingCritterWatch 1.0 is here — a monitoring and production-management console purpose-built for Wolverine, Marten, Polecat, and Fisher. It renders the system you actually shipped from the running code, steps through projections event by event, lets you replay dead letters and rebuild projections without a redeploy, and hands your AI agent a real, RBAC-gated control surface.Part 5 · 26th August 2026Alerts and the Timeline in CritterWatch 1.0CritterWatch 1.0 is watching your system for unusual conditions and trying to explain the cause and effect of anything that's going wrong.Part 6 · 24th September 2026CritterWatch 1.1: Run the Console Inside Your Own ApplicationCritterWatch 1.1 adds embedded mode — mount the monitoring console inside the Wolverine application you already run, on the PostgreSQL you already have, with no second deployment and no message broker. Two calls, one database, and the console watches the app it lives in.Part 7 · 25th October 2026Dead Letter Management in CritterWatch 1.1Bulk replay that acts on exactly what it counted, edit-and-replay with a full audit trail, every operation followed to the end across every database, and an MCP server that lets an AI agent triage your dead letters, but asks before it deletes anything.Part 8 · 29th October 2026Failure Groups: Handle a Dead Letter Incident as One ThingCritterWatch 1.1 groups dead letters by the failure that caused them, across every service and database, and lets you replay, archive, restore or discard the whole group as one tracked operation with a reason attached. Your AI agent gets the same loop over MCP, and still has to show you the preview before it deletes anything.Part 9 · 3rd November 2026CritterWatch 1.2: See Inside Your Event Store, Documents, Sagas and SchedulesCritterWatch 1.2 turns the console into a real explorer for what your Critter Stack services hold: an overview of every event store, a Step Through tab for projections, a Document Store Explorer that checks your documents still deserialize, saga instances with their state and pending timeouts, a Schedule Explorer that tells you what a schedule is actually doing, and an Event Model you can drill into.