# latitude-llm

> Latitude is the open-source agent engineering platform

- **URL**: https://www.freshcrate.ai/projects/latitude-llm
- **Author**: latitude-dev
- **Category**: AI Agents
- **Latest version**: `pi-telemetry-0.0.2` (2026-05-21)
- **License**: LGPL-3.0
- **Source**: https://github.com/latitude-dev/latitude-llm
- **Homepage**: https://latitude.so
- **Language**: TypeScript
- **GitHub**: 3,957 stars, 311 forks
- **Registry**: github
- **Tags**: `typescript`

## Description

Latitude is the open-source agent engineering platform

## Recent releases

| Version | Date | Urgency | Changes |
| --- | --- | --- | --- |
| `pi-telemetry-0.0.2` | 2026-05-21 | High | ### Fixed  - Telemetry export no longer blocks Pi's agent lifecycle at the end of a run. Trace uploads are dispatched asynchronously after span construction so the TUI can leave the working/loading state immediately. - Failed telemetry uploads are now silent unless debug logging is enabled, avoiding direct stderr writes that can disturb Pi's interactive terminal layout. |
| `openclaw-telemetry-cli-0.0.7` | 2026-04-29 | High | Initial release of the standalone installer CLI. The runtime split that landed in `@latitude-data/openclaw-telemetry` 0.0.6 ([PR #2920](https://github.com/latitude-dev/latitude-llm/pull/2920)) deleted the bundled CLI from the runtime package so that runtime would pass OpenClaw 2026.4.25+'s install-time `dangerous-exec` security scan. The 0.0.6 manual install flow asked operators to run six `openclaw config set` commands plus a hand-edited `plugins.allow` array; this package brings the one-shot |
| `openclaw-telemetry-0.0.1` | 2026-04-24 | High | ### Added  - Initial release. OpenClaw plugin that streams every agent run to Latitude as OTLP traces by subscribing to OpenClaw's typed `llm_input` / `llm_output` / `before_tool_call` / `after_tool_call` / `agent_end` hooks. - Per-run state accumulator keyed by `runId` that pairs LLM input/output into single calls, nests tool invocations under their parent LLM call, and handles out-of-order tool events defensively. - OTLP span tree with three span kinds — `interaction` (per agent run), `llm_re |
| `claude-code-telemetry-0.0.6` | 2026-04-21 | High | ### Fixed  - **Fixed URL domain** from `app.latitude.so` to `console.latitude.so`. |
| `claude-code-telemetry-0.0.5` | 2026-04-20 | High | ### Changed  - **Install UX rewritten with [`@clack/prompts`](https://www.npmjs.com/package/@clack/prompts)** — the interactive wizard now opens with a proper welcome banner, renders each prompt inside a gutter with a description line explaining the field + the relevant Latitude URL to fetch it from, masks the API key input with `•` as you type, and ends with a "Next step" panel plus a direct link to your project's trace view. Spinners stream in as each install step completes. - **README restru |
| `claude-code-telemetry-0.0.4` | 2026-04-20 | High | ### Added  - **Interactive `install` wizard** — `npx -y @latitude-data/claude-code-telemetry install` now prompts for `LATITUDE_API_KEY` and `LATITUDE_PROJECT`, merges them into `~/.claude/settings.json` under `env`, and installs the Stop-hook entry if missing. On macOS it also offers to set `BUN_OPTIONS` via `launchctl` and persist it with a `~/Library/LaunchAgents/so.latitude.claude-code-telemetry.plist`. Existing values are shown as defaults (API keys masked); a backup of `settings.json` is |
| `claude-code-telemetry-0.0.2` | 2026-04-20 | High | ### Added  - **Workspace and git context on every span** — the hook now reads the Claude Code session's `cwd` and derives `workspace.name` / `workspace.path`, `git.branch` / `git.commit` / `git.repo`, `claude_code.version`, `host.user`, and `hook.event`. The workspace name is attached as a span tag (`latitude.tags`); the full set is attached as shared trace metadata (`latitude.metadata`) on every emitted span so traces can be sliced by repo, branch, or CLI version in the Latitude UI. - **Full c |
| `typescript-telemetry-3.0.0-alpha.5` | 2026-04-17 | High | ### Fixed  - `capture()` now starts a new Latitude root trace when called under an active non-Latitude span, so wrapper spans such as workflow-level capture names are preserved instead of being absorbed into foreign traces. - Nested Latitude `capture()` calls still reuse the existing Latitude-owned trace and merge context as before. |
| `claude-code-telemetry-0.0.1` | 2026-04-17 | High | Package updates and improvements |
| `typescript-telemetry-3.0.0-alpha.4` | 2026-04-14 | Medium | ### Fixed  - **Provider SDK version coupling** — moved provider SDK packages (`openai`, `@anthropic-ai/sdk`, etc.) from `optionalDependencies` to `devDependencies` so they are no longer installed alongside `@latitude-data/telemetry`. Users can now use any compatible version of their provider SDK without conflicts. - **Bumped all Traceloop instrumentations to `^0.25.0`** — notably extends OpenAI support from `>=4 <6` to `>=4 <7`, fixing auto-instrumentation for users on `openai@6.x`. |

## Citation

- HTML: https://www.freshcrate.ai/projects/latitude-llm
- Markdown: https://www.freshcrate.ai/projects/latitude-llm.md
- Dependencies JSON: https://www.freshcrate.ai/api/projects/latitude-llm/deps

_Generated by freshcrate.ai. Indexes github releases for AI-agent ecosystem packages._