Lightspeed v0.2.0 includes all changes merged since v0.1.0: outbound environment registration, daemon distribution and upgrades, broader MCP support, session metadata and retention, shared content references, a faster management UI, and the product manual.
Environments and daemon distribution
- Machines behind NAT, Kubernetes pods, and other remote compute can register through outbound daemon connections using universe-scoped registration keys and persistent Ed25519 identities. Keys control identity mode, expiry, environment limits, and disconnect grace. The CLI and Platform support creating, listing, and revoking keys and inspecting registered environments.
- The
environment-gatewayruntime role owns daemon registration, worker routes, and environment reconciliation. Registered environments expose their groups, reconnect state, and last-seen information; ephemeral environments close after their configured disconnect grace. - The Linux amd64 daemon is now a static musl binary. Releases include
envd.jsondiscovery metadata and verified build identity.lightspeed-envd upgradeverifies and installs the deployment-selected build; optional automatic upgrades respond to protocol mismatches while retaining daemon identity. - Daemon fixes preserve one contiguous omitted-output gap on uneven pipe reads and close an upgrade candidate before executing it.
MCP and model tools
- MCP discovery supports larger enterprise inventories and oversized optional descriptions while retaining validation of tool names and schemas. Management views expose the retained inventory; tool search supports argument-name matching, names-only results, and bounded result pages. Tool validation errors include the relevant schema.
- Native MCP calls work in mixed batches with managed workflow tools and
await, including approval-gated calls alongside ungated siblings. - Builtin tools resolve model-facing names, schemas, and argument adapters for each provider request from compact internal identities. Provider-native calls remain available for transcript replay.
- Anthropic hosted web search and fetch include configuration controls, provider lowering, replay, and citation projection. Model-list caching reduces repeated provider discovery.
Sessions, content, and retention
- Sessions support metadata, containment filters, profile defaults, and close-based retention. Session and bot settings share profile and trigger controls, including lightweight existing-environment and no-environment overrides.
- Context entries, run outputs, and public projections share
ContentRefdescriptors and explicit provenance. Messages and visible reasoning expose complete text; detailed run views expose durable output descriptors. Audio transcripts retain source-audio provenance. - Content-addressed storage collection protects committed references against concurrent attachment and reupload, follows nested content edges, and uses distinct physical object keys. A deployment-wide collector runs bounded, resumable passes; operators also have the
cas-sweepCLI.
Platform and transcript improvements
- Faster session loading, incremental history loading, reduced transcript flicker, clearer tool traces, run statistics, and connection-timeout and origin-validation fixes.
- Unsent composer drafts persist locally per universe and session, including bot conversations. Sending, queueing, or steering resumes following the transcript bottom.
- Provider-native compaction appears as a muted transcript marker. Compaction thresholds now persist correctly in profile, session, and bot editors; camelCase fields retain snake_case input aliases.
- Session lists add lifecycle and metadata filters, per-universe preferences, configurable metadata columns, compact rows, and consistent lineage and identity controls. Profiles can be copied, and MCP creation and editing have clearer progress and tool-selection controls.
- Updated demo fixtures and regression coverage accompany these changes, including integration-link URL encoding.
Documentation and release artifacts
- A product manual covers getting started, everyday use, environments, deployment, integrations, architecture, and development. Existing references and repository links were consolidated around the manual.
- The Astro Starlight documentation site includes search, responsive navigation, light/dark themes, diagrams, screenshots, generated API and workflow references, per-page Markdown exports, and
llms.txt. The hosted manual is available at Lightspeed documentation. - Snapshots and tagged releases package the static documentation archive alongside the demo and executable archives. The release manifest, checksums, OCI bundles, and build provenance include the documentation artifact.
- Documentation CI validates adapters, links, anchors, assets, search, and the static build. The tagged-release workflow tests and builds the exact tagged source before publishing component images, Linux archives, the TypeScript client, checksums, and an SBOM.