PocketContext 0.24.0

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 resource parameter, such as Gemini, could not
  authorize or exchange codes. PocketContext now defaults an omitted resource to
  the instance's own /mcp endpoint. 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 destructiveHint explicitly. 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-generated X-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.

PocketContext 0.23.1

PocketContext 0.23.1

Fixes a crash in the remote MCP adapter introduced in 0.23.0. Bodyless knowledge
requests, including the schema tool, could panic during request cleanup and
terminate the entire server. The adapter now supplies an empty request body before
calling the embedded API router directly.

A regression test exercises the direct PocketBase router path. The previous
HTTP-proxied integration fixture normalized empty bodies and missed this failure.

Upgrade MCP-enabled servers to this patch using the normal stop, complete backup,
binary replacement and restart procedure. Preserve the existing service arguments,
OAuth grants, certificate cache and private tunnel identity. Database format remains
1; supported projects from 0.11.x through 0.23.0 require no data conversion.

The embedded manual and generated client prompt are pinned to 0.23.1. Previously
released website prompts remain unchanged.

---

PocketContext 0.23.1: 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.23.1/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.23.1/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.

PocketContext 0.23.0

PocketContext 0.23.0

PocketContext adds an opt-in remote MCP endpoint for external assistants on its
native HTTPS domain. Configure one service with
serve --headless --domain HOST --mcp, then connect the assistant to
https://HOST/mcp. See MCP setup.

• Built-in OAuth discovery, automatic client registration, S256 PKCE, explicit
  browser consent, access/refresh tokens and revocation.
• Existing reader sign-in links bootstrap consent without revealing or resetting
  the randomly generated setup password.
• Knowledge and space tools reuse authenticated API rules, including immutable
  evidence, citation checks, revision conflicts and atomic publication.
• File content is bounded and supplied explicitly; non-text conversion remains
  agent-owned. No arbitrary host paths, shell, network fetching or administration
  tools are exposed.
• OAuth state remains machine-local. Knowledge database format remains 1;
  projects from 0.11.x through 0.22.x need no knowledge-data conversion.
• The embedded manual and generated client setup prompt are pinned to 0.23.0.
  Previously released website prompts remain unchanged.

Gemini account linking and actual mobile behavior require user confirmation.
Automated checks are not evidence of voice support or phone attachment transfer.

---

PocketContext 0.23.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.23.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.23.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.

PocketContext 0.22.0

PocketContext 0.22.0

PocketContext removes built-in reader chat and the ACP host integration. The
reader focuses on browsing and searching cited knowledge; external agents keep
using the authenticated CLI/API and installed PocketContext skills for questions,
ingestion and synthesis.

• Removed the chat UI, conversation controls, model and permission selection,
  image prompts and dictation, ACP processes and browser chat endpoints.
• Removed serve --chat-agent and --chat-args. These are now unknown options.
• HTTPS phone access, private tunnels, sources, pages and publication history remain.
• Existing machine-local chat files are left untouched, but are no longer
  accessible through the reader. No transcript export, conversion, compatibility
  layer or automatic knowledge ingestion is provided.
• Knowledge database format remains 1; no knowledge-data conversion is needed.

Current setup prompts, the embedded manual and client invitations are pinned to
0.22.0. Previous release notes describe their historical features.

---

PocketContext 0.22.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.22.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.22.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.

PocketContext 0.21.1

PocketContext 0.21.1

Reader chat now has a compact, keyboard-accessible reasoning-effort slider followed by a model menu. Only combinations advertised by the adapter are offered. The selected pair stays visible, and Reset restores the model and effort selected by the adapter when the conversation was created. Existing conversations without a recorded original default keep Reset disabled rather than guessing.

All three native chat permission choices—Read-only, Workspace access and Full access (YOLO)—are available without host environment flags. The initial default remains read-only; read-only/workspace choices are remembered for new chats in the same browser. Full access applies only when explicitly selected for the current conversation and never becomes the new-chat default. During a running turn, increasing to Full access is supported; stop the turn before reducing access.

The reader also includes the workspace-navigation and import-approval-summary improvements made after 0.20.0. Long space names wrap within the space list on desktop and mobile. Local development has a pinned Nix/devenv toolchain and a documented hot-reload workflow. See development and chat setup.

The supported reader adapter remains the pinned Codex ACP adapter. Antigravity ACP was assessed but is not yet a supported backend. Fast mode is advertised by the Codex adapter for eligible models, but PocketContext does not yet bridge its session configuration controls.

Headless startup now rechecks the private socket if it appears during a TCP fallback check, avoiding an intermittent false port-conflict error when another program uses the configured reader port. The 0.21.0 tag did not produce a published release; 0.21.1 includes the corrected startup behavior.

There is no database-format change. Projects from 0.11.x through 0.20.0 remain compatible; follow the normal upgrade procedure, including a clean stop and complete backup before replacing the executable. Chat transcripts stay in the host's private cache.

---

PocketContext 0.21.1: 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.21.1/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.21.1/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.

PocketContext 0.20.0

PocketContext 0.20.0

Reader chat now has space-aware history, pinning and archiving, automatic session restoration, image attachments, model selection and browser dictation. The composer shield applies host-allowed permissions to the current chat. Full access requires an explicit host opt-in and explicit selection. See agent chat setup for configuration and limits.

---

