Skip to main content
Connect your client

Changelog

Releases, incidents, security advisories, and compliance notices for the gotcontext.ai platform, covering the public API, Web Dashboard, MCP Gateway, and SDKs. Every entry carries severity, affected components, and a clear customer-action flag.

Filters

Surface:
Type:

Latest releases

APIpermalink
Bug fixMediumWebAPIAction required: No

Delete projects with account usage history

Projects can be deleted when their only retained dependency is usage history. The usage records stay available at the account level.

Webpermalink
Bug fixMediumWebAction required: No

Choose all supported permissions for scoped API keys

API Keys in Settings now lists all supported permissions, including Plans, so you can grant only the access your integration needs.

Webpermalink
Bug fixMediumWebAPIAction required: No

Compare original text in Knowledge version history

Knowledge version comparisons show the exact wording changes when the full original text is available for both versions.

APIpermalink
Bug fixMediumWebAPIAction required: No

Read saved text on Knowledge item pages

Open a Knowledge item from Chat or the Knowledge list to read its saved text. Version comparisons show changes when a prior version exists.

APIpermalink
FeatureLowWebAPIAction required: No

Open attached Knowledge sources from saved Chat

Saved replies link to the Knowledge items you attached from the current project. Each link returns to the source after reload.

Webpermalink
Bug fixMediumWebAction required: No

Keep source details when attaching Knowledge in Chat

Chat includes the original wording from an attached Knowledge source when the index retains it, so details omitted from its summary can inform the answer.

Webpermalink
Bug fixLowWebAction required: No

Return to Chat and Knowledge after signing in

Signing in from a saved conversation, a news chat link, or a Knowledge item opens the intended page in the original language.

APIpermalink
Bug fixMediumAPIWebAction required: No

Open the first project while signup is syncing

A newly signed-in account can open its project list and finish onboarding while its signup notification is still in transit.

APIpermalink
FeatureLowAPIWebAction required: No

Keep search matches with fewer repeated paths

Preserve Details groups adjacent search results under one file path and keeps each match and line number intact.

Webpermalink
Bug fixMediumWebAction required: No

Free accounts can finish onboarding with their default project

New Free accounts can create their onboarding key, try compression, and open their dashboard using the included project.

Webpermalink
Bug fixLowWebAction required: No

Improve light-mode contrast in Billing and Knowledge

Billing payment buttons and Knowledge source titles use text colors that remain legible in both themes.

Webpermalink
Bug fixLowWebAction required: No

Show newly approved plan versions in Workspace

Version history refreshes when you merge a proposal and shows the new version with its author and proposal.

Webpermalink
Bug fixLowWebAction required: No

Close the mobile menu with the keyboard

Escape closes the menu and returns focus to its button. Tabbing past the menu dismisses it so the next focused control is visible.

Webpermalink
Bug fixLowWebAction required: No

Keep keyboard focus visible on public pages

The skip link appears above the site header. On phones, Quickstart code stays within its callout and the feedback button stays clear of focused controls.

Webpermalink
Bug fixLowWebAction required: No

Make homepage savings and approval labels easier to read

Compression savings and the Knowledge approval example use higher-contrast text in the light theme.

Webpermalink
Bug fixLowWebAction required: No

Improve contrast on public product pages

Comparison details, Quickstart examples, and other public page text stay readable in light and dark themes.

Webpermalink
Bug fixLowWebAction required: No

Keep Knowledge sources accessible on small screens

Knowledge sources use the available width on phones and tablets. Source titles remain readable and selectable, and keyboard navigation reaches the library before the add-source and search panels.

Webpermalink
Bug fixLowWebAction required: No

Update The Token Company comparison

The comparison now links to current plan, model and deployment information, and opens a runnable compression sample.

Show details ▾
  • Comparison and sample links keep the current language.
  • Comparison text, links, and actions meet contrast requirements in light and dark mode.
  • Each comparison source remains a named link when Chrome translates the page.
APIpermalink
Bug fixLowAPIWebAction required: No

Preserve details in the homepage compression demo

Preserve details (the detailed API preset) folds recognized log and paragraph repeats when the result is reversible and saves tokens. Otherwise the demo shows the original and reports zero tokens saved.

Webpermalink
Bug fixLowWebAction required: No

