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.
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
Projects can be deleted when their only retained dependency is usage history. The usage records stay available at the account level.
API Keys in Settings now lists all supported permissions, including Plans, so you can grant only the access your integration needs.
Knowledge version comparisons show the exact wording changes when the full original text is available for both versions.
Open a Knowledge item from Chat or the Knowledge list to read its saved text. Version comparisons show changes when a prior version exists.
Saved replies link to the Knowledge items you attached from the current project. Each link returns to the source after reload.
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.
Signing in from a saved conversation, a news chat link, or a Knowledge item opens the intended page in the original language.
A newly signed-in account can open its project list and finish onboarding while its signup notification is still in transit.
Preserve Details groups adjacent search results under one file path and keeps each match and line number intact.
New Free accounts can create their onboarding key, try compression, and open their dashboard using the included project.
Billing payment buttons and Knowledge source titles use text colors that remain legible in both themes.
Version history refreshes when you merge a proposal and shows the new version with its author and proposal.
Escape closes the menu and returns focus to its button. Tabbing past the menu dismisses it so the next focused control is visible.
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.
Compression savings and the Knowledge approval example use higher-contrast text in the light theme.
Comparison details, Quickstart examples, and other public page text stay readable in light and dark themes.
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.
The comparison now links to current plan, model and deployment information, and opens a runnable compression sample.
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.
The Agent Context directory and framework pages display French instructions. Framework, sign-up, and pricing links keep you in French.
Public framework lookups display the result and source link when the browser translates the page while the search is loading.
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.
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.
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.
Switching projects in the sidebar now updates the Knowledge source form, list, and search together. The All projects filter remains available inside Knowledge Hub.
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.
Opening or refreshing a Calls link loads the linked call details, even when the call is outside the current list.
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.
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.
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.
For recognized logs, the demo keeps error, warning and summary lines in order. It folds repeated INFO lines when doing so saves tokens.
Billing shows the selected Pro, Team or Business monthly price before sending you to Polar.
See how Headroom’s self-hosted MCP setup and user memory compare with GotContext’s hosted gateway and Knowledge Hub.
Choose how much detail to request and switch to the exact text you submitted whenever you need to check a detail.
The Business button opens signup for the $199 monthly plan in English and French.
Try a search on any Agent Context framework page to read excerpts from its public documentation and follow the original sources.
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.
The French pricing page now includes French plan comparisons, FAQ answers, savings estimates, procurement information, and contact form instructions.
Run the homepage demo on your own text, see the token counts, and compare actual plan prices before estimating savings.
Importing documentation that is published as many small pages is faster, and source links with an explicit default port open correctly.
Previewing generated HTML in chat no longer fetches images from other sites, and the preview panel is easier to use from the keyboard.
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.
Scanning PQL triggers previews qualified accounts without mutating CRM records or dispatching alerts until explicitly applied.
The API and MCP gateway use updated aiohttp components addressing published HTTP request-handling and secure-cookie advisories.
You can deny a browser enrollment request, and a denied device code cannot later grant account access.
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.
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.
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.
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.
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.
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).
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.
Preparing for RLS enablement: recording share acceptance now sets app.role=system for the accept UPDATE so it still works once policies are enforced.
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.
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.
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.
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.
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.
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.
Several transitive browser and server-runtime dependencies were updated to patched versions. No customer action is required.
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.
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.
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.
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.
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.
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.
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.
Request body-size limits are now enforced reliably, including for streamed requests. Over-limit requests are rejected before any route handler processes the body.
Notification links are now strictly escaped and URL-validated before rendering in the dashboard.
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.
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.
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.
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.
CSV cells beginning with formula-trigger characters (=, +, -, @) are now neutralized so exported files cannot execute formulas when opened in Excel or Google Sheets.
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.
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.
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.
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.
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.