Releases: stef-k/CogniRelay
CogniRelay v1.4.8
CogniRelay v1.4.8 Release Notes
Release date: 2026-04-26
CogniRelay v1.4.8 is a focused packaging compatibility patch for the shipped
last-mile adapter skill. It fixes the cognirelay-continuity-authoring skill
from v1.4.7 so common skill loaders can accept it directly from
agent-assets/.
Highlights
- Added YAML frontmatter to the shipped
cognirelay-continuity-authoring
skill. - Preserved the existing skill body and responsibility split: CogniRelay is the
substrate, the running agent authors semantic continuity fields, and hooks or
adapters do not infer semantic meaning. - Added a flexible regression test that validates the frontmatter block without
overfitting line positions.
Compatibility Notes
- Runtime version is now
1.4.8. - Existing HTTP, MCP, graph, schedule, continuity, UI, and adapter-hook behavior
is unchanged. - The
GET /v1/capabilitiesversionfield remains the capability schema
version ("1").
Verification
Release preparation should pass:
git diff --check
./.venv/bin/python -m ruff check app tests tools agent-assets
./.venv/bin/python -m unittest tests/test_agent_assets_289.py -v
./.venv/bin/python -m unittest discover -s tests -vCogniRelay v1.4.7
CogniRelay v1.4.7 Release Notes
Release date: 2026-04-26
CogniRelay v1.4.7 ships the last-mile adapter kit for agent-authored
continuity integration. It is a distribution and integration-quality release:
the runtime API remains stable except for the added help topic, while operators
now get copyable assets for safe agent startup/retrieval and continuity saves.
Highlights
- Added
agent-assets/with a copyablecognirelay-continuity-authoring
skill and real stdlib-only Python hooks for retrieval and continuity save
flows. - The retrieval hook performs read-only startup orientation and optional
bounded context retrieval, surfacing graph and schedule orientation without
mutating continuity, tasks, or schedule items. - The continuity save hook supports
facts,template,dry-run,write,
readback, anddoctormodes with deterministic JSON output, placeholder
rejection, local-only dry-run diffs, and readback verification. - Added the runtime help topic
last-mile-adapter, available over HTTP and MCP
throughsystem.topic_help. - Updated agent onboarding and the documentation index so cold-start agents can
discover the shipped adapter kit and the responsibility split.
Compatibility Notes
- Runtime version is now
1.4.7. - Existing HTTP, MCP, graph, schedule, continuity, and UI behavior is unchanged
except for the added help topic and documentation/assets. - The adapter hooks are shipped as copyable assets. They do not become server
runtime behavior and do not infer semantic continuity content. - Scheduling guidance remains bounded: agents may create one-shot reminders
explicitly when needed, but the adapter hooks do not create, acknowledge,
retire, execute, or mutate schedule items. - The
GET /v1/capabilitiesversionfield remains the capability schema
version ("1").
Verification
Release preparation should pass:
git diff --check
./.venv/bin/python -m ruff check app tests tools agent-assets
./.venv/bin/python -m unittest tests/test_agent_assets_289.py -v
./.venv/bin/python -m unittest tests/test_help_214_slice1.py tests/test_help_243_runtime_onboarding_limits.py tests/test_mcp_216_slice3_help.py -v
./.venv/bin/python -m unittest discover -s tests -vCogniRelay v1.4.6
CogniRelay v1.4.6 Release Notes
Release date: 2026-04-26
CogniRelay v1.4.6 is a focused MCP startup compatibility patch for standard
request metadata. It fixes clients that send MCP-reserved params._meta during
startup or request-method calls.
Highlights
tools/listnow accepts object-valuedparams._metaand returns the tool
catalog instead of failing withunexpected tools/list param.initialize,tools/list,tools/call, and runtime MCP help/reference
request methods now accept and ignore object-valuedparams._meta.- Actual tool
argumentsremain strict application payloads._metainside
tool arguments is not treated as request metadata. - The regression suite now replays the previously failing startup path:
initializewithclientInfo.title, followed bytools/listwith
params._meta.
Compatibility Notes
- Supported MCP protocol versions remain
2025-06-18and2025-11-25. clientInfoimplementation metadata compatibility from v1.4.5 is preserved.- Non-object
params._metafails deterministically with-32602 Invalid params. - Unknown non-metadata request params still fail deterministically.
- No MCP tool schema, HTTP route, schedule, graph, continuity, or UI response
shape changed. - The
GET /v1/capabilitiesversionfield remains the capability schema
version ("1").
Verification
Release preparation should pass:
git diff --check
./.venv/bin/python -m ruff check app tests tools
./.venv/bin/python -m unittest discover -s tests -vCogniRelay v1.4.5
CogniRelay v1.4.5 Release Notes
Release date: 2026-04-26
CogniRelay v1.4.5 is a focused MCP startup compatibility patch. It fixes
standards-compatible clients whose initialize request includes optional
clientInfo implementation metadata.
Highlights
initializenow accepts standard MCP implementation metadata fields under
clientInfo:title,description,websiteUrl, andicons.- The exact observed Codex startup payload with
clientInfo.titlenow succeeds. - The compatibility fix is not Codex-specific; it applies to the supported MCP
protocol versions2025-06-18and2025-11-25. - Immediate
tools/listafter successfulinitializeremains supported.
Compatibility Notes
- Top-level
initialize.paramsremains strict:protocolVersion,
capabilities, andclientInfo. clientInfo.nameremains required whenclientInfois present.- Unknown
clientInfofields still fail deterministically with
-32602 Invalid params. - No MCP tool schema, HTTP route, schedule, graph, continuity, or UI response
shape changed. - The
GET /v1/capabilitiesversionfield remains the capability schema
version ("1").
Verification
Release preparation should pass:
git diff --check
./.venv/bin/python -m ruff check app tests tools
./.venv/bin/python -m unittest discover -s tests -vCogniRelay v1.4.4
CogniRelay v1.4.4 Release Notes
Release date: 2026-04-26
CogniRelay v1.4.4 is a focused patch release for Codex MCP startup
compatibility after the v1.4.3 protocol-version bridge.
Highlights
- MCP sessions are now ready for request methods immediately after a successful
initialize. - Codex clients that call
tools/listright afterinitialize, without first
sendingnotifications/initialized, can complete startup. notifications/initializedremains accepted afterinitialize, so clients
that send the notification keep working.
Compatibility Notes
- MCP protocol-version compatibility from v1.4.3 is preserved:
initializeaccepts2025-06-18and2025-11-25. - Unsupported or malformed
initializerequests still do not mark a session
ready. - Request methods before any successful
initializestill fail with the
existing not-initialized behavior. - No MCP tool schema, HTTP route, schedule, graph, continuity, or UI response
shape changed. - The
GET /v1/capabilitiesversionfield remains the capability schema
version ("1").
Verification
Release preparation should pass:
git diff --check
./.venv/bin/python -m ruff check app tests tools
./.venv/bin/python -m unittest discover -s tests -vCogniRelay v1.4.3
CogniRelay v1.4.3 Release Notes
Release date: 2026-04-26
CogniRelay v1.4.3 is a focused patch release for MCP startup compatibility
with currently deployed Codex clients.
Highlights
- MCP
initializenow accepts both protocol versions2025-06-18and
2025-11-25. - Successful MCP initialization echoes the accepted client-requested protocol
version, so older compatible clients can complete startup. - Unknown protocol versions still fail deterministically with
Unsupported protocol versionand a supported-version list. /.well-known/mcp.json, discovery metadata, and MCP docs now advertise both
supported initialize protocol versions while keeping2025-11-25as the
preferred/latest version.
Compatibility Notes
- No MCP tool, JSON-RPC method, HTTP route, schedule, graph, continuity, or UI
response shape changed outside MCP initialize protocol negotiation metadata. - The bounded MCP posture remains intact:
initialize,
notifications/initialized,ping,tools/list,tools/call, and the
existing post-bootstrap help/reference request methods are unchanged. - The
GET /v1/capabilitiesversionfield remains the capability schema
version ("1").
Verification
Release preparation should pass:
git diff --check
./.venv/bin/python -m ruff check app tests tools
./.venv/bin/python -m unittest discover -s tests -vv1.4.2
CogniRelay v1.4.2 Release Notes
Release date: 2026-04-26
CogniRelay v1.4.2 is a focused patch release for two post-v1.4.1 fixes:
durable audit redaction for context retrieval and shipped-doc rendering in the
operator UI documentation browser.
Highlights
context.retrieveaudit events no longer persist raw task text or task-text
prefixes in durablelogs/api_audit.jsonlrows.- Context retrieval audit rows now record deterministic
task_hashand
task_length_bytesmetadata while preserving result counts and loaded
continuity selectors. /ui/docsnow reads the allowlisted documentation shipped with the running
application checkout instead of looking for those files in the configured
data repository.
Compatibility Notes
- No
POST /v1/context/retrieverequest or response shape changed. - Retrieval ranking, continuity behavior, graph context, schedule context, MCP
protocol behavior, and operator UI routes are unchanged. - The audit detail shape for
context_retrievechanged intentionally:
detail.taskwas removed and replaced by safe hash/length metadata. - The
GET /v1/capabilitiesversionfield remains the capability schema
version ("1").
Verification
Release preparation should pass:
git diff --check
./.venv/bin/python -m ruff check app tests tools
./.venv/bin/python -m unittest discover -s tests -vv1.4.1
CogniRelay v1.4.1 Release Notes
Release date: 2026-04-26
CogniRelay v1.4.1 is a focused patch release for the agent onboarding and
runtime help surfaces introduced in v1.4.0.
Highlights
- Clarified the thread-scoped
context.retrieveexample so agents use
subject_kind="thread"plussubject_idfor primary retrieval scoping. - Clarified that top-level
thread_idis valid for task and schedule lookup
examples, but not for primarycontext.retrievescoping. - Added explicit due schedule inspection examples for both
thread_idfilters
andsubject_kind=threadplussubject_idfilters. - Kept MCP
system.tool_usageon its existing compact response shape while
improving the summary guidance.
Compatibility Notes
- No runtime API behavior changed.
- No MCP protocol shape changed.
- No schedule, graph, continuity, UI, or route semantics changed.
- The
GET /v1/capabilitiesversionfield remains the capability schema
version ("1").
Verification
Release preparation should pass:
git diff --check
./.venv/bin/python -m ruff check app tests tools
./.venv/bin/python -m unittest discover -s tests -vv1.4.0
CogniRelay v1.4.0 Release Notes
Release date: 2026-04-25
CogniRelay v1.4.0 completes the post-#218/#236 roadmap. The release turns the
post-hardening work into shipped agent-facing runtime surfaces, stronger
operator inspection tools, and coherent docs/help/discovery metadata.
Highlights
- Runtime onboarding and help: agents can discover onboarding sections,
startup guidance, route identifiers, validation limits, and help topics
through bounded HTTP and MCP help surfaces. - Agent-facing derived graph context:
context.retrievenow includes
boundedbundle.graph_contextby default, and startupcontinuity.read
includes a compact top-levelgraph_summaryafter the base read succeeds. - One-shot schedules and reminders: the new SQLite-backed schedule store
supports reminders and task nudges through HTTP and MCP, with UTC-only
timestamps, pull-based due evaluation, and scopedschedule_contextin
startup and context orientation responses. - Expanded read-only operator UI: the local UI now includes graph, task,
context retrieval, documentation, and schedule inspection pages, in addition
to the continuity-oriented surfaces. - Coherent docs and discovery: payload reference, API docs, MCP docs,
onboarding, runtime help, discovery descriptors, capabilities, and the UI docs
browser now describe the same shipped behavior.
Compatibility Notes
- The
GET /v1/capabilitiesversionfield remains the capability schema
version ("1"). New feature keys were added without changing the schema. - The durable continuity capsule write cap remains 20 KB. Graph and schedule
information are derived response adjuncts, not stored capsule data. - Schedule reminders are one-shot only in this release. Recurrence, background
scheduler loops, SSE/push delivery, arbitrary command execution, webhooks, and
automatic task/continuity mutation remain out of scope. - Non-startup
continuity.readremains graph-free by default. Startup reads
receivegraph_summary; context retrieval receivesbundle.graph_context.
Verification
Release preparation should pass:
git diff --check
./.venv/bin/python -m ruff check app tests tools
./.venv/bin/python -m unittest discover -s tests -vv1.3.1
Fixed
- MCP HTTP initialize requests now accept standard JSON-RPC payloads in the request body instead of failing with a 422 due to an incorrect payload query parameter binding.
- Strengthened MCP regression coverage so the generated /v1/mcp HTTP contract requires a JSON request body and no longer advertises payload as a query parameter.
Validation
- ./.venv/bin/python -m unittest tests.test_mcp_rpc -v
- ./.venv/bin/python -m ruff check app/main.py tests/test_mcp_rpc.py
- ./.venv/bin/python -m unittest discover -s tests -v