Browse Agent Context in French

The Agent Context directory and framework pages display French instructions. Framework, sign-up, and pricing links keep you in French.

Webpermalink
Bug fixLowWebAction required: No

Keep framework lookup results visible with browser translation

Public framework lookups display the result and source link when the browser translates the page while the search is loading.

Webpermalink
Bug fixLowWebAPIAction required: No

Check queued Knowledge file uploads

Knowledge shows when a file has been received and is waiting for indexing. After automatic checks pause, you can check the same upload again. The filename is the default source title.

Webpermalink
Bug fixLowWebAction required: No

Retry failed file indexing from the timeline

When a file has a failed indexing status, its timeline can retry indexing the existing source. Confirm the retry and check the updated status in the same timeline.

APIpermalink
ImprovementLowAPIWebAction required: No

Compress repeated paragraphs in the homepage demo

Balanced and Detailed replace exact repeats with references to earlier paragraphs when that saves tokens. When there are no savings, the demo shows the original and says why. You can compare changed output with the source for details it may omit.

Webpermalink
Bug fixLowWebAction required: No

Keep Knowledge Hub on your active project

Switching projects in the sidebar now updates the Knowledge source form, list, and search together. The All projects filter remains available inside Knowledge Hub.

Webpermalink
Bug fixLowWebAction required: No

Find the Call ID in dashboard logs

The Calls table and details label the saved call identifier as Call ID. Use it to find the same call in the API or share its dashboard link.

Webpermalink
Bug fixLowWebAction required: No

Reopen call details from a dashboard link

Opening or refreshing a Calls link loads the linked call details, even when the call is outside the current list.

Webpermalink
Bug fixLowAPIWebAction required: No

View Batch Queue jobs on the Pro plan

Pro subscribers can view recent batch jobs and monitor progress in the dashboard. The queue keeps the original text when compression would increase its token count.

APIpermalink
Bug fixLowAPIWebAction required: No

Open the source page from a Context Hub excerpt

React and LangChain documentation previews retain the publisher page link when the excerpt comes from newly indexed documentation. Existing excerpts can still link to the documentation collection.

Webpermalink
Bug fixLowWebAction required: No

See measured input savings in the calculator

The calculator shows token savings for any sample that compresses and explains the assumed input price. It is available in English and French, with a readable heading in light mode.

APIpermalink
Bug fixLowAPIWebAction required: No

Keep incident details in the compression demo

For recognized logs, the demo keeps error, warning and summary lines in order. It folds repeated INFO lines when doing so saves tokens.

Webpermalink
ImprovementLowWebAction required: No

See your monthly price before opening checkout

Billing shows the selected Pro, Team or Business monthly price before sending you to Polar.

Webpermalink
Bug fixLowWebAction required: No

Headroom comparison includes its MCP server and persistent memory

See how Headroom’s self-hosted MCP setup and user memory compare with GotContext’s hosted gateway and Knowledge Hub.

Webpermalink
ImprovementLowWebAction required: No

Compare compressed output with the original on the homepage

Choose how much detail to request and switch to the exact text you submitted whenever you need to check a detail.

Webpermalink
Bug fixLowWebAction required: No

Start a monthly Business subscription from the homepage

The Business button opens signup for the $199 monthly plan in English and French.

Show details ▾
  • The homepage and Billing show the included limit of 500,000 compressions per month.
Webpermalink
ImprovementLowWebAction required: No

Search framework documentation before signing up

Try a search on any Agent Context framework page to read excerpts from its public documentation and follow the original sources.

Show details ▾
  • Search is available in English and French. The original documentation remains in its source language.
Webpermalink
Bug fixLowWebAction required: No

Business pricing clarifies higher-volume quotes

Business includes 500,000 pooled compressions per month at the published price. If you need more, the pricing calculator directs you to sales for a quote.

Show details ▾
  • The plan comparison, savings examples and FAQ use the same higher-volume terms in English and French.
Webpermalink
Bug fixLowWebAction required: No

Read the full pricing page in French

The French pricing page now includes French plan comparisons, FAQ answers, savings estimates, procurement information, and contact form instructions.

Show details ▾
  • The estimator and comparison tables include French control labels for screen readers.
  • The contact form displays French validation and confirmation messages.
