Changelog

gc_lookup: Tailwind CSS false-positive fixed; reingest cron no longer re-stages completed frameworks

gc_lookup was misclassifying Tailwind CSS class strings as markup and refusing to embed them, causing the Tailwind CSS framework docs to return zero results. Separately, the gc_lookup reingest cron was re-staging already-complete frameworks every run.

One-tap "send test notification" to verify push is wired

After enabling web push, users can immediately verify their device receives notifications. A button in the notification settings calls POST /v1/push/test, which sends a real push event to every active subscription for the account.

Web push notifications — phone alerts for replies and follows

gotcontext.ai is now an installable PWA with opt-in push notifications. Users who add the app to their home screen can receive native push alerts when someone replies to their comment or follows their profile.

Session-aware result deduplication for gc_lookup and search_semantic

When an agent calls gc_lookup or search_semantic multiple times in a session, results that were already returned in an earlier call are now filtered out automatically. This prevents the same chunk from occupying agent context window space twice across consecutive tool calls.

compress_tool_output — compress CLI and MCP tool output before re-feeding it

A new Pro-tier MCP tool and REST endpoint that strips ANSI codes, collapses repeated blank lines, elides stack-trace padding, and removes identical-line runs from CLI or tool output. An identifier footer is appended so models can distinguish compressed output from original text.

CompressResponse now includes a note field for inputs too small to benefit

POST /v1/compress now returns a non-null note string when the input is under ~200 tokens — the threshold where compression overhead exceeds the savings. Previously the API returned a negative savings_pct with no explanation.

Fixed order-dependent test flake in MCP tool catalog tests

An order-sensitive test was mutating the MCP tool catalog without restoring it, causing intermittent failures when tests ran in a different order. No behavior change in production.

Resend bounce and spam-complaint webhooks auto-set email opt-out

Hard bounces and spam complaints received from Resend now automatically set users.email_opt_out = True for the affected address, preventing future sends and closing a CAN-SPAM compliance gap.

Follow users — social graph with follow/unfollow + in-app notifications

Users can now follow each other. Following a user triggers an in-app notification for the target. The dashboard shows follower and following counts on profile pages.

User activity timeline and in-app reply notifications

A new activity feed and notification store lets users track replies, follows, and system events. The dashboard shows an unread badge on the notifications bell.

Content flagging and admin moderation queue

Users can flag comments, benchmark submissions, and news articles for review. Flagged content surfaces in a new /dashboard/admin/moderation queue for admins.

Benchmark comments and source attribution fields

Benchmark submissions now accept source_url and source_label fields for citing original research. Comment threads are now available on benchmark detail pages.

Pro plan badges and user avatar upload

Pro and above subscribers now display a Pro badge next to their username in comments and on profile pages. All users can upload a custom avatar (48 emoji options or image URL).

Admin price-audit monitor — weekly drift detection for model pricing

A new admin endpoint and dashboard surface shows detected drift between gotcontext's internal model-pricing catalog and live provider pricing. A weekly GitHub Actions cron runs the audit automatically.

Knowledge Hub: phantom "Indexing did not complete" + manual reindex endpoint

Knowledge Hub items that failed mid-embedding could get stuck in an INGESTING state, displaying a permanent "Indexing did not complete" banner in the dashboard with no recovery path. A new reindex endpoint lets users manually re-trigger ingestion.

Forum moderation system — content reports, mod actions, user silencing

A full moderation layer for the community feed: users can report comments, admins can act on reports, and repeat offenders can be silenced.

Rich comments — Markdown, hyperlinks, edit, and delete

Community feed comments now support Markdown formatting and hyperlinks. Comment authors can edit (with an "edited" timestamp) or delete their own comments.

Real usernames — choose a handle for community posts

Users can now set a unique username (handle) used in community feed comments and profile links. Existing users' display names remain their account full name until they set a handle.

Polar metering errors now surface in error monitoring

Failures in the Polar metering path were logged at a low severity level, making them invisible in error monitoring. They are now reported at error severity so they appear in alerts automatically.

Billing writes: usage-tracking now completes before response is returned

Usage-tracking writes in the billing path were dispatched as fire-and-forget background tasks and could be lost before completing during server suspend. They are now completed inline before the response is returned.

Automated weekly model-price audit

A new automated job runs weekly to detect drift between the internal model-pricing catalog and published provider rates. Detected drift generates an alert.

Model catalog: Gemini 3.1 Pro and Haiku 4.5 pricing corrected; gemini-3.5-flash added

Gemini 3.1 Pro was cataloged at $1.25/MTok input (should be $2.00). Haiku 4.5 input/output rates were swapped. gemini-3.5-flash was missing from the catalog entirely. All three affected the savings-estimate calculations on /v1/usage/by-model.

Opus pricing corrected from $15/$75 to $5/$25 across five surfaces

claude-opus-4 and claude-opus-4.5 had stale $15/$75 per MTok rates in the pricing catalog and across the web UI. Corrected to $5/$25. This lowered the displayed savings estimate for Opus-heavy workloads.

Three latent database query bugs fixed; regression guard added

Three database queries were silently failing in production due to a SQL syntax incompatibility. The affected paths (Knowledge Hub retention sweep and usage governance) were not executing. A regression guard prevents this class of bug from being introduced again.

gc_lookup reingest cron: COMPLETE frameworks no longer re-staged on every run

The gc_lookup framework re-ingest job was re-queuing every framework on every hourly run regardless of whether ingestion had already finished.

gc_lookup Phase B drain: free-tier slot starvation and head-of-line blocking fixed

The gc_lookup tool was using a single shared embedding queue that allowed a burst of free-tier embedding jobs to starve Pro jobs. A large framework (e.g. React docs) at the head of the queue could block all subsequent jobs until it completed.

Cache-hit savings now show up in your Cache-Adjusted Savings dashboard

Compression calls served from the semantic cache were not being recorded in the usage events behind the Cache-Adjusted Savings view, so cache ROI looked lower than it really was. They are now recorded with full cache attribution. Your billing and usage limits are unchanged — cache hits already counted toward your quota.

