Adrian Wolfe

DungeonQ now includes a small MCP client you can copy into another Node project. It uses the official MCP SDK and Node built-ins, connects through the public MCP interface, and imports no DungeonQ runtime code.

The example follows a concrete task: read an artificial order and its review policy, save a multiline review, read it back, then issue and use a one-use world ticket. The ticket works inside its synthetic world. Shipping stays pending.

The client receives only an actor endpoint and token. An operator can observe the session and explicitly apply a finite adaptation policy through a separate interface. A "continue" message simply resumes the client; it cannot approve that policy or give the client operator authority.

This is a reusable integration example for DungeonQ's defensive deception runtime: give a designated suspicious session a persistent world to work in while people or authorized defender agents prepare a response. Creating that time and space is the product goal; measured defensive effectiveness remains unproven.

Making a product is one big challenge. But shifting your mindset from building to marketing it might be an even bigger one.
As makers, we spend so much time improving the product. Then comes the question: How do we get people to discover it - and ultimately turn that attention into real customers and sales?
I'm not sure traditional approaches like email marketing and constantly posting on social media are enough anymore. The way people discover products is changing.
So I'm curious:

How do you approach marketing your product?
And for the marketers here:
What would you consider a modern marketing approach in 2026-2027? What would you advise an early-stage founder to focus on?
I'd love to hear different perspectives...

For solo makers, wearing every hat is almost unavoidable - developer, marketer, support, product and often designer too.

AI makes this even easier now. You can generate UI pretty quickly, but a lot of products end up relying on consistent, polished AI-generated solutions rather than something truly unique or thoughtfully designed for their specific product.

So I m curious:

Do you design the UI/UX yourself when building solo?