Webpermalink
ImprovementLowWebAction required: No

Try compression before signup and take your selected plan into billing

Run the homepage demo on your own text, see the token counts, and compare actual plan prices before estimating savings.

Show details ▾
  • The homepage opens with an editable demo. Run it to see the compressed output and the token counts from that request.
  • Pricing puts available plans, prices and purchase actions before the calculator and detailed comparison.
  • Billing shows the plan you chose through sign-in or signup. The French purchase flow includes localized trial terms and the monthly renewal price.
  • Quickstart opens the API Keys tab. The public dashboard guide, Trust sample, and benchmark run links also work on phones.
  • Pricing explains what a hosted plan upgrade adds and links to the MCP setup guide in your language.
  • Checkout now returns to Billing, where you can see when your selected plan takes effect.
  • Dashboard checkout shows the monthly offer before you pay. If checkout or the billing portal is unavailable, you can retry from your account.
APIpermalink
ImprovementLowAPIAction required: No

Faster documentation imports and corrected source links

Importing documentation that is published as many small pages is faster, and source links with an explicit default port open correctly.

Show details ▾
  • Documentation indexes are fetched several pages at a time, in the same order as before.
  • Source links no longer keep a default port that made the secure link fail.
  • Relevance calibration for large Knowledge projects reads far fewer rows.
Showing 40 of 451 releases

Security advisories · incidents · compliance history

Webpermalink
Security advisoryLowWebAction required: No

Artifact previews no longer load remote images

Previewing generated HTML in chat no longer fetches images from other sites, and the preview panel is easier to use from the keyboard.

Show details ▾
  • HTML previews show embedded images only; images hosted elsewhere are not requested.
  • Escape closes the preview panel and focus returns to where you were.
Webpermalink
Compliance noticeLowWebAction required: No

Terms and Privacy Policy now describe Chat web search

The Terms of Service, Privacy Policy and Sub-processors page now explain what Chat sends to search engines and websites when web research is on.

Show details ▾
  • A short search query from your question goes to public search engines; links you ask to open are requested from those sites.
  • Your account details, IP address and attached documents are not sent.
  • The Chat tools menu now says this next to the web research setting, where you can turn it off.
API v1.71.13 / Web v1.50.22permalink
Security advisoryMediumAPIWebAction required: No

CRM PQL scans default to preview and use server-configured webhooks

Scanning PQL triggers previews qualified accounts without mutating CRM records or dispatching alerts until explicitly applied.

Show details ▾
  • PQL scans run in read-only preview by default with a separate Apply scan results action.
  • Caller-supplied webhook destinations and customer quota-webhook fallbacks are not used for PQL alerts.
API v1.71.6permalink
Security advisoryHighAPIMCP GatewayAction required: No

HTTP dependencies receive security updates

The API and MCP gateway use updated aiohttp components addressing published HTTP request-handling and secure-cookie advisories.

Show details ▾
  • The API requires aiohttp 3.14.4 or later in the compatible 3.x series.
  • Updated releases include aiohttp 3.14.5 and yarl 1.25.1.
Web v1.45.0permalink
Security advisoryInformationalAPIWebAction required: No

Browser enrollment now has an explicit deny decision

You can deny a browser enrollment request, and a denied device code cannot later grant account access.

Show details ▾
  • The activation page confirms or denies the pending device request.
  • A denial is terminal for that device code; it does not create a credential.
  • Confirmation is bound to the signed-in account identity.
1.66.71permalink
Security advisoryMediumAPIMCP GatewayAction required: No

Free-tier compression quota now fails closed when usage cannot be measured

If Redis and the Postgres fallback both cannot determine monthly usage, free-tier compress and MCP calls return a retryable error instead of bypassing the monthly limit.

Show details ▾
  • Redis down + Postgres fallback exhausted on free plan -> HTTP 503 quota_unavailable
  • Postgres fallback uses the same billable UsageEvent filters as usage cache rebuild
  • Paid tiers remain fail-open when usage is unmeasured
1.66.70permalink
Security advisoryMediumAPIMCP GatewayAction required: No

API key auth refuses when Postgres cannot confirm enforcement state

If Redis authenticates a key but Postgres cannot confirm project binding or allowlists, the request is rejected (401 when the row is gone, 503 on DB outage) instead of serving possibly stale Redis enforcement fields.

