Skip to content

Guided tour

FabrCore 2.0 · Release and package availability

These guides track the current 2.0 source. Stable 2.0.0 publication is pending; package commands show the release target. Until it is published, follow the source quick start or use a matching available prerelease set. Release migration · Runtime modes

MODULE 13 · LESSON 13.5

Ask diagnostic questions safely

Ask about an agent through isolated administrative sessions.

Lesson 78 of 86 · FabrCore 2.0

Overview

Diagnostic sessions operate on a source snapshot with their own history and actor attribution. They must not borrow production tools, connections, Memory writes, background delegation or reply delivery. An operator can inspect behavior without resuming the target's business harness.

The diagnostic session has its own history

Creating an admin-session captures source context for an operator's investigation and gives the session its own identity/history. It can explain recorded configuration or behavior without adding the diagnostic turn to the agent's business conversation. Later data may need explicit reading; an initial snapshot is not a permanently live copy of everything.

Read-only tools enforce the boundary

The privileged diagnostic path excludes production tool execution, connections and business state mutation. Ordinary user messages with _admin are rejected; that channel label does not grant access. A deliberate management test-message action, by contrast, does invoke normal business behavior. Label these actions distinctly in the console.

Ask an isolated diagnostic question

  1. Use the privileged diagnostic API or Environment Diagnostics screen to start a session for the selected target.
  2. Ask about its captured configuration/history and inspect the diagnostic transcript/usage separately from the target conversation.
  3. Verify that the target history/state and external services are unchanged. Use explicit management test messages only when you intend to exercise business behavior.
Create an isolated session, submit a turn, then read the receipt 
POST /fabrcoreapi/admin/v1/principals/dev/agents/researcher/admin-sessions
Authorization: Bearer <administration-credential>
Content-Type: application/json

{ "sourceThreadId": "main" }

POST /fabrcoreapi/admin/v1/principals/dev/agents/researcher/admin-sessions/<session-id>/turns
Authorization: Bearer <administration-credential>
Content-Type: application/json

{ "turnId": "inspect-001", "message": "Which model and tools are configured for this agent?" }

GET /fabrcoreapi/admin/v1/principals/dev/agents/researcher/admin-sessions/<session-id>/turns/inspect-001
Authorization: Bearer <administration-credential>

Compare source and diagnostic transcripts

  1. Read the target's current history/state, then create an admin-session through the endpoint below and ask a question about its captured configuration.
  2. Poll the diagnostic turn receipt and inspect its administration-only transcript. Confirm the original business history and fixture system did not receive that question or a tool mutation.
  3. Ask a question requiring missing capture. The explanation should identify the unavailable evidence instead of inventing a hidden execution trace.

The result demonstrates isolated inspection. An operator receives an explanation of available evidence, not a replay of the target's business harness.

If the result is different

Sending an ordinary message with Channel=_admin is not the diagnostic API. Do not route privileged sessions through SurfaceChatLink's normal user chat path.

Go deeper

Explore the related documentation.