Skip to content

sheawinkler/ContextLattice

v3.11.1 Feature

This release adds 3 notable features for engineering teams evaluating rollout.

✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

agent-framework agent-orchestration ai-infra ai-interface context-engineering context-management
+4 more
go long-horizon-agents long-horizon-intelligence rust

Summary

AI summary

Native agent discovery now also checks the installer-owned agent_hooks.env repository root, preventing stale inherited paths from hiding valid Pi or Droid adapters.

Changes in this release

Feature Medium

Native agent discovery now also checks `agent_hooks.env` repository root.

Native agent discovery now also checks `agent_hooks.env` repository root.

Source: llm_adapter@2026-07-15

Confidence: high

Feature Medium

Shell-style `export CONTEXTLATTICE_REPO_ROOT=...` assignments are parsed by the native CLI.

Shell-style `export CONTEXTLATTICE_REPO_ROOT=...` assignments are parsed by the native CLI.

Source: llm_adapter@2026-07-15

Confidence: high

Feature Medium

Runner capability discovery can use the installed contract registry under ContextLattice global home.

Runner capability discovery can use the installed contract registry under ContextLattice global home.

Source: llm_adapter@2026-07-15

Confidence: high

Bugfix Medium

Regression test ensures stale inherited root falls through to valid installed root without shell override.

Regression test ensures stale inherited root falls through to valid installed root without shell override.

Source: llm_adapter@2026-07-15

Confidence: low

Full changelog

ContextLattice v3.11.1 - Upgrade-Safe Runner Discovery

v3.11.1 hardens in-place upgrades for long-lived agent processes. A stale inherited checkout path can no longer hide valid Pi or Droid adapters when the current ContextLattice install records a newer canonical root.

What changed

  • Native agent discovery now considers the installer-owned agent_hooks.env repository root in addition to an explicit repository and the current checkout.
  • Shell-style export CONTEXTLATTICE_REPO_ROOT=... assignments are parsed by the native CLI.
  • Runner capability discovery can use the installed contract registry under the ContextLattice global home.
  • Added a regression test proving that a stale inherited root falls through to a valid installed root without a shell override.

Boundaries preserved

  • The CLI remains the primary operator and agent interface.
  • Explicit repository selection and the current Git checkout remain authoritative when they contain the requested runner artifacts.
  • ContextLattice does not install Pi, Droid, or any other third-party harness.
  • Runner selection remains advisor-only. No automatic dispatch, merge, push, or mutation behavior was added.

Verify

contextlattice_agent_discover --agents pi,droid --pretty
contextlattice_doctor --agents pi,droid --skip-provider-smoke --pretty

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track sheawinkler/ContextLattice

Get notified when new releases ship.

Sign up free

About sheawinkler/ContextLattice

Private-by-default memory and context layer for agents with Go/Rust runtime, staged retrieval across fused data backends, and long-horizon context continuity.

All releases →

Related context

Earlier breaking changes

  • v3.17.3 Agent guidance now mandates the `/agents/tasks` route family.
  • v3.17.3 Task worker now checks approval before any execution steps.

Beta — feedback welcome: [email protected]