Skip to content

Meet Proxy 0.4.14 — unified searchable context

Choose a tag to compare

@diask5 diask5 released this 22 Oct 03:21

Meet Proxy 0.4.14 gives native and cloud agents one searchable context archive per verified account. Complete source files, an index and provenance are available in the cloud agent's read-only context folder. Search supports ranked keywords, phrases, prefixes, literal code strings and project/source/date filters.

Collection resumes after interruptions, merges known replicas, includes supported child chats, and preserves edits, exclusions and deletions. Incomplete captures remain staged until the complete capture can replace the previous readable version atomically. Source coverage, search and surrounding reads are available in the Library UI.

The hosted backend includes migrations 0040 and 0041. Existing account links, native chat routing, model-account state and sync choices are preserved. The bundled companion is runtime 48; it replaces earlier candidate collectors when the supported setup helper or plugin manager performs the upgrade.

Validation: 312 application tests, 49 UI checks, 12 deployment checks, 25 focused upgrade/receiver checks and package integrity. A separate real-agent diagnostic benchmark passed 13 cases and 29 factual checks on a synthetic corpus. All 36 isolated integration checks passed against the deployed runtime; public UI assets and existing account settings were verified. See the repository's verification and benchmark documents for scope and production evidence.

Update the existing commonplace alias or install meet-proxy; enable only one alias. Codex users should extract the verified archive to a permanent directory and run its bundled server/configure-codex.mjs helper from the intended existing chat. Refresh that chat's MCP connection if the host requires it. Already-linked accounts do not need another Google sign-in. Transcript sync still follows the owner's saved choice.

Limitations: unsupported applications and attachments require explicit connectors; ChatGPT web history requires export import. Answer citations currently appear as IDs. Conductor's host-specific sleeping-chat and Mac-binding limitations remain independent of relay availability.