Repository navigation
PocketContext 0.24.0
Fixes remote MCP connection problems found after 0.23.1 and adds an opt-in hosted
container mode. Local projects, password login, native HTTPS and tunnels keep
their existing behavior.
Remote MCP fixes
- OAuth clients that omit the
resourceparameter, such as Gemini, could not
authorize or exchange codes. PocketContext now defaults an omitted resource to
the instance's own/mcpendpoint. An explicitly empty, different or repeated
resource is still rejected; audience binding, exact callbacks, S256 PKCE and
explicit consent are unchanged. - Native desktop MCP clients can register HTTP callbacks on literal
127.0.0.1
or[::1]with their listener port.localhost, LAN addresses and custom URI
schemes remain refused; public callbacks still require HTTPS. - Every tool now declares
destructiveHintexplicitly. Read-only tools are no
longer classified as destructive by clients that treat an omitted hint
conservatively; all state-changing tools remain marked destructive. - Authorization errors name the specific failed requirement.
- Structured, metadata-only diagnostics for OAuth, HTTP and MCP completions go to
stderr with a server-generatedX-Request-ID. They exclude arguments, results,
SQL, search text, content, credentials and OAuth parameter values. See
MCP setup.
Hosted containers
An opt-in container image packages one knowledge base per domain for
PocketDeploy/ONCE: email one-time-code login through runtime SMTP, public reader
and MCP behind the proxy, and complete private S3 backups daily and before
upgrades with verified isolated restores. Only explicitly enrolled instances
follow validated releases automatically. See hosted containers.
Upgrading
Use the normal stop, complete backup, binary replacement and restart procedure.
Preserve existing service arguments, OAuth grants, certificate cache and private
tunnel identity. Database format remains 1; projects from 0.11.x through 0.23.1
require no data conversion.
The embedded manual and generated client prompt are pinned to 0.24.0. Previously
released website prompts remain unchanged.
PocketContext 0.24.0: a local knowledge base: server, reader and CLI in one binary.
Linux amd64 and arm64: static musl binaries. macOS arm64: macOS 15 or later, ad hoc signed. Windows amd64: statically linked MinGW build, unsigned.
Install on Linux or macOS into the project folder: curl -fsSL https://github.com/pocketcontext-labs/pocketcontext/releases/download/v0.24.0/install.sh | sh -s -- /absolute/project/folder
Install on Windows (PowerShell): $env:POCKETCONTEXT_INSTALL_DIR = 'C:\absolute\project\folder'; irm https://github.com/pocketcontext-labs/pocketcontext/releases/download/v0.24.0/install.ps1 | iex
Both installers require the target folder, usually the project folder beside pocketcontext.db (it may be inside iCloud Drive, OneDrive, Dropbox or Google Drive).
See the README.