Show details ▾
  • Deleted/revoked key with stale Redis blob -> HTTP 401
  • Postgres outage during enforcement lookup -> HTTP 503 auth_state_unavailable
  • Successful DB lookup still overwrites Redis-seeded state from Postgres
1.66.69permalink
Security advisoryHighAPIAction required: No

Polar subscription webhook processing failures now return 503

If a subscription lifecycle handler fails after signature verify, the webhook returns 503 so Svix retries instead of acknowledging with 200 and risking a dropped grant or downgrade.

Show details ▾
  • Lifecycle handler exceptions -> HTTP 503 Webhook processing failed
  • Unreadable discriminator after verify -> HTTP 503
  • Named-but-unhandled events still return 200
1.66.68permalink
Security advisoryMediumAPIAction required: No

Resend inbound webhooks now deduplicate Svix replays

Replayed Resend deliveries with the same svix-id short-circuit with 200 before re-running bounce/complaint suppression. Dedup failures return 503 so retries stay safe.

Show details ▾
  • dedup_inbound_event(provider=resend) after signature verify
  • Replay -> 200 ok without re-applying opt-out
  • Dedup DB error -> 503 dedup unavailable
1.66.67permalink
Security advisoryHighAPIAction required: No

Resend bounce suppression failures now return 503 (fail closed)

If bounce/complaint opt-out handling fails after signature verify, the webhook returns 503 so Resend retries instead of acknowledging with 200 and permanently skipping email suppression.

Show details ▾
  • Suppression-handler exceptions -> HTTP 503 suppression unavailable
  • Soft/ignored/success paths still return 200
  • Misconfig and bad signatures remain 400
1.66.66permalink
Security advisoryHighAPIAction required: No

Inbound webhook dedup failures now return 503 instead of re-processing

If the dedup ledger is unavailable after signature verification, Clerk, Polar, and GitHub webhooks return 503 and skip handlers. This prevents non-idempotent side effects from running twice when Svix retries, at the cost of a temporary delay until dedup recovers (GitHub needs a manual redeliver).

Show details ▾
  • Dedup DB errors fail closed with 503; handlers are not dispatched
  • Rollback after a dedup error is best-effort and cannot demote the 503 to a 500
  • GitHub log/detail includes the redeliver phrase for operator recovery
1.66.64permalink
Security advisoryHighAPIAction required: No

Offline migration scripts now include the RLS safety sweep

When you generate SQL with alembic upgrade --sql, the output now includes the same post-migration Row Level Security sweep that runs on every Fly deploy. Previously, applying offline-generated scripts could leave new public tables without RLS enabled.

Show details ▾
  • Offline Alembic runs on Postgres URLs emit lock_timeout + ENABLE ROW LEVEL SECURITY sweep SQL after migrations
  • Mirrors the every-deploy migration hook so air-gapped or reviewed SQL paths cannot skip tenant isolation hardening
1.66.20permalink
Security advisoryMediumAPIAction required: No

Accept-grant elevates to system before RLS-sensitive write

Preparing for RLS enablement: recording share acceptance now sets app.role=system for the accept UPDATE so it still works once policies are enforced.

