Master smith at the dashboard control room, wall of glowing amber screens showing live gauges, charts, and status lights
Chapter 7 · Forge-Master Studio

Dashboard — Forge-Master Studio

The reasoning orchestrator's home in the dashboard. Part of Chapter 7: The Dashboard.

Part of Chapter 7, This page covers the Forge-Master top-level group. See The Dashboard for the Forge group tabs, Dashboard — Settings Group, and Dashboard — LiveGuard Tabs.

Forge-Master Studio Tab

The reasoning orchestrator's home. See the Forge-Master chapter for the deep dive. Three panels:

  • Prompt gallery, pre-built prompts grouped by intent (operational, troubleshoot, advisory). Click to populate the chat box; edit before sending.
  • Streaming chat, POST /api/forge-master/chat to start, then subscribes to GET /api/forge-master/chat/:sessionId/stream. Shows live classification badge with the via field (keyword / embedding-cache / router-llm), quorum-estimate cost preview if advisory mode triggers (with cancel button), live tool-call trace, and the streaming reply token-by-token.
  • Embedding cache tile, pulls from GET /api/forge-master/cache-stats. Shows {size, hitRate, maxSize: 500}. When cold, displays a hint that hits start once you've used Forge-Master a few times.

Classification Badge

Every Forge-Master response shows a classification badge indicating how the intent was routed:

Via valueMeaning
keywordFast-path: matched by keyword rules, no model call for routing
embedding-cacheHit the write-through embedding cache, free re-route
router-llmRouter model called to classify intent (stage 3 fallback)

Quorum Advisory

When quorumAdvisory is set to auto or always in Settings → Brain, advisory-lane responses show a quorum-estimate cost preview before the models are called. A cancel button aborts the quorum dispatch if the estimated cost is too high.

Session Persistence

The Studio tab maintains a persistent per-tab session ID in sessionStorage and sends it as x-pforge-session-id on every request. This means prior turns survive page reloads and New Chat resets, Forge-Master can reference earlier messages in the same browser tab session.

Session history is stored as JSONL in .forge/fm-sessions/. Use pforge fm-session list to inspect sessions or pforge fm-session purge to clean up. Sessions auto-rotate at 200 turns.

Observer narrations vs. Studio: The Studio tab is pull-based — you ask, Forge-Master answers. Live narrations from observer mode (when enabled) are push-based: they appear on the main dashboard view, not in this Studio tab. See Dashboard — Observer Narrations Card for the live feed. Enable the observer in Settings → Forge-Master.

Timeline Source

Forge-Master turns are indexed as the fm-turn source in the Timeline tab. Each entry shows the lane, a truncated user message, and turn number. Useful for correlating reasoning decisions with plan execution events.

Deep dive: The Forge-Master chapter covers the full reasoning pipeline, intent classification, tool call orchestration, BM25 recall, quorum dispatch, and session management.