gc_submit_benchmark: submit a benchmark run straight from your MCP client

A new free MCP tool lets coding agents and Claude Code sessions submit a compression benchmark result directly, without leaving the terminal.

Fixed a 500 error on the Batch Queue dashboard page

The Batch Queue page returned a 500 for some accounts due to a Clerk user ID being passed where a UUID was expected. The page now loads correctly.

Benchmarks community: threaded Q&A, AI moderation, and a percentile ranking chip

Benchmark run pages now support threaded questions and answers, show where a result ranks among similar runs, and include AI-assisted moderation to keep discussions on-topic.

gc_lookup framework docs now refresh on a schedule

The gc_lookup free MCP tool now returns more complete and accurate answers for Tailwind CSS, LangChain, and SQLAlchemy, which previously had incomplete doc coverage.

Dashboard feed gains up/down votes and threaded comments

The /dashboard/feed page is redesigned as a community-style stream with voting, threaded comments, and a trending sidebar — unifying AI news, blog posts, and benchmark runs in one place.

Knowledge Hub dashboard redesigned with real per-source token metrics

The /dashboard/knowledge page shows a live metrics header (source count, total tokens indexed, average compression ratio) and per-source token counts, using the same token counter as /v1/compress.

GitHub push events can trigger per-project compression jobs

Teams with a connected GitHub repository can now have push and pull-request events automatically dispatch a compression job for changed files, using the access token already in their integration settings.

New sign-ups now get a Default project automatically

New accounts landed on an empty dashboard with no projects available. The projects endpoint now creates a Default project on first load for any account that has none.

Fixed an intermittent load race that left dashboard pages blank on hard refresh or fresh login

Around 25 dashboard pages could appear blank on a hard refresh or fresh login because data fetching started before Clerk had finished hydrating. All affected pages now wait for Clerk to be ready before fetching.

A new Feed — your logged-in home for AI news and benchmarks

Signed-in users now land on a Feed: one reverse-chronological stream of the latest AI news and community benchmark runs. News items appear compressed to a short skeleton with a compression-ratio badge, so the feed doubles as a live demo of what gotcontext does. The full tools dashboard stays one click away in the nav.

Automatic capacity scaling for steadier performance under load

The API now scales its compute capacity to live demand, so response times stay steady when traffic rises and costs stay low when it is quiet. No action required — this is fully automatic.

Compressing a very large document no longer fails

Compressing a large file (multi-megabyte documents producing tens of thousands of chunks) is now reliable. Previously the engine could exhaust memory building its internal similarity graph and the request would fail; memory is now bounded regardless of document size, and compression results are unchanged.

Framework docs lookups now return real documentation

Looking up Next.js, Pydantic, Drizzle, or FastMCP through the framework-docs tool now returns the actual API documentation with code examples, indexed from each project’s clean machine-readable docs. More frameworks follow.

Framework docs re-indexed from clean machine-readable sources

Framework documentation lookups now return real documentation prose for the first set of frameworks (Next.js, Pydantic, Drizzle, FastMCP), re-indexed from their clean machine-readable docs instead of scraped landing-page HTML. More frameworks follow.

Framework docs lookup now returns readable documentation

The free framework-docs lookup tool now returns the actual documentation text instead of a compressed placeholder. Where a framework was already indexed cleanly you’ll see real prose; a broader re-index of the framework catalog is in progress.

ingest_context now accepts a file_url with no inline text

If you ingest a document by URL through the ingest_context MCP tool, the call now works. Previously a file_url-only request was rejected with a “text cannot be empty” error before the URL was ever fetched; passing inline text was unaffected.

Release notes brought current + kept in sync automatically

These public release notes are now caught up to the latest release, and a deploy-time check blocks a release if they fall behind — so this page stays current going forward.

Referral credits now apply exactly once — even under concurrent or retried sign-ups

If you refer someone, your Pro period is extended exactly once. Previously a rapid retry of the sign-up event could double-apply the credit, and a separate edge case could under-apply it when two referrals landed at the same moment.

More reliable inbound event processing + zero-loss deploys

Billing, referral, and usage events delivered by our providers are now de-duplicated and survive a deploy without being dropped, so dashboard usage and account state stay accurate across releases.

Billing: plan state refreshes on renewal + clear past-due / canceled warnings

Your plan status now updates correctly when a subscription renews, and the billing page shows a clear banner if a subscription is past-due or canceled instead of appearing active.

Dashboard overview + site accessibility and reliability pass

The dashboard overview plus the security, status, and Agent Context Hub pages got an accuracy, accessibility, and reliability pass — including corrected API code samples, keyboard-focus rings, and a status page that no longer hangs when the API is slow.

New per-model token-cost savings pages

Added dedicated pages at /savings-by-model showing measured compression savings and live per-token pricing for each major model (Claude, GPT, Gemini, and more), each with a built-in “try it” compression demo.

Maintenance: tensor-grep dependency bumped to 1.13.21

Internal dependency update. tensor-grep >=1.13.21 brings 25+ patches from the 1.12→1.13 minor series. Three MCP tools (gc_agent_capsule, gc_context_render, gc_edit_plan) updated to use the new positional CLI form to maintain compatibility. No user-facing behaviour changes.

Internal stability: async background task cleanup

Three background-task sites had cleanup warnings under Python 3.14 that could cause unpredictable shutdown behaviour. All three are now cleaned up correctly.

Internal stability: two compression engine error fixes

Two internal bugs in the compression engine: ACE bullet ingestion could crash on a malformed payload, and a dependency import path was outdated. Both are fixed.

Fix: /news command palette showed raw locale key + empty state hid "No articles" message

See the web-v1.37.4 entry for full details.

Internal stability: billing SDK test isolation fix

Test-environment only — no customer-facing change. The billing SDK now initialises correctly in test environments, eliminating spurious errors during test teardown.

Fix: /news command palette showed raw locale key + empty state hid "No articles" message

