Changelog
This page starts with the state each package was in when this documentation site launched — it isn’t a full development history. Earlier changes live in the project’s git history.
2026-08
Section titled “2026-08”Plugins — 0.2.0
Section titled “Plugins — 0.2.0”@telem/openclaw-plugin, @telem/opencode-plugin, and @telem/pi-telem all
shipped 0.2.0, packaged as registry-ready installs across all three
surfaces (OpenClaw, opencode, pi):
- Each package now builds a
dist-only tarball with an explicitfileslist, rather than requiring a source checkout. - Install paths were verified end-to-end against a local Verdaccio registry rehearsing the real npm registry, one clean install per surface — see the coming-soon note on each integration page for current public npm availability.
@telem/openclaw-pluginregisters thetelem-openclaw-setupbin entry point used by the OpenClaw install flow.
All three packages carry the same V2 search contract work underneath this
release — a search block resolved per call, a strict
normalized_schema_version >= 2 gate with no V1 fallback, and trajectory v5
identity — see the OpenClaw,
opencode, and pi pages for
the surface-specific details.
telem-sdk — 0.1.0
Section titled “telem-sdk — 0.1.0”The Python SDK’s first version, 0.1.0:
- V2 search contract —
search()reads the server’s normalized envelope (results+by_provider, preserving partial per-provider failures) behind anormalized_schema_version >= 2check; see Python SDK. - Query batching —
search()accepts a sequence of queries, which batch into a single interaction and run concurrently server-side; see Multi-query batching. - MCP server — the
[mcp]extra addstelem-mcp, a stateless MCP stdio server exposingtelem_search,telem_providers, andtelem_session_history; see MCP server.
telem-sdk is not yet published to PyPI — see the install note on the
Python SDK page.