Jeremy Loomis

DungeonQ's goal is to give security teams and authorized defender agents time and space to respond while a designated suspicious session works in a persistent synthetic world.

v0.15.0 adds a reproducible console showing the next step: what happens after an alert?

1. A real MCP client enters the workspace, checks conflicting claims and saves a note that survives restart. Wrong Tickets remain useful only inside their issuing world. A claimed "source restored" message does not change the route. Follow-up work is bounded and offers a stop; participant text cannot authorize operator changes.

2. A separate local receiver acknowledges an alert and rotates a temporary connector credential. Readbacks check that old authority and old-ticket use are denied, authorized new reads work, and those results survive restart.

You find an app that looks simpler or costs less. You try it, like it, then go back to the old one because moving your work feels like another project.

The awkward part might be:

AI can draft a reply, build a small app, or run a routine task. But being able to automate something does not always mean you want to hand it over.

Sometimes doing it yourself is how you notice a problem or understand what someone actually needs.