Two customer-visible bugs on the /news surface. (1) The command palette (Cmd+K) entry for /news displayed a raw key string instead of the correct label. (2) The /news empty state (zero articles published) showed the newsletter subscription form but suppressed the "No articles published yet." message.

Fix: multimodal_ingest MCP tool crashed on every call

The multimodal_ingest MCP tool raised an error on every call. The underlying multimodal compression component was missing a required method in its text-encoder adapter. Fixed.

P0 hotfix: cache circuit breaker flapping — request amplification fixed

The cache circuit breaker flapped open/closed roughly 80 times over about 12 hours. Auth, rate-limiting, and plan-cache lookups fell back to slower paths on each open cycle, adding latency. The site remained up throughout. Root cause: an internal telemetry counter fired extra cache requests per operation (3× amplification), exhausting the monthly free-tier cap.

P0 hotfix: 3 endpoints returned 500 on invalid input

Three API endpoints returned 500 instead of the correct 400 or 404 on invalid or missing input. No data loss. Fixed with proper input validation.

gc_search_docs: hybrid keyword + semantic re-ranking

gc_search_docs now runs a two-stage retrieval: keyword search to find candidate chunks, then semantic re-ranking to promote the most relevant results. Semantically relevant chunks that score lower on keyword search are now promoted to their correct position. Falls back to keyword-only when embeddings are unavailable. Response includes a score_type field ("rrf" | "bm25") indicating which retrieval path was used.

