See failures, cost, and latency in production
You add traces, usage and cost accounting, cache policy, cancellation, bounded retries, and safe logs. Debug output becomes evidence for tests and operations.
Unit example (nearest native match)
See the idea in context
axllm.SetRateLimiter(globalLimiter)
axllm.SetTracer(tracer)
axllm.SetMeter(meter)
workflow.ForwardWithHooks(ctx, client, input, nil, axllm.AxRuntimeHooks{RateLimiter: callLimiter, Tracer: tracer, Meter: meter})
axllm.SetRateLimiter(nil); axllm.SetTracer(nil); axllm.SetMeter(nil)- Trace the run
tracer connects model and tool activity to the surrounding request.
- Make cancellation possible
abortSignal lets callers stop work that is no longer useful.
- Control repeated work
contextCache makes reuse an explicit operational policy.
Run itIn your own project
go get github.com/ax-llm/ax/packages/go
package main
import (
"context"
"fmt"
"os"
axllm "github.com/ax-llm/ax/packages/go"
)
func main() {
client := axllm.NewAI("openai", map[string]axllm.Value{"apiKey": os.Getenv("OPENAI_API_KEY")})
classify := axllm.NewAx("review:string -> sentiment:class \"positive, negative, neutral\"", nil)
result, err := classify.Forward(context.Background(), client, map[string]axllm.Value{
"review": "Useful and boring in the best way."
}, nil)
if err != nil {
panic(err)
}
fmt.Println("sentiment:", result.(map[string]axllm.Value)["sentiment"])
}Set OPENAI_APIKEY in your environment before running provider-backed code.
From a clone of the ax repo:
npm run example -- go src/examples/go/long-agents/smart_defaults_agent.goActive practice
Answer 2 in a row to learn this · attempt 1