Tracing

The SDK records one GroundForge Trace for each direct invocation or Channel request. Calls to invoke, ainvoke, stream, and astream are instrumented. Model and tool activity appears as steps inside the same Trace instead of separate top-level requests. A Channel request commonly appears as:

Channel input
├─ Agent or model step
├─ Gateway decision
├─ Tool or MCP call
└─ Channel output

The basic Agent invocation does not need custom metadata:

result = agent.invoke(
    {"messages": [{"role": "user", "content": "What is the weather in Ottawa?"}]}
)

If your application already uses a stable LangChain thread_id, you may keep using it to group related requests. It is not required for the basic GroundForge connection. Known secret fields and authorization values are redacted before Trace data is sent. Still avoid credentials in prompts or tool arguments. See Traces and Request Tracing.

Example

Complete LangChain Agent Example, send one request, and confirm one root Trace contains the Channel, model, tool, Gateway decision, and response steps.

Overview

Concepts

Examples

Platform

SDK

CLI

REST APIs

Operations

Reference

Example

​Example

Example