@ultrathink-solutions/openclaw-logfire 0.1.0 → 0.1.1

package/CHANGELOG.md

@@ -5,6 +5,21 @@ All notable changes to `@ultrathink-solutions/openclaw-logfire` will be document
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.1.1] - 2026-02-16
+
+### Fixed
+
+- Removed JSON Schema `$schema` declaration (draft 2020-12) from `openclaw.plugin.json` — OpenClaw's bundled Ajv only supports draft-07 and crashes on any CLI command when an incompatible `$schema` is present
+- Changed plugin manifest `id` from `"logfire"` to `"openclaw-logfire"` — OpenClaw resolves plugin config by manifest `id`, and the mismatch caused config entries to silently not pass through to the plugin
+
+### Changed
+
+- **Breaking:** Config entry key must now be `"openclaw-logfire"` (was `"logfire"`) to match the corrected manifest `id`
+
+### Added
+
+- `SKILL.md` for ClawHub registry listing
+
 ## [0.1.0] - 2026-02-15
 
 ### Added
@@ -25,4 +40,5 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Batch and simple span processor modes
 - Zero-config quickstart (just set `LOGFIRE_TOKEN`)
 
+[0.1.1]: https://github.com/Ultrathink-Solutions/openclaw-logfire/compare/v0.1.0...v0.1.1
 [0.1.0]: https://github.com/Ultrathink-Solutions/openclaw-logfire/releases/tag/v0.1.0

package/README.md

