Skip to content

v1.10.0 — DeepSeek Harness support

Latest
Latest

Choose a tag to compare

View all tags
@dell-zhang dell-zhang released this 15 Aug 05:51
v1.10.0
81b4bf4

TeleMem now connects directly to the official DeepSeek Harness through its Cordis MCP client. The opt-in patch launches the pinned TeleMem release with uvx and exposes all eight memory operations as mcp__telemem__* tools.

Added

  • DeepSeek Harness patch at examples/deepseek-harness.cordis.yml, tested against the public 0.1.0-rc.5 MCP configuration contract.
  • Explicit forwarding for provider keys and TeleMem settings that DSH intentionally scrubs from MCP child processes.
  • A two-minute tool-call timeout for LLM-backed memory writes, strict startup failure behavior, and offline contract tests for the integration.

Changed

  • YAML and JSON configs securely expand ${NAME} environment references after parsing and report missing variables by name.
  • config.deepseek.yaml now reads DEEPSEEK_API_KEY for extraction and OPENAI_API_KEY for embeddings without storing secrets in the file.

Quick start

export DEEPSEEK_API_KEY="your-deepseek-api-key"
export OPENAI_API_KEY="your-openai-api-key"
export TELEMEM_CONFIG="$PWD/config/config.deepseek.yaml"
npx @deepseek-ai/dsh web --patch "$PWD/examples/deepseek-harness.cordis.yml"

Full changelog: https://github.com/TeleAI-UAGI/telemem/blob/main/CHANGELOG.md

Assets 2
Loading