Show details ▾
  • accept_grant elevates app.role mid-transaction before stamping accepted_at (0149 requires a service write, not a grantee UPDATE).
  • Does not flip RLS_GUC_ENABLED or change the production DB role; those remain CEO-gated (#514).
1.64.1permalink
Security advisoryMediumAPIAction required: No

Chat completions now has its own 60/min ceiling

POST /v1/chat/completions forwards each call to an upstream model provider on your own stored API key, so you are billed directly for it. It previously inherited the general per-plan request limit, which on the top tier allowed 500 calls a minute. It is now capped at 60 a minute -- one per second -- so a runaway loop or a leaked key costs far less before you notice. Normal interactive use is nowhere near this.

Show details ▾
  • The new ceiling applies only to POST /v1/chat/completions. Compression, knowledge and every other endpoint keep their existing per-plan limits.
  • Per-path ceilings can now only lower a limit, never raise one. Previously a path entry replaced the plan value outright, so an entry above your plan tier would have increased your allowance instead of capping it.
  • Responses continue to carry x-ratelimit-limit, x-ratelimit-remaining and x-ratelimit-reset, so a client can see the ceiling it is working against.
1.64.1permalink
Security advisoryMediumAPIAction required: No

Webhook signing secrets are now encrypted at rest

The secret your endpoint uses to verify the signature on our webhook deliveries is now encrypted in our database rather than stored as readable text. Nothing changes for you: the secret value itself is unchanged, so your existing verification keeps working and no reconfiguration is needed.

Show details ▾
  • New webhook secrets are encrypted before they are stored, using the same versioned key scheme already used for provider credentials.
  • The secret is still shown to you once, in full, when you create the webhook. It stays redacted everywhere else.
  • Delivery signatures are unchanged, so endpoints that already verify our signature continue to verify successfully.
1.62.0permalink
Security advisoryMediumAPIAction required: No

Signed A2A Agent Card for verifiable identity

Other AI agents that discover gotcontext through the Agent2Agent (A2A) protocol can now cryptographically verify that the Agent Card really came from gotcontext, before they trust or delegate to it. Our public Agent Card now carries a JWS signature that a standard A2A client can check against our published key.

Show details ▾
  • The Agent Card at the well-known A2A discovery path now includes a JWS signature (Ed25519) over the RFC 8785 canonical form of the card.
  • Verifiers can fetch the verification key from our published key set and reject a forged or tampered card.
  • The signature is additive and backward compatible: existing clients that ignore it keep working; self-hosted deployments without a signing key serve an unsigned card.
API v1.58.7permalink
Security advisoryHighMCP GatewayAction required: No

Restricted server-side-path tools on the hosted MCP service

A few Pro-tier MCP tools accept a server-side file path, which is only meaningful in a self-hosted deployment. On the hosted service they are now correctly hidden and blocked, since they do not apply there. Self-hosted deployments are unaffected and keep full access.

Show details ▾
  • Tools that take a server-side path are no longer discoverable or callable on the hosted MCP endpoint.
  • Added an automated release check so any future tool of this kind is caught before it ships.
  • Self-hosted operators keep these tools in full.
API v1.58.7permalink
Security advisoryHighAPIAction required: No

Upgraded a core web framework to clear published CVEs

Upgraded the API's underlying web framework to a new major version, clearing four high-severity published vulnerabilities, including authentication-bypass and request-forgery classes. No action is required on your side.

Show details ▾
  • Core web framework upgraded to its latest major release.
  • Four high-severity published vulnerabilities resolved.
  • No changes to your integration or request format.
API v1.58.7permalink
Security advisoryMediumAPIMCP GatewayAction required: No

Knowledge Base private items and sharing are now enforced

Items marked private are visible only to the API key that created them. Per-key sharing allowlists are enforced on every Knowledge Base operation: query, read, edit, delete, and diff, across both the MCP and REST surfaces.

Show details ▾
  • Private Knowledge Base items are accessible only to the API key that created them.
  • Sharing allowlists are checked on every operation (query, read, edit, delete, diff), not just on query.
  • Enforcement is consistent across the MCP gateway and the REST API.
Web v1.44.15permalink
Security advisoryMediumWebAction required: No

Web dependency security updates

Several transitive browser and server-runtime dependencies were updated to patched versions. No customer action is required.

Show details ▾
  • Updated affected transitive packages used by the web runtime and build toolchain.
  • Kept the update within compatible version ranges to avoid changing application behavior.
  • Hosted customers receive the fix automatically.
API v1.53.0permalink
Security advisoryHighAPIMCP GatewayAction required: No

Security and reliability fixes: filesystem filter, billing portal, cron cost, Docker pinning

Seven fixes from a proactive internal audit. The MCP search_code tool is now properly filtered in SaaS mode. Per-API-key tool restrictions now apply at discovery (tools/list) as well as dispatch. The billing portal returns a clear error instead of a misleading upgrade prompt when the database is briefly unavailable. GitHub Actions cron schedules were cut to reduce infrastructure cost. Docker base images are now digest-pinned for supply-chain stability. Hosted customers are auto-upgraded.

Show details ▾
  • The MCP search_code tool is now correctly restricted when running in hosted mode, preventing server-path access.
  • Per-API-key tool allowlists now filter tools/list (discovery) and tools/call (dispatch) consistently.
  • The billing portal returns a 503 with a clear message instead of a 404 "upgrade first" when the database is briefly unavailable.
  • The compression engine now rejects non-finite embeddings at ingest, preventing silent result corruption downstream.
  • Wire-shape contracts for the forum and social surfaces are now locked against future renames.
  • GitHub Actions cron schedules reduced by roughly 59% to cut infrastructure cost.
  • Docker base images are now digest-pinned so base-image changes arrive as reviewable pull requests.
API v1.52.3permalink
Security advisoryHighAPIMCP GatewayAction required: No

Security hardening: account deletion, billing, and webhook fixes

Five fixes from a proactive internal security audit. API keys are now revoked the moment their owner account is deleted; referral credits can only be earned once per referred user; the MCP proxy tool now blocks requests to internal network addresses; key revocation is reliable under concurrent requests; and usage-alert delivery is durable across server restarts. Hosted customers are auto-upgraded. No action required.

Show details ▾
  • Deleting an account now revokes all of its API keys before the account is removed.
  • Referral credit can only be earned once per referred user.
  • The MCP proxy tool no longer forwards requests to private or internal network addresses.
  • Key revocation is now reliable even under concurrent requests, so a revoked key is consistently rejected.
  • Usage-alert delivery is durable and is no longer dropped when a server instance restarts.
API v1.50.23permalink
Security advisoryMediumAPIAction required: No

Forum security: user silencing, safer username conflicts, link sanitization

Three forum hardening fixes: moderators can silence and unsilence users; username conflicts no longer reveal whether a name is already taken by another account; and unsafe links are stripped from comment content.

Show details ▾
  • Moderators can silence a user so they can no longer post comments, and reverse it.
  • Username conflicts are reported without revealing whether the name belongs to another account.
  • Unsafe links are stripped from comment content.
API v1.50.22permalink
Security advisoryMediumAPIAction required: No

Comment sanitizer hardened

The comment sanitizer was rebuilt to strip all HTML tags directly instead of relying on allowlisting, closing a class of HTML-entity edge cases and reducing the dependency surface.

Show details ▾
  • All HTML/XML tags are now stripped from comments; no HTML attributes survive.
  • Plain text and Markdown syntax is preserved.
API v1.50.16permalink
Security advisoryMediumAPIAction required: No

Payment-token audience enforcement

Skyfire payment tokens are now validated against the expected audience, so a token issued for a different service cannot be reused against this API. Agent payments remain off by default.

Show details ▾
  • Payment tokens whose audience does not match this service are rejected.
  • Operators enabling agent payments configure the expected audience as part of setup.
API v1.50.15permalink
Security advisoryHighAPIAction required: No

Secret encryption now fails closed in production

If the encryption key is not configured in production, secret-storage operations now fail safely instead of proceeding, preventing secrets from ever being written unencrypted. Local development behavior is unchanged.

Show details ▾
  • In production, a missing encryption key blocks the operation rather than storing unencrypted data.
  • Local development is unaffected for convenience.
  • Operators who rely on encryption should confirm the key is configured before deploying.
API v1.50.5 / Web v1.42.2permalink
Security advisoryLowAPIWebAction required: No

Hardened HTTP security-header baseline across the API and dashboard

Every API and dashboard response now carries a stronger set of browser security headers, defense-in-depth against clickjacking, MIME-type confusion, and referrer leakage. No customer action is required.

Show details ▾
  • Added X-Content-Type-Options (nosniff), X-Frame-Options (clickjacking protection), a stricter Referrer-Policy, and a Permissions-Policy denying unused device features.
  • Headers are only set when not already present, so nothing a route configures itself is overwritten.
  • A full Content-Security-Policy is being rolled out separately in report-only mode first, to avoid breaking sign-in or analytics.
  • No customer action is required.
API v1.50.4permalink
Security advisoryMediumAPIAction required: No

Per-plan request body-size limits now enforced reliably, including for streamed requests

Request body-size limits are now enforced reliably, including for streamed requests. Over-limit requests are rejected before any route handler processes the body.

Show details ▾
  • Identified through a proactive internal security audit and fixed server-side.
  • All upload styles (including streamed requests) are now subject to the same per-plan size limits.
  • Over-limit requests receive a deterministic 413 response before any route handler processes the body.
  • Within-limit uploads are unaffected.
  • No customer action is required.
Web v1.42.1permalink
Security advisoryMediumWebAction required: No

Dashboard notification rendering hardened against HTML injection

Notification links are now strictly escaped and URL-validated before rendering in the dashboard.

Show details ▾
  • Found through a proactive internal security audit; fixed in the rendering layer.
  • Notification links are now validated as http(s) URLs; invalid URLs render as plain text with no anchor element.
  • No customer action is required.
API v1.50.3permalink
Security advisoryHighAPIMCP GatewayAction required: No

Knowledge-base and tool access restrictions now fail closed on a database error

A database error during API key resolution could reset a key's knowledge-base and tool allowlists to unrestricted. Those restrictions now hold their seeded values when a database error occurs.

Show details ▾
  • Found through a proactive internal security audit as a follow-on to the v1.50.0 hardening.
  • Per-key knowledge-base and tool allowlists are now preserved correctly when a database error occurs during key resolution, rather than resetting to unrestricted.
  • Keys with no allowlist configured remain unrestricted. Existing behaviour is unchanged.
  • No customer action is required.
API v1.50.2permalink
Security advisoryMediumAPIAction required: No

GitHub tokens and webhook secrets now encrypted at rest

GitHub personal access tokens and webhook secrets stored for the GitHub integration were previously held as plaintext in the database. They are now encrypted with a server-side key; existing values are transparently upgraded.

Show details ▾
  • Found through a proactive internal security audit and fixed server-side.
  • Integration secrets are now stored as encrypted ciphertext; a database read or backup exposes ciphertext only.
  • Existing plaintext values were re-encrypted during the deployment. No manual step required.
  • Secret encryption now fails closed in production: if the encryption key is not configured, secret-storage operations fail safely instead of proceeding unencrypted.
  • No customer action is required.
API v1.50.1permalink
Security advisoryMediumAPIAction required: No

Outbound webhook URLs validated against internal-network access

User-configured webhook delivery URLs were not validated against internal network ranges, allowing delivery to private or cloud-metadata addresses. Webhook URLs are now checked at creation and re-validated immediately before each delivery.

Show details ▾
  • Found through a proactive internal security audit and fixed server-side.
  • Webhook creation now rejects URLs that resolve to private, loopback, link-local, or cloud-metadata addresses.
  • The delivery path re-validates the target address immediately before each outbound request.
  • HTTP redirects are no longer followed during delivery.
  • No customer action is required.
API v1.50.0permalink
Security advisoryHighAPIMCP GatewayAction required: No

Scoped API keys now strictly enforced; destructive-action confirmation locked to dashboard sign-in

Scoped API keys were accepted by the server but their scope constraints were not persisted or enforced. Every scoped key silently ran with full access. Scope restrictions are now applied end-to-end. Separately, the confirmation gate for destructive key operations now requires an active dashboard session.

Show details ▾
  • Found through a proactive internal security audit and fixed server-side.
  • Scope restrictions are now stored and enforced on every request. Previously they were accepted at creation but not applied.
  • Existing keys without explicit scopes are treated as legacy full-access keys. No behaviour change for current users.
  • A temporary backend outage during key resolution no longer causes a scoped key to fall back to full access.
  • The confirmation gate for destructive key operations now requires an active dashboard session.
  • No customer action is required.
API v1.45.xpermalink
Security advisoryMediumAPIAction required: No

Analytics CSV export hardened against spreadsheet formula injection

CSV cells beginning with formula-trigger characters (=, +, -, @) are now neutralized so exported files cannot execute formulas when opened in Excel or Google Sheets.

Show details ▾
  • Identified through a proactive internal security review and fixed server-side.
  • Cells that start with =, +, -, or @ are prefixed with a tab character before export, following standard CSV injection mitigation practice.
  • Numeric and date values are unaffected.
  • No customer action is required.
API v1.35.0permalink
Security advisoryHighAPIMCP GatewayAction required: No

Live key revocation across all API servers + outbound URL hardening

Revoked gc_ API keys are now invalidated promptly and reliably across all API servers. Separately, the document-fetch and Knowledge Hub ingest paths now block requests to private or internal network addresses across all known address encoding variants.

Fixed in:
API v1.35.0
Components:
API key lifecycle · MCP Gateway
Show details ▾
  • Revoked API keys are now invalidated promptly across all API servers. Revocation no longer requires waiting for a cache TTL to expire.
  • Server restarts no longer cause revocation events to be missed.
  • The document-fetch and Knowledge Hub ingest paths now block requests to private or internal network addresses.
  • Pairs with the v1.34.36 hotfix (cache-invalidation gap in the key confirmation flow) shipped the same day.
API v1.34.36permalink
Security advisoryHighAPIAction required: No

P0 hotfix: revoked confirm-tokens now invalidated promptly across all servers

A revoked key issued through the key-confirmation flow was not immediately invalidated in the shared cache, allowing it to continue authenticating on peer servers until the cache refreshed. The fix invalidates the cache immediately after revoking the key in the database.

Affected:
API v1.34.35
Fixed in:
API v1.34.36
Components:
API key lifecycle
Show details ▾
  • Cache invalidation is best-effort: a cache failure is logged and does not surface as an error to the caller.
Incident · resolved in API v1.23.12026-05-09 17:14 to 17:24 UTC (10 minutes)permalink
IncidentCriticalMCP GatewayAction required: No

MCP tools returned 500 for ~10 minutes

All MCP tool calls failed with HTTP 500 for approximately 10 minutes. No data was lost. Customers using MCP clients (Claude Code, Cursor, Codex CLI, Gemini CLI) saw tool calls fail and could retry after the window closed.

Affected:
API v1.22.4 to v1.23.0
Fixed in:
API v1.23.1
Components:
MCP Gateway · tools/call dispatch
Show details ▾
  • A routing change caused every tool call to reach a code path with a reference that had never existed. The defect was dormant in a prior release but only became reachable after the routing change landed.
  • Resolution: the broken reference was removed and deployed as API v1.23.1.
  • Hardening: automated checks were added to catch this entire class of defect before it ships.
Compliance notice · resolved in API v1.23.1permalink
Compliance noticeHighAPIAction required: No

Unsubscribe endpoint returned 401 for all requests

Between API v1.23.0 and v1.23.1, the `/v1/unsubscribe` endpoint (used for the CAN-SPAM/GDPR-required unsubscribe link in transactional emails) returned 401 Unauthorized for all requests. No unsubscribe records were lost. The endpoint returned a non-200 to clients, which retried or surfaced the error. No customer action required.

Affected:
API v1.23.0
Fixed in:
API v1.23.1
Components:
API · /v1/unsubscribe · transactional email footer
Show details ▾
  • The endpoint now correctly accepts unauthenticated requests as required for the unsubscribe use case.
  • No personal data was processed during the regression window. All requests during the window returned an explicit 401; retrying the unsubscribe link resolves the original opt-out.
Security advisory · resolved in API v1.22.6permalink
Security advisoryHighAPIMCP GatewayAction required: Yes

SSRF: outbound URL fetch paths now block requests to private and internal network addresses

Outbound URL fetches (used by webhook delivery, KB document ingestion, and a small number of MCP tools) could be tricked into reaching loopback or private addresses through address encoding techniques. The webhook/document-fetch paths now block requests to private or internal network addresses. Hosted customers received the fix automatically; self-hosted operators should upgrade to API ≥ v1.22.6.

Action required

Self-hosted operators: upgrade the API container to v1.22.6 or newer. No action required for customers on the hosted gotcontext.ai service.

Affected:
API ≤ v1.22.5
Fixed in:
API v1.22.6
CVE:
CVE pending assignment
CVSS:
7.5 (High), CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Components:
Webhook delivery · Knowledge Hub
Show details ▾
  • All outbound URL fetch paths now enforce private/internal network blocking at both validation time and connection time.
  • No active exploitation was observed in production traffic. The advisory is published preemptively.

Older releases are listed above on this page. Follow release announcements on GitHub for change notifications. Security advisories, incidents, and compliance notices are filed on this page; use the filters above to narrow by surface or type.

Citing a specific change? Use the permalink on each entry (/changelog#<entry-id>). To get notified when a security advisory or breaking change ships, subscribe via the Atom feed or create an account for email notifications.