---
title: "Quentin Wendegass (@quentinw) | Hashnode"
description: "Software geek and founder of Privatrak. Read the latest articles by Quentin Wendegass on Hashnode."
url: "https://hashnode.com/@quentinw"
---

@quentinw

# Quentin Wendegass

@quentinw · Bangkok, Thailand · Joined October 2026

Software geek and founder of Privatrak

## Comments

[It says why, but not quite enough. The write gets a 409 with its own error code and "this setup run has been undone and takes no more changes; start a new one". So the agent knows the run is gone, but the message actually nudges it towards a fresh run, and nothing tells it the user undid those changes on purpose. I'll change it to say what was undone and to check with the user before redoing any of it. Thanks, that's a real gap.](https://hashnode.com/posts/we-gave-our-mcp-server-an-undo-button/6ad836b459e12396314dd304/comment/6ad9f6c433fb0a7d0ff0dbab#reply-6adde2f24c3bcf1186999326)

Reply · Article · Oct 25 · [We gave our MCP server an undo button](https://hashnode.com/posts/we-gave-our-mcp-server-an-undo-button/6ad836b459e12396314dd304)

[Yeah, we've been thinking about that too, change fail rate is a good way to put it. Counting the quiet fixes is a good catch, the undo rate alone would look better than reality.](https://hashnode.com/posts/we-gave-our-mcp-server-an-undo-button/6ad836b459e12396314dd304/comment/6ad8a032d9343ecc8bb271be#reply-6ad8bd089ad6f051d0fec7d0)

Reply · Article · Oct 21 · [We gave our MCP server an undo button](https://hashnode.com/posts/we-gave-our-mcp-server-an-undo-button/6ad836b459e12396314dd304)