Skip to content

Partner v0.2.0

Choose a tag to compare

@github-actions github-actions released this 10 Nov 15:37
· 20 commits to master since this release

English | 简体中文 | 繁體中文

Partner v0.2.0

A feature release for connecting external agents and plugins. Until now, what Partner knew about you stayed inside its own conversation. Game AI mods, editor and browser plugins and other agent programs each talked to a model of their own and started from nothing. v0.2.0 adds Memory Services: you give such a program a local endpoint, and your Partner comes along. Anything that lets you enter an OpenAI- or Anthropic-compatible address, a key and a model name can use one. That covers an NPC dialogue mod, a writing plugin or a separate agent framework. Each request it sends gets the relevant memories added, and what it asked and got back is summarized into the main memory, so the main conversation can recall it later.

The memory store gains an origin column (schema v3, migrated automatically on first start). The session and settings formats are otherwise unchanged.

New

Memory Services

Add, edit and remove endpoints on the new Memory Services page in the sidebar. Each service listens on its own 127.0.0.1 port and forwards to a real model: the main model by default, or an upstream of its own. It changes only three things in a request:

  • the model name the caller uses is replaced with the upstream's;
  • recalled memories go in front of the caller's last user message, within a token budget that the context length and the request's own size bound;
  • an optional custom prompt goes before the caller's system prompt (empty by default).

Everything else passes through unchanged: tools, tool_choice, stream, response_format, and the upstream's tool_calls, SSE frames, usage and errors. The caller keeps its own tools and its own history; Partner's MCP servers and desktop control are not exposed through a service.

Summaries back into the main memory

After a configurable idle interval, or at the latest after a maximum wait under steady traffic, a service summarizes what callers asked and what it answered into one sentence. The sentence starts with [对外服务:<name>] and goes into the main memory. Stopping, deleting or "Summarize now" flushes too, and on shutdown every service flushes before exit. Summaries can be turned off per service; recall keeps working.

Memory origins

The Memory page labels service-written memories with their service and can filter by it. A service memory never retires a main-session memory, and deleting a conversation does not delete it. Deleting the service offers to remove the memories it wrote.

Separate credentials

Every service has its own generated token (at least 32 characters, shown once, rotatable), accepted as Authorization: Bearer or x-api-key. The caller's credential is never forwarded; the upstream key stays in the settings.

Limits

  • Same machine only. A service listens on 127.0.0.1, so the mod or plugin has to run on the computer Partner runs on.
  • Pass-through, not conversion. A service's protocol must match its upstream's. A mismatch is refused when saving, and a configuration that drifts later answers 502 without contacting the upstream.
  • External text reaches the main memory. Summaries are recalled by the main conversation like any other memory, so an untrusted caller could steer it through them. Give the token only to programs you trust, or turn summaries off.

Upgrading

  • Install v0.2.0 directly, or let v0.1.4 update itself.
  • The memory database migrates to schema v3 on first start; existing memories become main-session memories.
  • No service exists until you add one, so nothing listens on a new port after the upgrade.

The voice engines are downloaded from the engines-v1 release on first use; their URLs and SHA-256 are pinned in this build. The app code is MIT licensed; the engine runtimes and model weights keep their own licences, see THIRD-PARTY-NOTICES.md in the release assets.