Trace&AgenticBuilder

Two big improvements. First, I added a new agentic builder flow that helps turn a user’s intent into a workflow through planning, option generation, selection, and workflow creation. The builder can break down a request, evaluate possible workflow steps, show different options, ask follow-up questions, and let the user choose what should become part of the workflow.

Second, I added a much better diagnostics and tracing system so we can inspect workflow runs, follow events step by step, and debug problems more easily. The tracing work captures browser activity, API requests, builder stages, workflow runs, and individual workflow steps as structured diagnostic data.

I also added a diagnostics UI so these runs and events can be viewed instead of hidden in logs. I also updated many existing API routes so trace data and builder state can move through the app more reliably. Together, these changes make the workflow builder more useful, easier to understand, and much easier to debug.

I made this by splitting the work into a few focused packages and connecting them back into the existing Next.js app. The new agentic-builder package handles the builder flow: taking a prompt, resolving intent, evaluating possible capabilities, creating options, managing builder sessions, and exposing the builder through HTTP and MCP adapters.

I also added a builder-dag package to track proposed workflow changes as commits and branches. This lets the builder show preview options, mark choices as selected or rejected, and safely turn accepted plans into workflow changes. On the frontend, React and React Flow are used to stream planning progress, show workflow previews, display questions, and let users make decisions.