PocketContext 0.20.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.20.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.20.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.

PocketContext 0.19.0

0.19.0 — Agent chat in the reader

Optional built-in chat connects the PocketContext reader to a host-side Codex ACP
adapter. A phone can ask questions and review agent permission requests through the
same signed-in reader. PocketContext still ships its server, reader, CLI, HTTPS and
ACP bridge in one binary; chat additionally needs a separately installed adapter,
Node.js and provider sign-in on the host. No agent runtime is installed on the phone.

• Enable chat explicitly with serve --chat-agent ABS_EXECUTABLE and optional
  --chat-args JSON_ARRAY. It composes with --headless, --domain and --tunnel.
  Browser requests cannot select an executable.
• The first supported adapter is @agentclientprotocol/codex-acp@2.5.0 with
  @openai/codex@0.165.0. Sessions use read-only mode and on-request approvals.
  Permission controls preserve the adapter's actual choices.
• Host sessions survive browser disconnection. Private local transcripts survive
  server restarts; agent restoration depends on ACP session/load support and
  successful restoration. Interrupted work is explicit and prompts are not replayed.
• Knowledge operations use the authenticated CLI/API under generated instructions;
  a scratch directory and instructions do not constitute a security sandbox.
• Chat is disabled unless configured. Existing local reader, native HTTPS,
  private tunnel and external-agent workflows remain available.

Read chat setup and limitations. Provider authentication is configured
on the host, separately from reader sign-in. External AI services receive the
context the agent sends and their costs and limits apply.

There is no knowledge schema migration. Projects from 0.11.x–0.18.0 keep database
format 1; 0.10.0 and earlier remain unsupported. Follow the upgrade procedure:
verify the release, cleanly stop the project, back up the complete project and
matching old binary, explicitly replace it, then refresh profiles/skills and clients.
Chat transcripts and provider credentials are private machine state, outside the
synced project backup.

---

PocketContext 0.19.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.19.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.19.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.

PocketContext 0.18.0

PocketContext 0.18.0

Open the reader on a phone through a domain with HTTPS managed by the same
PocketContext binary. No separate web server or certificate tool is required.

On an initialized, stopped project:

./pocketcontext serve --headless --domain knowledge.example.com

• HTTPS hosting is opt-in. Default local and private-tunnel workflows remain
  available. Add --tunnel when both forms of access are wanted.
• PocketContext obtains and renews a Let's Encrypt certificate for the configured
  domain. Public TCP ports 80 and 443, suitable DNS, and an always-on reachable
  host are required. HTTP serves certificate challenges and HTTPS redirects.
• Public access exposes the authenticated reader and its supported APIs; local
  administration and the embedded administrator dashboard remain private.
• Run open --public locally to create a short-lived phone sign-in link without
  opening a browser on the server.
• Certificate state stays in the private machine cache, outside the synced
  project. Existing database snapshot, publication, and conflict guards remain.
• One operating-system service supervises the foreground process. Setup agents
  configure service startup and verify the public URL before declaring success.

See HTTPS hosting, permanent services, and
upgrades. Upgrade clients to the matching release and regenerate
installed skills. Existing single-user databases require no data conversion.

This release adds phone access to the reader. Agent chat is not included.

---

PocketContext 0.18.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.18.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.18.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.

PocketContext 0.17.0

PocketContext 0.17.0

Run an initialized project's headless server and private tunnel together as one
foreground process:

./pocketcontext serve --headless --tunnel

• One operating-system service can supervise both components. The command owns
  both and refuses an already running server or tunnel.
• The tunnel starts after private-socket readiness, without opening reader TCP.
  Existing identity and address are preserved.
• Ctrl+C, SIGTERM and authenticated stop stop both and flush the database.
  Startup and terminal component errors shut down the other component and return
  an error so the service manager can restart the process.
• tunnel serve remains available with its independent background-server
  behavior; stopping that tunnel still leaves its server running.
• --tunnel requires --headless. Configure an OS service explicitly for boot,
  login and crash recovery; the CLI does not install one.

See Running a permanent service for a systemd user unit and
migration from two separate units. Follow Upgrades and use
matching client/server releases; regenerate installed skills after upgrading.

No database format, authentication protocol or dependency changes. Existing
single-user databases from 0.11.x through 0.16.2 require no data conversion.

---

PocketContext 0.17.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.17.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.17.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.

PocketContext 0.16.2

PocketContext 0.16.2

Start an initialized project's headless server and private tunnel with one command:

./pocketcontext tunnel serve

• A stopped server starts headlessly in the background; a compatible running
  server is reused without changing its listeners.
• The tunnel stays in the foreground. Ctrl+C or a tunnel failure leaves the
  database server running. Use pocketcontext stop to flush and stop it.
• Missing databases still require explicit initialization. Existing lease,
  conflict, release compatibility and authentication checks remain in force.
• Startup can be interrupted without continuing to tunnel identity setup.
  A background server already launched remains running.
• Generate the client setup prompt separately with tunnel invite after the
  tunnel reports readiness. Reader setup and sign-in recovery are unchanged.

No database format, authentication protocol or dependency changes. Existing
single-user databases from 0.11.x through 0.16.1 require no data conversion.
Follow the upgrade procedure, use matching server/client
releases and regenerate installed skills. Earlier website prompt files retain
their original bytes and release pins.