Ever wished you could peek under the hood of your Forge app (while it’s running) and fix things on the fly? Traditional debugging tools live outside your application, forcing you to jump between logs, dashboards, and backend scripts. At Elements, we wanted a faster, more integrated way to understand what happens inside our Forge apps as they run.

In this session, we’ll show how we built a developer-mode debug tool for Forge apps that any team can adapt using an extensible architecture. You’ll see how modular UI components, reusable resolvers, and a structured layout enable safe in-app data inspection and live testing without leaving the app.

Whether you’re building internal tools or large-scale Marketplace apps, you’ll take away patterns for embedding observability and debugging directly into your own Forge experiences — enabling faster iteration and a deeper understanding of how your apps behave.

Key takeaways:

• Discover and see in action the real power of Elements Forge DevTools — a demo showing how we use it to relaunch Forge functions, inspect resolver data, manipulate stored data, and validate computations directly inside a Forge app
• Learn how we built it — from designing reusable Forge UI components to managing resolver calls and app state between the host and debug panel
• Hear what worked (and what surprised us) — lessons learned from experimenting with context handling, performance, and maintainability while building the tool