@@ -1,13 +1,18 @@
-# @ultrathink/openclaw-logfire
+# @ultrathink-solutions/openclaw-logfire
+
+[![npm version](https://img.shields.io/npm/v/@ultrathink-solutions/openclaw-logfire)](https://www.npmjs.com/package/@ultrathink-solutions/openclaw-logfire)
+[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
 
 Pydantic [Logfire](https://pydantic.dev/logfire) observability plugin for [OpenClaw](https://openclaw.ai).
 
 Full agent lifecycle tracing aligned with [OTEL GenAI semantic conventions](https://opentelemetry.io/docs/specs/semconv/gen-ai/) — tool calls, token metrics, error stack traces, and optional distributed tracing across services.
 
+> **Real-world context:** We built this plugin as part of deploying OpenClaw into production on the [Ultrathink Axon platform](https://ultrathinksolutions.com/the-signal/openclaw-to-production/). The architecture and design decisions are detailed in that post.
+
 ## Quickstart
 
 ```bash
-npm install @ultrathink/openclaw-logfire
+npm install @ultrathink-solutions/openclaw-logfire
 ```
 
 Set your Logfire write token:
@@ -22,7 +27,7 @@ Add to `openclaw.json`:
 {
   "plugins": {
     "entries": {
-      "logfire": {
+      "openclaw-logfire": {
         "enabled": true,
         "config": {}
       }
@@ -88,7 +93,7 @@ All settings are optional. Sensible defaults work out of the box.
 {
   "plugins": {
     "entries": {
-      "logfire": {
+      "openclaw-logfire": {
         "enabled": true,
         "config": {
           // Logfire project (enables clickable trace links in logs)
@@ -229,9 +234,16 @@ ln -s $(pwd) ~/.openclaw/extensions/openclaw-logfire
 
 export LOGFIRE_TOKEN="your-write-token"
 openclaw restart
-openclaw plugins list  # Should show "logfire" as enabled
+openclaw plugins list  # Should show "openclaw-logfire" as enabled
 ```
 
+## Built By
+
+[Ultrathink Solutions](https://ultrathinksolutions.com) — production-grade AI agent infrastructure. We help teams close the gap between AI demos and production systems.
+
+- [We Put OpenClaw Into Production in a Weekend](https://ultrathinksolutions.com/the-signal/openclaw-to-production/) — the architecture behind this plugin
+- [The AI Execution Gap](https://ultrathinksolutions.com/the-signal/ai-execution-gap/) — why most AI projects stall between POC and production
+
 ## License
 
 MIT

package/SKILL.md

@@ -0,0 +1,98 @@
+---
+name: openclaw-logfire
+description: Pydantic Logfire observability — OTEL GenAI traces, tool call spans, token metrics, distributed tracing
+version: 0.1.1
+homepage: https://github.com/Ultrathink-Solutions/openclaw-logfire
+metadata:
+  openclaw:
+    primaryEnv: LOGFIRE_TOKEN
+    requires:
+      env:
+        - LOGFIRE_TOKEN
+---
+
+# OpenClaw Logfire Plugin
+
+Pydantic [Logfire](https://pydantic.dev/logfire) observability plugin for OpenClaw. Traces the full agent lifecycle with [OTEL GenAI semantic conventions](https://opentelemetry.io/docs/specs/semconv/gen-ai/) — tool calls, token usage, errors, and optional distributed tracing across services.
+
+## Install
+
+```bash
+openclaw plugins install @ultrathink-solutions/openclaw-logfire
+```
+
+Set your Logfire write token:
+
+```bash
+export LOGFIRE_TOKEN="your-token"
+```
+
+Add to `openclaw.json`:
+
+```json
+{
+  "plugins": {
+    "entries": {
+      "openclaw-logfire": {
+        "enabled": true,
+        "config": {}
+      }
+    }
+  }
+}
+```
+
+Restart OpenClaw. Traces appear in your Logfire dashboard.
+
+## What It Traces
+
+Every agent invocation produces a span tree:
+
+```
+invoke_agent chief-of-staff          (root span)
+  |-- execute_tool Read              (file read)
+  |-- execute_tool exec              (shell command)
+  |-- execute_tool Write             (file write)
+```
+
+Spans follow OTEL GenAI semantic conventions: `gen_ai.agent.name`, `gen_ai.tool.name`, `gen_ai.usage.input_tokens`, `gen_ai.usage.output_tokens`, etc.
+
+## Metrics
+
+- `gen_ai.client.token.usage` — token count histogram (input/output)
+- `gen_ai.client.operation.duration` — agent invocation latency
+
+## Key Configuration
+
+| Setting | Default | Description |
+|---------|---------|-------------|
+| `environment` | `development` | Deployment environment label |
+| `serviceName` | `openclaw-agent` | OTEL service name |
+| `providerName` | — | GenAI provider (e.g. `anthropic`) |
+| `captureToolInput` | `true` | Record tool arguments |
+| `redactSecrets` | `true` | Strip API keys and JWTs |
+| `distributedTracing.enabled` | `false` | W3C traceparent propagation |
+
+## Security & Privacy
+
+- **Secret redaction** (on by default): Strips API keys, platform tokens, JWTs, and credentials from recorded tool arguments before export
+- **Tool output** is not captured by default (`captureToolOutput: false`)
+- **Message content** is not captured by default (`captureMessageContent: false`)
+- **Data destination**: Traces are exported via OTLP HTTP to Pydantic Logfire (US or EU region). No other external endpoints are contacted.
+- **No local persistence**: All data is streamed to Logfire; nothing is written to disk
+
+## External Endpoints
+
+| URL | Data Sent |
+|-----|-----------|
+| `https://logfire-api.pydantic.dev` (US) | OTLP traces + metrics |
+| `https://logfire-api-eu.pydantic.dev` (EU) | OTLP traces + metrics |
+
+By using this plugin, trace and metric data is sent to Pydantic Logfire. Only install if you trust this destination.
+
+## Links
+
+- [GitHub](https://github.com/Ultrathink-Solutions/openclaw-logfire)
+- [npm](https://www.npmjs.com/package/@ultrathink-solutions/openclaw-logfire)
+- [Logfire](https://pydantic.dev/logfire)
+- [Blog: We Put OpenClaw Into Production](https://ultrathinksolutions.com/the-signal/openclaw-to-production/)

package/openclaw.plugin.json

@@ -1,8 +1,7 @@
 {
-  "id": "logfire",
+  "id": "openclaw-logfire",
   "kind": "observability",
   "configSchema": {
-    "$schema": "https://json-schema.org/draft/2020-12/schema",
     "type": "object",
     "additionalProperties": false,
     "properties": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ultrathink-solutions/openclaw-logfire",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Pydantic Logfire observability plugin for OpenClaw — OTEL GenAI semantic conventions, distributed tracing, token metrics, trace links",
   "license": "MIT",
   "author": "Ultrathink Solutions <engineering@ultrathink.dev>",
@@ -32,6 +32,7 @@
   "files": [
     "dist/",
     "openclaw.plugin.json",
+    "SKILL.md",
     "README.md",
     "LICENSE",
     "CHANGELOG.md"