Knowledge Hub REST API — /v1/kb/* mirrors all 7 MCP tools

Non-MCP clients (curl, Python SDK, server-side fetch) can now use Knowledge Hub via standard REST without wiring an MCP transport. All 7 gc_kb_* operations are available: ingest, list, get, edit (optimistic concurrency), delete, version history, and semantic query.

Advisory MCP tool calls now visible in dashboard; /news/[slug] gets stale cache + error boundary

Orchestrator sessions that exclusively used advisory tools (gc_pre_flight, tool_help, search_semantic, etc.) showed zero events on the dashboard despite 50+ MCP calls. Advisory tools now write zero-token activity rows so all tool usage is visible. The /news article detail page now serves stale content on transient errors rather than propagating a 5xx to visitors.

Fixed in:

API v1.35.7

Components:

MCP Gateway · Dashboard · News page

/v1/global-savings now sets Cache-Control: public, max-age=60 for Vercel edge caching

The landing page hero counter endpoint is called on every SSR render. Adding a 60s public Cache-Control header lets the Vercel edge layer absorb repeated calls, reducing Fly request rate on the highest-traffic surface without any behavior change to the displayed data.

Fixed in:

API v1.35.6

Components:

API

llms.txt line 36 stale tool count fixed; /v1/filter-cli documented in API reference

gotcontext.ai/llms.txt now consistently shows 148 tools across all bullets (line 36 previously retained the stale "142" count). docs/architecture/API.md now documents the /v1/filter-cli endpoint which was undocumented since its initial ship.

Fixed in:

API v1.35.5

Components:

llms.txt · API documentation

Post-ship audit bundle — gc_read_doc HTML fix, NewsArticle type seam, drafter truncation, /news SSR cache

gc_read_doc now returns readable markdown instead of raw HTML. The /news listing page serves stale cache on rate-limit bursts rather than 500ing all concurrent visitors. The news drafter no longer retries (at $0.12/call) when title/excerpt exceed length limits. Frontend NewsArticle type is split to match the backend wire shape, eliminating undefined reads on list vs detail fields.

Fixed in:

API v1.35.4

Components:

MCP Gateway · News pipeline · News page

Reliability bundle — revoke broadcast ordering, document-fetch size limit, cross-document search isolation

Revoked API keys are now reliably invalidated even when the cache-invalidation call fails. The document-fetch size limit now raises an error instead of silently passing. Cross-document search isolation is now confirmed end-to-end.

Fixed in:

API v1.35.3

Components:

API key lifecycle · MCP Gateway

KB async upload — stuck-INGESTING recovery

File uploads that entered INGESTING but never completed (worker crashed between tx1 and tx2, e.g. on Fly machine suspend) now recover automatically. A new hourly cron sweeps rows stuck in INGESTING for >10 minutes and transitions them to FAILED with a retry message. Previously these rows were invisible to the kb-process-uploads cron (WHERE status='UPLOADED') and sat stuck indefinitely.

Fixed in:

API v1.35.2

Components:

Knowledge Hub

search_semantic and gc_search_docs: hybrid keyword + semantic retrieval

search_semantic and gc_search_docs now fuse semantic and keyword scores for better recall on exact-token queries. Response carries score_type: "rrf" | "cosine" so callers can detect which retrieval path was used.

Fixed in:

API v1.35.1

Components:

MCP Gateway

MCP catalog hot-reload + circuit-breaker telemetry + SSE keepalive + scoped API keys

Operators can now hot-reload the MCP tool catalog without restarting servers (admin-only, rate-limited). Circuit breakers emit Prometheus telemetry. MCP SSE connections survive idle proxy timeouts. Dashboard ships a least-privilege scope picker for minting scoped gc_ keys. Document-fetch paths hardened against requests to private or internal network addresses.

Fixed in:

API v1.34.35

Components:

MCP Gateway · Dashboard · API key lifecycle · Compression API

MCP tools now signal parallel-dispatch eligibility via readOnlyHint annotation

Three read-only MCP tools (gc_lookup, search_semantic, read_skeleton) are now marked as read-only in their schema, following the MCP spec's readOnlyHint annotation. Compatible MCP clients can use this hint to safely run these tools in parallel.

Fixed in:

API v1.34.34

Components:

MCP Gateway

gc_search_docs now matches morphological variants (authentication → authenticate)

gc_search_docs now matches morphological variants of a query term. Previously a search for "authentication" returned nothing when the docs contained only "authenticate" or "auth". Query terms of six or more characters now match by prefix, so "authentication" matches "authenticate" and "compression" matches "compressed". Shorter queries still require an exact match to avoid false positives.

Fixed in:

API v1.34.33

Components:

MCP Gateway

Hotfix: gc_search_docs now actually returns results; gc_read_doc respects size limits

Two bugs found immediately after the v1.34.31 release. (1) gc_search_docs returned empty results because it assumed a static documentation-index path that does not exist in production; it now fetches the live index directly. (2) gc_read_doc could return documents large enough to exceed MCP client tool-result limits; responses are now capped to a safe size.

Fixed in:

API v1.34.32

Components:

MCP Gateway

Search + read gotcontext docs via MCP (free tier) — gc_search_docs + gc_read_doc

First ship of the MCP API parity plan (3-4 week roadmap, CEO-approved). Agents can now search and read gotcontext product documentation without leaving their terminal. Free for all plans, no auth required — top-of-funnel conversion utility per industry research on Context7 + ref.tools precedents. Install the plugin once, ask your AI "how do I authenticate with gotcontext?", and it answers from the live docs.

Fixed in:

API v1.34.31

Components:

MCP Gateway · Claude Code plugin

modulate_region now accepts singular node_id alongside node_ids

Agents calling modulate_region with a singular node_id string previously got a validation error because only the plural node_ids list form was accepted. Now both forms work: a singular node_id string is accepted and treated as a single-element list. Backward compatible — existing node_ids callers are unchanged.

Fixed in:

API v1.34.30

Components:

MCP Gateway

batch_ingest_documents MCP schema now exposes scope params (session_id, workspace_id, user_id, agent_id)

Discoverability fix from v1.34.28 F12 verification: the handler already accepted session_id but the MCP tools/list schema for batch_ingest_documents did not declare it (or the other 3 scope params). Agents enumerating the catalog now see these params via the documented schema. Per-session savings tracking from v1.34.28 now works correctly when callers want non-default session scoping. Handler behavior unchanged.

Fixed in:

API v1.34.29

Components:

MCP Gateway

Per-session savings now reflect read_skeleton, batch_ingest, ingest_directory, and filter_cli_output

v1.34.27 fixed F12 narrowly on ingest_context, but handlers that bypassed it (BatchCompressionManager.compress_batch → compressor.ingest_file_async directly) still skipped the per-session SavingsTracker. v1.34.28 wires the four remaining real-savings producers: read_skeleton, batch_ingest_documents, ingest_directory, and filter_cli_output. The broader F12 class is now fully closed — every agent that calls get_savings_report / get_savings_inline mid-session sees real numbers regardless of which compression tool produced them.

Fixed in:

API v1.34.28

Components:

MCP Gateway

Per-session savings reports now reflect ingest_context activity

Pre-fix the SavingsTracker was dead infrastructure — _get_tracker existed but was only ever called by .get_report() paths, never .record(). Every agent that called get_savings_report or get_savings_inline mid-session after an ingest_context call saw $0 / 0 tokens saved even after real compression activity. The mismatch with /v1/global-savings (which already showed 1.38M tokens saved across all users from the persistent usage_events table) confirmed the per-session tracker was never receiving the events the report was reading. Agents querying their own savings now see real numbers.

Fixed in:

API v1.34.27

Components:

MCP Gateway

Unregistered unused /webhooks/resend route

No Resend webhook is configured, so the registered endpoint was being probed by bots. POST /webhooks/resend now returns 404.

Fixed in:

API v1.34.26

Components:

Webhook delivery

Agent-driven gc_ key lifecycle: mint + revoke via MCP

Agents (CI runners, Claude Code sessions, automation) can now manage gc_ API key lifecycle without a dashboard session. Pro+ only.

Fixed in:

API v1.34.25

Components:

MCP Gateway · API key lifecycle

Internal: reduce observability noise from unconfigured Resend webhook

Reduced error noise from an unconfigured Resend webhook endpoint. The 400 response to inbound calls is unchanged.

Fixed in:

API v1.34.24

Components:

Webhook delivery

read_skeleton JSON serialization 500 + ingest_context ENOENT on multi-segment file_id

Two bugs found in internal testing. (1) Calling ingest_context with an inline query parameter returned a 500 error, which broke the recommended ingest-and-query workflow. (2) Calling ingest_context with a multi-segment file_id failed on first write because the parent directories were not created automatically.

Fixed in:

API v1.34.23

Components:

MCP Gateway

read_skeleton default mode changed to "auto" + internal test fixes

read_skeleton now defaults to "auto" selection mode, which routes to the best available compression strategy. Previously it defaulted to "baseline".

Fixed in:

API v1.34.22

Components:

MCP Gateway

ingest_context now accepts a remote URL to fetch and ingest server-side

MCP agents can now pass a remote HTTPS URL to ingest_context instead of pasting document text inline. The server fetches and ingests the content, with validation that the URL resolves to a public address. text and file_url are mutually exclusive; successful fetches stamp source_url on the response.

Fixed in:

API v1.34.21

Components:

MCP Gateway

gc_rebind_api_key: headless API key project attribution via MCP

CI runners, Claude Code sessions, and automation can now change which project a gc_ API key is attributed to without a dashboard session. Pro+ only.

Fixed in:

API v1.34.20

Components:

MCP Gateway · API key lifecycle

News drafter body substance floor — closes auto-published shitpost gap

The full-site audit caught an auto-published one-word "Bruh" article on /news with full Industry News card treatment. The ingest quality gate (v1.34.0) filters by title regex + ups + comments threshold, but the drafter validator accepted any truthy body — a clickbait-titled high-ups Reddit post with a one-word body cleared both ingest AND drafting. The fix adds a minimum body floor at validation time so future shitposts are rejected before queue insertion.

Fixed in:

API v1.34.19

Components:

News pipeline

/news/[slug] Clerk middleware crash + /news/editorial-standards redirect

Every uncached SSR render of /news/[slug] threw `Clerk: auth() was called but Clerk can't detect usage of clerkMiddleware()` because src/proxy.ts only wraps clerkMiddleware around protected routes — the (unauth)/news/[slug] paywall added in v1.28.3 called auth() from a route NOT covered by the matcher. Vercel CDN cache masked most events; Sentry surfaced 2 events from manual URL-entry to /news/editorial-standards. The fix uses try-catch so the throw is treated as "no session" (paywall preview path). Also added a permanent redirect /news/editorial-standards → /news/about so external references no longer hit the [slug] catch-all.

Fixed in:

Web v1.29.2

Components:

News page

News ingest hardening — informal-tone gate + source_slug propagation

Tightened the ingest quality gate to reject overly-informal Reddit titles before drafting, and threaded the source_slug field through the publish path so per-source filters on /news work correctly. Internal-quality improvements — no customer-facing UX change.

Fixed in:

API v1.34.18

Components:

News pipeline

News ingest test hardening (internal)

Internal test-suite hardening on the news ingest path — no customer-facing change. Backfilled to satisfy the public-changelog-sync gate (CEO directive 2026-05-19 requires every CHANGELOG.md version to appear on this page).

Fixed in:

API v1.34.2

Components:

News pipeline

/news round 1 of rate-fix-rate loop — 2 high-confidence fixes (head metadata + inline code)

Two /news fixes: (1) Page head metadata still showed old "AI News" / "Hand-curated" strings after the H1 rename, causing incorrect titles in browser tabs and link unfurls. (2) Inline code spans in news articles were rendering as full-width blocks instead of inline.

Fixed in:

Web v1.27.9

Components:

News page

RSS feed at /news/feed.xml — aligned with the news strategy ship

The Atom/RSS feed at /news/feed.xml predates the news strategy ship and carried 3 misalignments: (1) channel title "AI News" collided with competitor AINEWS brand (2) channel description still claimed "Hand-curated" — same lie the listing page subhead fixed in v1.27.6 (3) entry links pointed to external source_url instead of on-domain /news/[slug] — the same SEO/attention-leakage problem the listing card title fix addressed. RSS subscribers (power users + LLM agents) now land on our analysis where the source is then linked at the bottom.

Fixed in:

Web v1.27.8

Components:

News page

Multi-source news ingest — infrastructure for lab blogs and HN (disabled by default)

Infrastructure for ingesting news from multiple source types (lab blogs, HN). Disabled by default — production continues on Reddit-only until sources are configured.

Fixed in:

API v1.34.6

Components:

News pipeline

Markdown tables now render on news article pages

The news article page was missing support for GitHub Flavored Markdown, so tables, strikethrough, and autolinks rendered as plain text. Cost-comparison tables in articles now display correctly with proper alignment.

Fixed in:

Web v1.27.7

Components:

News page

Cost-of-Inference weekly column — deterministic cost tables across live model catalog

New weekly article format publishing deterministic per-model cost calculations across the live model pricing catalog. Numbers are formula-derived, not AI-generated — no hallucination risk on cost figures.

Fixed in:

API v1.34.5

Components:

News pipeline

News articles upgraded to 600-900 word structured analysis

Drafted news articles now follow a structured 5-part format (lede, statistics, analysis, forward-looking, sources) at 600-900 words, replacing the previous 400-900 word unstructured format.

Fixed in:

API v1.34.4

Components:

News pipeline

News page — content strategy update, copy improvements, and cost controls

The news section has been repositioned as an analyst surface focused on LLM unit economics and benchmark-backed analysis. Thumbnail generation costs reduced; clickbait headline patterns banned from the drafter.

Fixed in:

API v1.34.3 + Web v1.27.6

Components:

News page · News pipeline

News drafter re-applies quality gate at publish time to clear legacy queue

The quality gate added in v1.34.0 applied only to newly ingested items. Existing queued items were still eligible for publishing. The drafter now re-checks queued items at claim time and skips any that do not meet the current title criteria.

Fixed in:

API v1.34.1

Components:

News pipeline

News drafter now filters for important news — quality gate at ingest

Previously the drafter published every post that surfaced from community feeds, including help requests, weekly meta threads, and general questions. Ingest now applies a quality gate: minimum engagement thresholds (upvotes and comments) plus a title blocklist. Both thresholds must pass simultaneously.

Fixed in:

API v1.34.0

Components:

News pipeline

/news category filter — was showing 0 articles for every category

The category filter showed "All (30)" but every individual category chip showed 0 articles. The filter chip list was hardcoded with categories that did not match what the drafter actually produces. Fixed by deriving the chip list from the articles currently loaded — new categories automatically appear without any code change.

Fixed in:

Web v1.27.5

Components:

News page

News drafter — structural rules for AI search citation eligibility

Six structural rules added to the drafter prompt shape every article toward eligibility for citation in AI search results (ChatGPT, Perplexity, Claude, Gemini). Rules focus on lede structure, named sources, concrete statistics, and self-contained excerpts.

Fixed in:

API v1.33.0

Components:

News pipeline

/news metrics instrumentation — pageview, scroll depth, source clicks, and AI Search referral attribution

Analytics instrumentation added to track which articles get visits and engagement. Captures article pageviews, scroll-depth milestones, source clicks, and referral channel — including distinguishing AI Search (ChatGPT, Perplexity, Claude, Gemini) from traditional search and social.

Fixed in:

Web v1.27.4

Components:

News page

/news SEO upgrade — NewsArticle JSON-LD enhancements and per-article sitemap entries

Each article page now emits richer JSON-LD structured data (canonical entity URL, article section, language, free-access flag, image as ImageObject). The sitemap now enumerates each published article individually with its last-modified date so search engines can crawl articles directly.

Fixed in:

Web v1.27.3

Components:

News page

/news thumbnails now display at thumbnail size instead of stretching to full-width

Article thumbnails on the news listing and article detail pages were rendering as full-width banners. The listing now shows a fixed-size thumbnail beside article content; the detail page caps the image at a compact width.

Fixed in:

Web v1.27.2

Components:

News page

News article thumbnails: retry logic and hourly backfill improve coverage from ~30% to ~80%

Production showed only about 30% of articles had thumbnails. The image generator sometimes returns a text-only response for certain article topics. A retry with a simplified prompt is now attempted, and an hourly backfill cron sweeps recent articles missing thumbnails.

Fixed in:

API v1.32.12

Components:

News pipeline

P0 — news ingest silently fell back to 1 source after server recycle; 8-subreddit seed now durable

The 8-subreddit expansion shipped in v1.32.10 was seeded via a manual one-time database command rather than a schema migration. Server recycling wiped that data, causing ingest to silently fall back to a single source. The seed is now applied via a migration that survives every deploy.

Fixed in:

API v1.32.11

Components:

News pipeline

News ingest now pulls from 8 subreddits covering AI engineering, Claude, OpenAI, and Gemini communities

Ingest was previously pulling from a single source. It now iterates over all configured sources. The source set expanded to 8 subreddits covering AI engineering practitioners, Claude Code workflows, and official lab feeds. A failed feed does not abort the remaining sources.

Fixed in:

API v1.32.10

Components:

News pipeline

Hotfix — news thumbnails were uploading to the wrong storage bucket, causing public URLs to 404

Thumbnail generation in v1.32.8 wrote to an incorrect storage bucket, so all generated thumbnail URLs returned 404. Thumbnails now write to the dedicated news-thumbnails bucket.

Fixed in:

API v1.32.9

Components:

News pipeline

News drafter now generates an AI-produced hero thumbnail per draft

Every news draft now gets an original AI-generated 16:9 editorial thumbnail at draft time. Image generation runs concurrently with text drafting so wall time is not significantly increased. A monthly budget cap prevents runaway spend.

Fixed in:

API v1.32.8

Components:

News pipeline

Hotfix — admin "Approve" returned 500 when publishing a news draft

Every admin click on "Approve draft" returned HTTP 500. The publish, edit, and withdraw article paths were passing timestamp strings to the database instead of datetime objects.

Fixed in:

API v1.32.7

Components:

News pipeline

News drafts auto-publish 1 hour after entering the queue

Drafts that are not manually reviewed within 60 minutes are automatically published. Human-reviewed drafts continue to publish immediately on click. The audit trail records whether an article was auto-published or human-approved.

Fixed in:

API v1.32.6

Components:

News pipeline

Hotfix — admin drafts queue showed empty bodies when expanding a draft for preview

The draft list endpoint was omitting the article body from its response. Expanding any draft in the admin queue showed a blank body. Draft bodies now appear correctly.

Fixed in:

API v1.32.5

Components:

News pipeline

Hotfix — admin pages crashed because the draft list response shape did not match the frontend type

After v1.32.3 fixed admin authentication, both admin pages immediately crashed with a "Cannot read properties of undefined" error. The frontend type expected a wrapped object but the API returns a bare array. Both pages now render correctly.

Fixed in:

Web v1.32.4

Components:

Dashboard

Hotfix — admin drafts queue returned 403 for every click even with a valid admin session

The public news read path was inadvertently matching the admin sub-path, causing the authentication middleware to skip session validation. Admin endpoints now correctly require authentication while public news reads remain unauthenticated.

Fixed in:

API v1.32.3

Components:

Dashboard

Hotfix — news-draft cron returned 500 due to incorrect timestamp format in database queries

The news drafter cron returned HTTP 500 after the auth bypass was fixed in v1.32.1. Timestamp values were being formatted as strings before being passed to the database, which requires datetime objects.

Fixed in:

API v1.32.2

Components:

News pipeline

Hotfix — news-draft cron returned 401 on every scheduled run

The news drafter cron endpoint was not correctly configured as a cron route, causing every scheduled run to be rejected before the cron secret check ran. No production cron runs were lost; the fix landed before the first scheduled trigger.

Fixed in:

API v1.32.1

Components:

News pipeline

In-tree AI News drafter pipeline and admin approval queue

An hourly cron now generates publication-ready news article drafts from ingested items, with editorial validation (kill-word checks, ownership-mention scrubbing) and a monthly budget cap. Drafts go to an admin approval queue before publishing.

Dependency update — tensor-grep version pin updated; no customer-visible change

Dependency version floor updated. No customer-visible behaviour change.

Hotfix — Vercel production deploys had been failing since 2026-05-19

Production deploys were failing at the prerender step due to an auth hook used inside a component that runs at static-site-generation time where the auth provider is not in scope. The auth-aware navigation swap has been reverted.

Fixed in:

API v1.31.1 / Web v1.27.1

Components:

Dashboard

News page — discoverability, RSS feed, newsletter capture, markdown rendering, hero image cards

The /news section was not linked from any navigation, footer, or sitemap. This release adds /news to all primary navigation entry points, replaces the empty-state dead-end with a newsletter capture form, adds an RSS feed, upgrades article rendering to full markdown, and adds reading-time, source attribution, and hero image cards.

Fixed in:

API v1.31.0 / Web v1.27.0

Components:

News page

Hotfix — news ingest was failing silently; all Reddit items were landing in the error bucket

After v1.30.0 shipped the news ingest cron, all 25 ingested items were being rejected because a timestamp was passed as a string rather than a datetime object. All items now ingest successfully.

Fixed in:

API v1.30.2

Components:

News pipeline

Hotfix — news ingest cron was returning 401 on every scheduled run

The news ingest cron endpoint was not correctly configured as a cron route, causing every scheduled run to be rejected. No production runs were lost; the fix landed before the first scheduled trigger.

Fixed in:

API v1.30.1

Components:

News pipeline

In-tree news ingest cron replaces third-party scheduler that was silently not running

The original news ingest architecture used a third-party workflow scheduler that was found to silently fail to register cron jobs. News ingest is now handled by a native API cron endpoint running hourly. Deduplication prevents re-ingesting the same items across runs.

Fixed in:

API v1.30.0

Components:

News pipeline

Hotfix — public news read endpoints were incorrectly requiring authentication

News article listing, category, and individual article read endpoints were requiring authentication, making /news inaccessible to unauthenticated visitors. Read endpoints are now public; write/admin endpoints remain authenticated.

Fixed in:

API v1.29.1

Components:

News page

AI News Center — storage and read surface for the news feed

New /news public read routes and admin write endpoints ship the storage and read surface for an AI news feed. Articles can be submitted, edited, published, and DMCA-withdrawn. Public reads are unauthenticated for SEO.

Fixed in:

API v1.29.0 / Web v1.26.0

Components:

News page

Resend bounce webhook, landing CTA analytics, and billing cost accuracy

Three improvements shipped together. Email bounces and complaints now automatically suppress future emails to the affected address. Landing page CTA clicks are now tracked for conversion analysis. A CI gate ensures future billing cost calculations route through the central cost model.

Fixed in:

API v1.28.0 / Web v1.25.0

Components:

Webhook delivery · Dashboard · Billing

AI Benchmark Repository — community-standard schema (multi-GPU, Apple Silicon, ITL, speculative decoding)

The benchmark schema now matches the fields used by NVIDIA NIM, vLLM, MLPerf, and the Apple Silicon community — making submitted results directly comparable to numbers published elsewhere. New hardware-class filter tabs (NVIDIA CUDA / AMD ROCm / Apple Silicon / Intel Arc) let you find relevant results without scrolling.

Fixed in:

API v1.27.0

Components:

/benchmarks leaderboard · /benchmarks/submit wizard · /benchmarks/runs/:slug result page · POST /v1/benchmarks/runs · GET /v1/benchmarks/leaderboard

AI Benchmark Repository — submit wizard, leaderboard, permalinks, diagnostics, and MCP tool

The complete benchmark surface is now live: a 3-step submit wizard, sortable leaderboard with 4 ranking lenses (tokens/sec · $/Mtok · tokens/sec/watt · value composite), shareable per-run permalinks with automated diagnostics, and a `submit_benchmark` MCP tool so agents can log results programmatically.

Fixed in:

API v1.26.0

Components:

/benchmarks/submit · /benchmarks leaderboard · /benchmarks/:modelSlug per-model page · /benchmarks/runs/:slug permalink · MCP `submit_benchmark` tool · POST /v1/benchmarks/runs · GET /v1/benchmarks/leaderboard · GET /v1/benchmarks/runs/:id_or_slug

AI Benchmark Repository — foundation (schema, REST API, outlier detection)

The gotcontext.ai benchmark repository is now open for submissions. Log your inference runs — model, quant, hardware, context length, batch size, tokens/sec — and get a shareable permalink. Anonymous submissions are accepted alongside authenticated ones.

Fixed in:

API v1.25.0

Components:

POST /v1/benchmarks/runs · GET /v1/benchmarks/runs/:id_or_slug · GET /v1/benchmarks/leaderboard · POST /v1/benchmarks/runs/:id/flag · GET /v1/benchmarks/hardware

Billing accuracy sweep — model-aware pricing across all savings surfaces

Savings figures are now consistent and model-accurate across every surface: the weekly digest email, the usage alert suffix in `/v1/usage`, and the per-compression `estimated_cost_saved` field. Customers running Claude Opus were seeing savings understated by up to 5×; Haiku users were seeing savings overstated by up to 3.75×. No customer action required — the fix applies to the next weekly digest and any new compressions.

Fixed in:

API v1.23.20

Components:

weekly digest email · /v1/usage alert suffix · /v1/compress estimated_cost_saved · Pro pricing copy in two email templates

MCP gateway — ?profile=core (7 tools, ~2K tokens) vs ?profile=full (142 tools)

Clients that only need compression, search, and memory can now connect to `https://api.gotcontext.ai/mcp?profile=core` and receive exactly 7 essential tools using ~2K tokens instead of ~38K. The default unparameterized URL is unchanged and continues to advertise the full 142-tool catalog.

Fixed in:

API v1.23.18

Components:

MCP Gateway · Claude Code plugin

MCP gateway hardening — schema accuracy, SSRF policy errors, and 142-tool coverage sweep

Three reliability improvements to the MCP gateway: the `gc_blast_radius` tool now correctly communicates that `focus_symbol` is required (previously the schema said optional but the underlying tool required it, causing confusing errors); SSRF-blocked requests now return a structured JSON error instead of a bare network message; a 142-tool end-to-end sweep confirmed every tool works as documented.

Affected:

MCP clients using `gc_blast_radius` without `focus_symbol` prior to API v1.23.15

Fixed in:

API v1.23.15

Components:

MCP `gc_blast_radius` tool · MCP `proxy_mcp_server` tool · MCP `check_budget` tool

Four new MCP tools for code context — agent capsule, edit plan, callers, context render

Four new Pro-tier MCP tools give agents structured context before making code changes: `gc_agent_capsule` summarises what to change and validates it, `gc_edit_plan` produces a machine-readable edit plan, `gc_callers` finds call sites for a symbol, and `gc_context_render` returns a ranked prompt-ready context bundle for a natural-language query.

Fixed in:

API v1.23.9

Components:

MCP `gc_agent_capsule` (new) · MCP `gc_edit_plan` (new) · MCP `gc_callers` (new) · MCP `gc_context_render` (new) · MCP `gc_blast_radius` (extended)

`gc_blast_radius` restored — tool was returning degraded responses for most callers

The `gc_blast_radius` MCP tool was returning a degraded error response for any caller who did not pass `focus_symbol` (which the schema incorrectly marked optional). This affected the majority of real-world uses. The tool now returns a clear, actionable error when `focus_symbol` is missing. Callers who were passing it correctly were unaffected.

Affected:

API v1.23.0 – v1.23.6 (gc_blast_radius callers omitting focus_symbol)

Fixed in:

API v1.23.8

Components:

MCP `gc_blast_radius` tool

French locale landing page and sign-up now render in French; billing checkout path fixed

The French-language site (`/fr/`) was displaying English copy despite `<html lang="fr">` being set. Every major landing page section (Hero, Navbar, Features, FAQ, CTA, Footer) and the sign-up page now render in French. Separately, the pricing page CTA (`/sign-up?plan=pro`) now correctly routes new users through sign-up into the Polar checkout — the `plan` parameter was previously dropped silently.

Fixed in:

API v1.23.6

Components:

/fr landing page · /fr/sign-up · /dashboard/billing upgrade CTA

Agent payment settlement status now flips correctly after payment verification

When an agent paid for a compression call via Nevermined or Skyfire, the payment was processed but the settlement status remained stuck at "pending" permanently. The reconciliation API now reflects settled payments correctly. This is an infrastructure fix; no end-user action is required.

Fixed in:

API v1.23.2

Components:

Agent payment processing · GET /v1/payments/reconciliation · /v1/compress (agent-payment-authenticated calls)

Public changelog now auto-synced: CI hard-fails when the page drifts behind CHANGELOG.md

A new CI gate ensures the customer-facing changelog at /changelog is updated with every release. The gate allows exactly one in-flight version (the time between writing a CHANGELOG entry and deploying the page update), but fails the deploy if two or more releases are missing. This release also backfills the public page with 10 entries covering API v1.23.2 through v1.27.0 that were missing.

Fixed in:

API v1.27.1

Components:

/changelog

Analytics savings figures now match the dashboard's top-keys widget

The per-project analytics summary was showing savings figures that did not match the "Top expensive keys" widget on the main dashboard. The two surfaces were using different formulas and different time windows. Both now use the same model-aware pricing and a consistent 30-day window by default.

Fixed in:

API v1.23.19

Components:

GET /v1/analytics/summary · /dashboard/analytics per-project savings · /dashboard Top expensive keys widget

MCP tool schema honesty improvements and 142-tool end-to-end sweep CI gate

The `check_budget` tool now returns a validation error when called with unknown fields (it was previously silently ignoring them). Knowledge Hub MCP tools now explicitly document the requirement for a project-bound API key in their descriptions. A CI job runs the full 142-tool end-to-end sweep against live production after every deploy.

Fixed in:

API v1.23.17

Components:

MCP `check_budget` tool · MCP `gc_kb_*` tools (7 tools)

Internal: CI test fix for Knowledge Hub SQLite compatibility — no customer-visible change

Three consecutive releases were blocked from deploying to production by a CI test failure in the Knowledge Hub test suite. Fixed by correctly skipping Postgres-specific tests when CI runs against SQLite. No customer-visible change.

Fixed in:

API v1.23.10

Components:

CI test suite

Quality sprint — dashboard accessibility, pricing rewrite, blog standardization

Four dashboard surfaces (Webhooks, Teams, Profiles, Admin) audited to 3/3 convergence for accessibility, focus management, and error semantics. The /pricing page was rewritten in two waves (ROI calculator, SLA matrix, sub-processors list, trust portal); a separate fix corrected the contact form rendering raw HTML. Every blog post now uses the same canonical layout (TOC, cite block, related links, contribute grid) and was scrubbed against an anti-AI-writing rubric.

Fixed in:

Web v1.24.1

Components:

/dashboard/webhooks · /dashboard/teams · /dashboard/profiles · /dashboard/admin · /pricing · /docs · /blog

Onboarding email drip + free-tier MCP context lookup tool

New users receive a 5-email onboarding drip over 14 days via Resend (feature-flag-gated against the existing welcome path so existing users are unaffected). Free-tier MCP keys can now see `gc_lookup` in `tools/list` (returns 501 stub pending the Phase 2 ingestion pipeline; behaviour will change to a working response without a version bump when Phase 2 ships).

Fixed in:

API v1.23.0

Components:

Email onboarding · MCP Gateway · Free tier

AI news feed and framework context hub

Two new pages on gotcontext.ai for AI context-engineering reference: `/news` (chronological feed of curated AI items across Models, Funding, Tools, Papers, Infrastructure, Agents, Policy) and `/context` (framework hub covering 9 frameworks: Next.js, FastAPI, LangChain, SQLAlchemy, Pydantic, Tailwind, Drizzle, FastMCP, React).

Fixed in:

Web v1.24.0

Components:

/news · /context

Budget alert delivery restored for users who re-enabled email alerts

Users who opted out of email alerts and then later re-enabled them were not receiving the 75 / 90 / 100 % project-budget threshold notifications. Fixed in API v1.22.8. No customer action required — the next budget-check tick after the upgrade will deliver the still-relevant alert.

Fixed in:

API v1.22.8

Components:

Project budgets · Email alerts

GET /v1/projects/{id}/usage returned 500

The per-project usage endpoint had been returning HTTP 500 in production. The dashboard's per-project usage tab and any direct API integration relying on this endpoint were affected. Fixed in API v1.22.7.

Fixed in:

API v1.22.7

Components:

/v1/projects/{id}/usage · per-project usage tab

is_default field exposed on /v1/projects responses

The default-project marker is now returned by the API so client code can drive UI gating from server truth instead of inferring it from a project name. No breaking changes — additive field.

Fixed in:

API v1.22.7

Components:

/v1/projects · dashboard project picker

Removed 5 unimplemented MCP tool stubs from tools/list

Five MCP tools that appeared in `tools/list` had no implementation behind them — calling them returned an error. They have been removed from the listing until the implementations land. Clients that enumerated and called these tools will see them stop appearing in `tools/list`; calls to them would have failed previously anyway.

Fixed in:

API v1.22.3

Components:

MCP `tools/list`

Usage badge now shown on each project in Dashboard

Each project card in the dashboard now displays a usage badge showing this month's API-call count, so users can see at a glance which projects are active without opening each one. No customer action required.

Fixed in:

Web v1.23.4

Components:

/dashboard/projects

Internal: per-project FinOps surface hardening — no customer-visible change

Internal cleanup across the per-project FinOps surface (project budgets, per-project usage, project-bound API keys). No customer-visible API contract change. Bundled here for SemVer traceability.

Fixed in:

API v1.22.5

Components:

per-project FinOps internals

Internal: dashboard FinOps audit — no customer-visible change

Internal-only audit pass on the dashboard FinOps surface. No customer-visible UI or behavioural change. Bundled here for SemVer traceability.

Fixed in:

Web v1.23.3

Components:

dashboard FinOps internals