Changelog

AI agents can create and edit your workflows

Two new MCP tools let an AI author and edit saved workflows for you. It can create a new named workflow or save an edit to an existing one as a new version (edits never overwrite an old version, so run history stays honest). These only touch your saved graphs and spend nothing. An agent can only write workflows in the project its key is scoped to, and the tools tell it the limits up front: up to 100 nodes can be saved, but a single run submits at most 10 steps. Available on Pro and above.

AI agents can run your saved workflows

A new MCP tool lets an AI run one of your saved workflows and get a run id back right away (you can then check on it with the run-status tool). This one spends against your provider balance, so it passes the same safety checks as running a workflow from the dashboard: it is capped at 10 steps per run, multi-step runs stay off until enabled, an agent can only run a workflow in the project its key is scoped to, and there is a strict per-key rate limit that fails safe if it cannot be checked. Available on Pro and above.

AI agents can check the status of runs they submitted

Two new read-only MCP tools let an AI check on runs. It can look up one run (its status and each step’s output) or list your recent runs and what each cost. They only read; an agent only ever sees runs you submitted, and a project-scoped key only sees that project’s runs. Available on Pro and above.

AI agents can list and open your saved workflows

Two new read-only MCP tools let an AI agent see the workflows you have saved and open one to inspect its steps, without you having to paste them in. They only read; they never run a workflow or spend anything, and an agent only ever sees workflows in the project its key is scoped to. Available on Pro and above.

Answers are formatted instead of showing raw markdown

Models write in markdown, and the transcript was showing it literally: headings as hash signs, emphasis as asterisks, tables as rows of pipes. Only code blocks were formatted. Answers now render properly, including headings, lists, tables, quotes, links and inline code. Code blocks keep their Copy and Preview buttons, and your own messages are still shown exactly as you typed them.

Chat now remembers what you already said

Every message was previously sent to the model on its own, so it had no idea what had been discussed a moment earlier and you had to restate context in each question. A conversation now carries its earlier turns, and follow-up questions work the way you would expect. Older turns fall out of the window once a conversation gets long; they are left out rather than summarised, so nothing is invented.

Chat history is saved to your account instead of one browser

Conversations were kept only in the browser you happened to be using. A different machine showed nothing, and clearing site data destroyed them with no way to get them back. They are now stored on your account, so the same history follows you between devices and survives a cleared cache. Anything already in your current browser still appears until it has been replaced by newly saved conversations.

You can paste an image straight into the chat composer

Attaching a screenshot previously meant saving it to a file first, or dragging it in. Pasting now attaches it directly, which is how most people expect to share one. Pasting ordinary text is unchanged.

Sending to a paid OpenRouter model no longer fails when an assistant is attached

Chat has two ways to send a turn: directly, or delegated to a saved assistant. Only the direct one had been taught that OpenRouter reports its own per-call cost, so a delegated turn on a paid OpenRouter model was refused with a message about the spend ceiling being unable to bound it — on a build whose notes said those models worked. Both statements were true, of different paths. They now apply one rule, and a test fails the build if they ever disagree again.

The chat Canvas budget panel now shows your real quota

The Budget panel inside chat displayed a fixed usage bar under a heading that said it was live cost tracking. The figures were the same for every account and every project and were not read from anywhere. It now shows your actual usage for the billing period, and says plainly when that figure cannot be read rather than substituting a number.

Chat offers every model your OpenRouter key can reach

The model picker only listed free OpenRouter models, because the API refused any model missing from our own pricing catalogue and the picker narrowed itself to match. OpenRouter reports what each call actually cost, so that catalogue was never the source of truth there. Paid models now appear and work, and the savings receipt still uses the real reported cost rather than an estimate.

Chat no longer requires you to attach context first

Chat used to refuse to send anything until you attached context to compress, so typing a plain question got you an error instead of an answer. Context is optional now: ask whatever you like, and attach source material when you actually have some. A question with no context skips the compressor entirely and goes straight to your model, so it is as fast as any other chat.

You can now find the page where you add a provider key

Adding your own OpenRouter, Anthropic or OpenAI key is what makes Chat work, and the page for it had no link anywhere in the product: not in the sidebar, not on the Settings page, and not in Chat itself, whose own note said to add a key in Settings without linking there. The only way in was typing the address by hand. It now has a sidebar entry under Workspace, an entry in the mobile menu, and a direct link from Chat.

The homepage now opens on the compression itself

The homepage opens with a live WebGL field of tokens that collapses as you scroll: a loose cloud ("You send the model everything") compresses into a dense core ("We compress it. Same meaning. A fraction of the tokens.") and lands on the result. It is the product shown rather than described. On phones, and for anyone who has asked their system for reduced motion or is on a data saver, the page shows a still frame instead, so nothing heavy loads.

Homepage rebuilt as one story instead of two

The homepage had been running two full landing pages back to back: you reached a "Ready to cut your token bill?" closing call-to-action about a third of the way down, and then a second, older pitch started over and repeated the same product story. The page was 19,075px tall on desktop and just under 36 phone screens on mobile. It is now a single narrative that says each thing once, roughly a third shorter, with one closing call-to-action at the end. Every section that carried something unique is still there: the live playground, the code-compression benchmarks, the measurement methodology, the setup command, and pricing.

Live compression stat on the homepage, simplified pricing layout

The homepage hero now shows a live, real-time average savings figure pulled from production traffic instead of a static number. The pricing page is reorganized around Free, Pro, and Business as the three primary plans plus a distinct Enterprise contact column; the Team plan is unchanged and still purchasable, now reachable from a "Need pooled seats for a team?" expandable section.

Chat landing screen decluttered

The Chat landing screen crammed a lot on-screen at once: a long model description overlapping other text, an Export button with nothing to export yet, a permanent disclaimer paragraph, and four large description cards. All four are cleaned up so the composer is the clear focus, matching the density of other modern chat UIs.

Knowledge Agents tab now matches the Sources tab visually

The Agents tab under Knowledge (plan proposals, delegated tasks, A2A peers, MCP clients, MCP activity) was missing the card elevation and depth that the rest of the dashboard has, because a shared style layer wasn’t being loaded on that page. Panels now render with the same borders and shadows as everywhere else.

Knowledge Hub visual polish

The Knowledge dashboard’s stat cards, primary action buttons, and file-upload drop zone now carry more depth and clarity, matching the rest of the redesigned dashboard shell.

Community Feed Ecosystem Taxonomy & Responsive Hardening

The community feed now supports expanded ecosystem filters (Agents, Skills, Ideas), restores the saved-bookmarks filter on the backend router, surfaces top MCP skills and submission CTAs in the rail, and prevents iOS Safari input zooming.

Dashboard Responsive & iOS Accessibility Hardening

Authenticated dashboard chrome and home widgets now respect iOS safe areas, keep menus scrollable inside the viewport, and meet WCAG 2.2 AA contrast and focus targets on phone and tablet.

Mobile navigation menu provides full-screen coverage with seamless scrolling

The mobile navigation drawer now covers the full viewport with an opaque backdrop and locks background scroll so underlying page elements do not bleed through.

Top navigation buttons and profile avatars no longer overlap the mobile menu

Desktop navigation actions and signed-in account buttons now cleanly collapse on smaller screens and tablets without colliding with the menu button.

Marketing pages work better on tablets and iPhones

Navigation now fits tablet screens, menus can scroll on smaller phones, and browser controls and safe areas no longer cover important page controls.

Accessibility sweep across the public site, and the blog RSS feed now exists

Menus, buttons and links across the marketing site are now easier to hit on a phone, low-contrast text has been corrected, and keyboard users can reach content they previously could not. The blog RSS feed the site advertised is live.

Find a past chat, and reach your connectors from Chat

The conversation list in Chat now has a search box and groups your chats by when you last used them, so a long history stays navigable.

Chat is now a full-screen workspace, and you can send messages on a phone again

Chat opens as its own full-width workspace instead of a panel inside the dashboard, and the message box no longer collapses on small screens - the Send button was previously off the edge of the screen on a phone.

A 30-day savings trend on your dashboard home

Home now shows how many tokens you saved over the last 30 days as a chart, in the space that previously repeated links already in the sidebar.

Usage details from the sidebar, and a tidier header

The plan card at the bottom of the dashboard sidebar is now clickable and opens your usage for the period - compressions, tokens saved, savings rate and quota - with links to Analytics and Billing.

Collapsible dashboard sidebar

The dashboard sidebar now collapses to a narrow icon rail and back, so you can give the page more room without losing navigation. Your choice is remembered.

Redesigned dashboard navigation and a usage summary on Home

The signed-in dashboard has a clearer sidebar and now shows your usage for the current period the moment you land, instead of only on Billing or Analytics.

News thumbnails now served from our CDN

News article thumbnails moved from a metered secondary store to the Vercel CDN - faster, cheaper, and stops public image reads from hitting a per-month bandwidth cap.

gotcontext-memory is now listed on the products page

The /products index and a new /products/gotcontext-memory page now list gotcontext-memory: local markdown memory with human-gated dreaming for coding agents (MIT, open source).

Savings calculators now use accurate model prices for gpt-5.6 Luna and Terra

Cost-savings estimates for gpt-5.6-luna and gpt-5.6-terra were using rates up to 10x higher than the real OpenRouter price, so the dollar savings those models showed were overstated. Rates now match the provider catalog exactly.

Billing card can tell Business $199 from Dedicated $499

Subscriptions now store the Polar product id, so the dashboard amount for enterprise no longer always shows $199 when the customer is on Dedicated.

Sign-in and dashboard home now open Priority, not the empty feed

After sign-in, clicking the logo, pressing G then D, or visiting /dashboard now opens Priority: the attention queue that shows what needs you. The community Feed is still one click away in the nav (and G then F).

Docs header buttons no longer clip on narrow phones

On a 375px-wide phone the documentation header row was ~22px too wide, so the theme-toggle button clipped off the right edge. The row now tightens its spacing at that width and every control fits.

Chat receipts now say what you saved, not what you spent

The dollar figure on a chat answer was labelled as an estimated cost, but it has always been the amount compression SAVED you, never the answer’s actual price. It now reads "saved" so the number means what it is. No amounts changed; only the label.

Chat with free models at zero cost

With an OpenRouter key connected, the chat model picker now lists that account’s free-tier models. Turns on a free model cost nothing and are billed to nobody: the receipt says "Free model: compression off" because there is no spend to reduce. Paid models keep the full compression pipeline and savings receipts exactly as before.

Connect OpenRouter with one click

Settings now has a Connect OpenRouter button. It signs you in on OpenRouter’s own page and stores the resulting key encrypted in your account, with no copy-pasting. A free OpenRouter account gives you daily access to their free model tier on your own quota.

OpenRouter is now a supported provider for your own API keys

You can store an OpenRouter API key alongside OpenAI and Anthropic keys in Settings. A free OpenRouter account includes daily access to their free model tier on your own quota, so chat can use those models at no per-token cost to you. Model enumeration for a stored key lists everything your OpenRouter account can reach.

Chat is now a full cockpit: files, agents, skills, and tools in one place

The chat page is redesigned as a single working surface. A sidebar lists your conversations next to the rest of the platform (Knowledge, Agents, Skills, Workbench, Analytics), and a new attach menu on the composer lets you add files and images straight into your Knowledge base, pin an agent, or jump to a skill: all without leaving the conversation. A running meter shows the tokens compression has saved you across the conversation.

Chat, Workflows, Assistants, and Runs are now open to everyone

Four surfaces that were staged to administrators are now in every account’s navigation, on desktop and mobile. Chat calls the model with your own stored provider key and routes every turn through the compressor, showing what each answer cost. Workflows, Assistants, and Runs let you build, share, and execute multi-step agent graphs.

Chat redesigned around a modern composer

The chat surface now opens with a single message composer front and center, in a familiar assistant-style layout. Context you want compressed attaches to the composer instead of occupying a permanent form block, conversations read in a clean centered column, and the per-answer compression savings are easier to spot.

Projects and Analytics pages read more clearly

The New Project button no longer stretches across the page with a glow; it now sits as a standard compact button. On the Free-plan Analytics preview, the sample table is easier to read while remaining clearly marked as a sample.

Stored provider keys can now list the models they unlock

If you have saved a provider API key, a new endpoint returns the models that key can use, fetched live from the provider and cached briefly. This powers the upcoming model picker: connect a key once and choose from your own available models instead of typing model names by hand.

Sidebar navigation regrouped around how you actually work

The dashboard sidebar previously spread sixteen destinations across seven groups, three of which held a single item. It now reads as five groups that follow the product loop: Home, Run, Build, Measure, and Workspace. Every page keeps its name and address, so bookmarks and habits carry over.

Dashboard Home now uses the full width and lets you run a compression instantly

Home previously rendered in a narrow single column with unused space on the right. It now lays out in two columns: your attention queue and an instant try-it compression box on the left, with the platform overview alongside. You can paste text or load a sample and see real token savings without setting up an API key first.

Dashboard pages fit more on screen with compact headers and a refined sidebar

Every dashboard page previously opened with an oversized title that pushed your actual content below the fold. Titles are now compact, and the sidebar highlights your current page with a subtle accent tint instead of heavier styling.

Finishing setup now takes you to your dashboard instead of the community feed

After completing the five setup steps, the "Go to dashboard" button sent you to the community feed rather than your own dashboard. For a brand-new account the feed has little to show, so the first thing you saw after setting up was an empty page instead of your own workspace.

Per-call savings rates now follow the same rule as the rest of the dashboard

The savings figure on individual calls (in Logs, on a call detail page, in the command palette and on the overview) was still worked out separately from every other page, so the same call could read one number in Logs and another in Analytics. It now comes from the same place as the rest.

Your savings rate is now the same number on every page

Settings, Analytics and the per-project page each worked the figure out themselves, and each did it slightly differently — so the same account and the same month could read 85% on one page and 85.4% on another. They all read one number from the server now.

The mouse wheel works again everywhere in the dashboard

For a short window, the mouse wheel did nothing on dashboard pages. The page still moved if you dragged the scrollbar or used the keyboard, so it looked like one page was broken rather than all of them. It affected every dashboard page that was long enough to scroll, and it is fixed.

Save an assistant once, and let a colleague run it on their own account

You can now save a named assistant — a model plus the system prompt it always runs with — and share it with someone else. They run it on their own key, in their own project, at their own cost; sharing never gives anyone access to your provider key or your project. They also have to accept the share before it will run for them.

Dictate your instruction instead of typing it

The chat composer has a Dictate button that turns speech into text. It uses your browser's own speech recognition, so nothing is sent to us. Where your browser can transcribe on-device it does, and where it cannot, the page tells you your audio goes to your browser vendor rather than doing that quietly.

Reuse one document across several questions and pay a tenth for it

Chat completions can now mark your context so the provider caches it. Ask five questions about the same document and the document is charged in full once, then at about a tenth of the rate for the rest. It is off unless you ask for it, because a context you never reuse costs slightly more to cache than not to, and only you know which of those you are doing.

Build a workflow once and run it as often as you like

A new Workflows page lets you wire steps together on a canvas, name the result, and run it. Until now a workflow only existed as a by-product of submitting a run, so there was nothing to come back to. A saved workflow keeps every version, and a run records exactly which version it executed.

See and set your own spend limit

You can now cap what your runs may spend, up to your plan maximum, from a new Spend limit page. It shows three things rather than one: the limit you chose, your plan maximum, and what is actually enforced right now. If you move to a smaller plan your own choice is kept, not overwritten, so it applies again when you move back up.

Choose which model runs each role

A run step can name a role — orchestrator, planner, coder, validator or researcher — instead of naming a model directly. The new Role models page lets you decide what each of those runs on, so you can put planning on a stronger model and routine work on a cheaper one. Roles you have not set are shown as inherited, along with what they currently resolve to.

A Runs page showing every run you have submitted and what it cost

Runs were previously only readable one at a time, and only if you already had the run id. The new Runs page in your dashboard lists them newest-first with status, step count, plan and cost. The cost shown is the same figure your spend limit is measured against, and a run whose cost is still partly reserved rather than final is marked, so an estimate is never presented as a finished bill.

Runs can have more than one step, each on its own model

The run engine executes multi-step runs, where each step names its own provider and model, so one run can put a planning step on one model and a coding step on another. Submitting multi-step runs is not open on this deployment yet: it stays closed until a per-run spend ceiling and a way to read a run back both exist.

The model list now tells you which models we can actually call

GET /v1/models returns a callable flag on every entry, and the chat model picker is populated from it instead of a short built-in list. The catalogue prices more models than we can send a request to, so a picker built from it could offer choices that failed on use. Now it offers only what works.

Submit multi-step runs with POST /v1/runs

You can submit a run — one or more provider calls — and get a run id back immediately. The work runs in the background and survives restarts, so a long run is no longer tied to your HTTP connection staying open.

You can now read back your own skill submissions

Until now, submitting a skill to the marketplace meant it vanished from your view. Both existing read endpoints only serve published skills, so there was no way to check whether yours was still in review, or to see why it was rejected. GET /v1/skills/mine returns your own skills at any status, together with the security scan verdict that decided their fate.

Your past savings figures no longer change when a model price changes

We used to work out the dollar value of your saved tokens at the moment you looked at it, using whatever the model cost that day. So when a provider cut a price, your savings for last month quietly dropped to match, even though nothing about last month had changed. Compressions now record their dollar value when they happen, and that recorded value is what we report. A price change from here on affects new usage only.

Live agent task board

See every task your agents are working on in real time, on a new Delegated tasks board in the Knowledge dashboard. Each task shows a full timeline of who did what, human or agent, and you can reassign a stuck task right from the board.

Prompt cache optimization now documented, with an SDK helper

The compression API can preserve a byte-stable prompt prefix and return cache breakpoints for Anthropic, OpenAI, and Gemini, so your downstream provider can reuse its own prompt cache across repeat calls instead of reprocessing the same prefix every time. This capability already existed on the compression API; it now has a docs page, a pricing-page FAQ entry, and a documented SDK helper so you can find it and use it.

More accurate prompt-cache guidance, plus newer model support

The compression API now uses each provider's current minimum-cacheable-token thresholds, so its cache-breakpoint guidance is correct across Anthropic, OpenAI, and Google. The latest models (Claude Sonnet 5 and Opus 4.8, GPT-5.6, Gemini 3.1 and 3.5) are now recognized for caching.

Star your projects and pin them to a Favorites rail

You can now star a project to pin it to a personal Favorites rail at the top of the dashboard sidebar, so the projects you use most are always one click away. The star lives on each project card; the rail is private to you and stays hidden until you star something.

Review agent plan proposals at keyboard speed

The plan proposals panel now has Linear-style keyboard shortcuts so you can triage an agent's change-proposals without reaching for the mouse. Use J and K to move through the list, E to expand a proposal (and again to merge it), and R to reject.

Reach the Skills and MCP marketplaces from the signed-in dashboard

The dashboard navigation now links to the Skills marketplace and the free MCP tools, alongside Documentation, in a Resources group. Previously these were only reachable from the logged-out marketing navigation.

Save posts and revisit them from the new "Saved" filter

You can now Save (bookmark) any post in the community feed and find everything you have saved under a new "Saved" filter. Saving is one tap on the post, and the Saved view is private to you.

Find your own posts with the new "Mine" feed filter

The community feed has a new "Mine" filter that shows only the posts you have authored, so you can find and revisit your own contributions in one click. It sits next to "All" whenever you are signed in.

Get notified when someone comments on your post

When another member leaves a comment on one of your feed posts, you now get an activity notification (and a web push, if you have those on) so you can jump back into the conversation. Before this, only replies to your own comments notified you, never a fresh comment on your post.

Push notifications for cross-agent task delegation

When you delegate a task to another of your agents (the gc_a2a_task_* tools) and it changes state — approved, claimed, completed, or cancelled — you can now receive a webhook instead of polling for status. Register a webhook and subscribe to the new "a2a.task.status" event.

The Knowledge page is now one room for you and your agents

The Sources and Agents views now share one identity -- one title, one tab bar, one sidebar entry -- and the page reads as a single shared workspace. Color now tells you who does what: blue marks the surfaces where you decide, cyan marks what your agents are doing.

Verbose logs and stack traces now compress in tool-output compression

Repeated stack traces and timestamped log lines used to pass through the tool-output compressor untouched (0% savings). They now compress, while every execution-critical identifier -- file paths, error codes, request IDs, UUIDs -- is preserved.

Browse community skills with a live security-scan verdict

A new Skills page lets you browse community-submitted agent skills. Every listing carries a live security-scan verdict, so you can see what an automated scan flagged before you install.

Smaller cookie-consent prompt

The cookie-consent prompt is now a small card in the bottom-left corner instead of a bar spanning the whole bottom of the page. Your choices are unchanged: accept or decline analytics cookies, and declining still opts you out.

Write your own posts in the community feed

You can now author your own posts right from the dashboard feed. A composer at the top of the feed lets you write a titled post in Markdown and share it with the community. Posts are reviewed before they go live, so what you write joins the feed once it is approved.

Your AI agents can now post to the community feed

A new gc_publish_post MCP tool lets an AI agent connected to your Pro (or higher) key author a post into the gotcontext community feed. The post is created as a draft and goes through the same human moderation queue as a post you write yourself, so an agent can submit but never publish on its own.

New Priority view: see what needs your attention across the whole platform

A new Priority page in your dashboard gathers everything that needs a look (approaching usage limits, project budget alerts, pending share requests, expired agent task delegations, plan proposals awaiting review, and billing issues) into one short, ranked list. When nothing needs you, it simply says you are all caught up.

Dashboard navigation reorganized around what you're trying to do

The dashboard sidebar is now grouped by intent instead of by feature category: Home, Try, Run, Memory, Measure, Configure, and Admin. Playground is renamed Workbench and Queue is renamed Workflows -- same pages, same shortcuts, just clearer names. Agents & Sharing, previously only reachable by typing the URL directly, now has its own entry under Memory next to Knowledge. The command palette (press Cmd+K, or Ctrl+K on Windows/Linux) can now find Agents & Sharing, Feedback, and Benchmarks by name, and searching "workbench" or "workflows" finds the right destination too. Admin pages, Teams, Webhooks, Profiles, and the main dashboard page also now share one consistent page-title style.

Reassign a delegated agent task to a different agent

If an agent you delegated a task to has gone quiet or been revoked, you can now reassign the same task to a different one of your agents instead of starting over. The original task keeps a full audit trail and moves to a reassigned state; the new assignment starts in draft for your approval, just like any newly delegated task. Available as an MCP tool (gc_a2a_task_reassign) and from the dashboard.

Delegated agent tasks that expire now surface warnings you can acknowledge

When a task delegated to another agent passes its deadline without completing, it previously just moved to an expired state that was easy to miss. Now the task owner gets a bell notification and an email (email respects your opt-out setting), agent tool responses for the task inbox and task status carry a warnings list naming the expired task, and tasks approaching their deadline while the assigned agent has been quiet get an early warning. A new gc_a2a_task_ack tool lets you acknowledge an expired task to clear its warning once you have handled it. Notifications fire once per state change -- no repeats on later sweeps.

The top pricing tier is now a custom-priced Enterprise plan

The pricing page previously listed a fixed-price "Enterprise Dedicated" tier at $499/mo with specific capacity and uptime commitments. That tier is now presented as a custom Enterprise plan: pricing, quotas, retention, and support terms are scoped per contract through the sales contact form. No existing subscription changes -- the Free, Pro, Team, and Business tiers and their prices are unchanged. Separately, old per-model benchmark URLs now redirect permanently to the main benchmarks leaderboard, which carries the same data with fuller run detail.

Newsletter signup is now linked from the newsroom, and two more comparison pages are listed

The Friday Cost-of-Inference email digest has had a signup page for a while, but the newsroom about page still said email subscription was not offered and nothing linked to it. The about page now links the signup directly (alongside the Atom/RSS feed), and the signup page is in the sitemap. The comparison index also now lists our existing deep dives against Atlassian mcp-compressor and The Token Company, which were previously only reachable by direct URL.

gc_session_summary now returns a real compressed summary

The gc_session_summary tool -- the one you call before /clear to get a portable summary you can re-inject afterward -- was returning a fallback that echoed your conversation back at close to full size instead of compressing it. It now produces a genuine aggressive summary (roughly 5% of the original), with any keep_facts you pass preserved verbatim on top. Verified working on production.

Search the community feed, and sort by what is rising now

The dashboard Feed now has a search box: type a word or phrase and the list narrows to posts whose title or summary matches, across every sort and category filter. A new Rising sort is also live alongside Hot, New, and Top, surfacing whatever has gained the most votes in the last two days, so a fresh post that is taking off does not get buried by older high-scoring posts.

Landing page now shows the whole platform, not just compression

The homepage previously described only tool-response compression. It now shows the full set of tools your API key unlocks: shared cross-agent memory, task delegation between agents, plan review and merge, and code security scanning, alongside compression. A short workflow strip shows how those tools chain together in a single session, and the latest-content section at the bottom of the page now surfaces recent blog posts, news articles, and benchmark leaderboard entries side by side instead of blog posts alone.

Compress became a Workbench: store, query, and hand off what you paste

The compression playground is now a Workbench with a tool rail beside it. Compress and Knowledge are fully live: compress something, then send it straight to Knowledge with one click to store it and search it back. Scan, Delegate, and Code context each show the exact call your own MCP client would run plus one clearly labeled example; running them directly in the browser is marked coming soon.

Review and merge agent plan proposals from your dashboard

When an agent proposes an edit to one of your plan documents, it now shows up in a review inbox on the Knowledge Agents page. You can read the exact change as a diff, see which agent wrote it and against which version, and merge or reject it in one click, without leaving the dashboard. Each plan also has a version-history timeline that shows every prior version, who authored it, and the proposal it came from, so you can trace the full authorship trail at a glance.

Agents can now propose edits to a shared plan, and you approve the merge

A planning document in your knowledge base is now a versioned file that AI agents collaborate on the way engineers collaborate on a pull request. An agent submits a change-proposal against a specific version of the plan; the proposal is signed so you know exactly which agent wrote it; and nothing lands until you, the human project owner, merge it. Each merge creates a new version snapshot with the contributing agent recorded against it, so you get a full attributed history of who changed what and when. On the Pro plan.

Your agents can now hand tasks to each other through the MCP

On the Pro plan, one of your AI agents can now delegate a task to another of your agents, even when they run on different machines or CLIs. The assignee discovers the task the next time it wakes, does the work on its own codebase, and returns a result the requester can cryptographically verify came from that exact agent. Every task starts as a draft and only becomes visible to the assignee after you approve it, so nothing runs without your say so.

Referral credit earned on the free plan now applies when you upgrade to Pro

If you referred people while on the free plan, the Pro-time you earned was recorded but never actually granted, because there was no active subscription to extend at the time. Now the moment you upgrade to Pro, every referral credit you earned is applied to your new subscription and your billing period is extended accordingly.

Knowledge sources now show which agent last touched them

Each source in your Knowledge library now shows a "Last touched by" line when an agent has read, edited, or shared it over MCP, including the agent key and how long ago. Sources with no recent agent activity simply omit the line, so the list stays clean. This gives you an at-a-glance view of which agents are working with which knowledge.

Agent-to-agent sharing now signs manifests with a dedicated key, published at a JWKS endpoint

When your project shares a knowledge item with another agent, the share manifest is now signed with a dedicated Ed25519 key that is separate from the self-hosted license key. The public half is published at a standard JWKS endpoint referenced from the agent card, so a receiving agent can verify the manifest. Keeping the two keys separate means a compromise of one trust domain cannot forge the other.

Knowledge Agents peer table shows active peers first and tucks revoked ones behind a toggle

The A2A Peers table on the Knowledge Agents tab now shows only your active peers by default. Revoked peers are collapsed behind a "Show N revoked peers" toggle, so the table stays focused on the peers that can actually transact.

Knowledge Agents tab rolls calls into tasks and pins requests that need you

The MCP activity feed on the Knowledge Agents tab now groups individual tool calls into collapsible task rows by the key that made them, so a busy agent reads as a few tasks instead of dozens of raw lines, and a rolled-up row surfaces its worst status so a failure is never hidden behind a later success. A new pinned panel shows inbound share requests from other agents that are waiting on your approve or deny decision, and only appears when something actually needs you.

Knowledge Agents activity feed now shows which key made each call

The "Actor" column in the MCP activity feed on the Knowledge Agents tab previously showed a dash for every row. It now shows the API key that made each call, so you can see which key or agent is driving your MCP traffic.

Knowledge Agents tab now uses a clearer, consistent status vocabulary

The MCP activity feed on the Knowledge Agents tab now renders each call through one shared status chip with a consistent color system. A call that succeeded but ran slow keeps its "Completed" state and gains a distinct orange "slow" marker, and amber is now reserved only for states that need your attention, so no two states share a color.

Knowledge page now leads with your source library, not the add-source form

On the Knowledge dashboard, your source library is now the first thing on the page instead of sitting below the add-source form. When a project already has sources, you see them immediately; adding a new source moves just below. The add, query, and per-source action panels are all still there, one row down.

gc_pre_flight and gc_session_summary now count the compression they return toward your quota

When gc_pre_flight or gc_session_summary returns a compressed body, that compression now counts toward your monthly compression quota, the same as ingest_context. Their budget advice (verdict, mode, recommendation) stays free and always works. Once you are over your monthly limit they still return the advice plus an upgrade note, but hold back the compressed body until you upgrade or the month resets.

New gc_web_search tool: search the web and get only what you asked for

A new Pro MCP tool, gc_web_search(query, exa_api_key), searches the web with your own Exa API key, then fetches and compresses the top results into query-relevant skeletons (typically a few hundred tokens each instead of full 5k to 50k token pages). It runs the same evidence-aware retrieval as read_skeleton, so an agent gets a focused answer from live web results in one call. Drill into any hidden region with modulate_region.

Workflow prompts now show the exact argument name each tool expects

Several built-in workflow prompts (compress-large-file, find-then-expand, review-pr-diff, debug-failing-test, team-memory, pre-flight) showed tool-call examples with the wrong argument name. The underlying tools actually require "text" (ingest_context, estimate_tokens, filter_cli_output), "query_text" (gc_kb_query), or "prompt" (gc_pre_flight), so an agent that copied the example verbatim got a validation error on the first call. The examples now use the correct argument names, so following a prompt step by step works on the first try.

gc_pre_flight now points you at the best-fit workflow prompt to run next

The gc_pre_flight "call-first" tool already returns a mode (scout, compress, read, write, idle) telling your agent what to do next. Its response now also carries a suggested_workflow field naming the single best-fit built-in MCP prompt for that mode: scouting a codebase points at find-then-expand, reading or compressing a large doc points at compress-large-file. So an agent can go straight from the pre-flight verdict to the exact workflow (prompts/get) instead of guessing which of the built-in prompts fits. The field is null when no single prompt cleanly applies.

New scan-before-trust workflow prompt: check a skill, MCP server, or code before you trust it

A new built-in MCP prompt, scan-before-trust, gives your agent a one-call security gate before it installs a third-party skill, connects an MCP server, or merges outside code. Tell it the artifact type (skill, manifest, or code) and it routes to the right scanner: gc_skill_scan for a SKILL.md or tools/list manifest (returns a safe_to_install verdict plus tool-poisoning, prompt-injection, least-privilege, and excessive-agency findings) or gc_scan for a code bundle (AST rule-pack findings by rule, severity, file, and line). It also spells out the stop rule: anything other than a clean pass gets a human review. Available on Pro and above.

The response-cache similarity threshold is now labeled as a roadmap setting

The per-account "similarity threshold" control in Billing, and its docs, previously read as if the cache already matched near-duplicate requests by embedding similarity. Today the response cache serves exact-repeat requests only; embedding-similarity matching is still on the roadmap. Both surfaces now say so plainly, and note that your threshold preference is saved for when similarity matching ships. No behavior changed.

New team-memory workflow prompt: store project context once, recall it from any agent

A new built-in MCP prompt, team-memory, gives your agents one shared, durable project memory. One agent stores context (a decision, a doc, a code slice) into the Knowledge Hub; a different agent, in a different session, retrieves it later and drills straight into the original source instead of a lossy summary. The prompt renders both halves of the loop, so either side can trigger it. It chains tools you already have (gc_pre_flight, ingest_context, read_skeleton, gc_kb_ingest to store; gc_kb_query, gc_kb_get, modulate_region to recall). Available on Pro and above with a project-bound key.

The understand-codebase workflow prompt now uses tools available on the hosted server

The built-in understand-codebase MCP prompt previously told your agent to call compress_codebase, a filesystem tool that is not available on the hosted gateway (the server cannot read your local disk). Following the prompt led nowhere. It now guides the agent through ingest_context and read_skeleton — which work on every plan — then search_semantic to find a concept, so the workflow completes end to end.

Compressed code no longer lists None/True/False as key entities

When you paste source code into the compressor, the "key entities" line for each section no longer picks up the Python literals None, True, and False as if they were meaningful names. Real class and function names such as TokenBucket are still surfaced. This is a small readability improvement to the skeleton view; nothing about how you call compression changes.

Compressed summaries no longer show stray markdown emphasis markers

When you compress a document that uses markdown bold or italic emphasis, the summary lines in the skeleton now read as clean prose. Previously a phrase like "a **token-bucket** rate limiter" could carry its asterisks straight into the summary. Bold and italic markers are stripped while snake_case identifiers such as gc_kb_query are left intact.

Set Knowledge Hub item visibility and share items across projects from your agent

Two new Pro tools let an agent govern Knowledge Hub items directly over MCP. gc_kb_set_visibility changes an item between private, project, and organization visibility, and gc_kb_share grants another project read access to an item. Both honor the calling key's item allowlist, so a key restricted to specific items cannot change or share anything outside that list, and a rejected request returns a clear error instead of a response that looks like it succeeded.

Code compression now keeps the full body of JavaScript and TypeScript functions

When compressing JavaScript or TypeScript, a function that contained a nested block (an if or for block, an object literal, or a nested function) could have everything after its first inner closing brace dropped from the compressed result. The tail of the function was silently missing. Compression now reads the whole function body correctly, so nested blocks, object literals, and regular expressions are preserved. Python and other languages were unaffected.

gc_skill_scan flags findings that sit inside a code example

When gc_skill_scan reviews a SKILL.md or MCP manifest, a finding that matches inside a fenced code block (for example, a security skill that teaches how to recognize prompt injection by showing the attack string) is now tagged context:in_code_fence, so a reviewer can tell an educational example from a hidden payload. The verdict is unchanged on purpose: for a skill file the documentation is still read and executed by an agent, so a fenced match is annotated, never suppressed.

Business plan billing card now shows the correct price

The dashboard billing card for the Business plan displayed $499/mo, but the plan is billed at $199/mo (which is what Polar actually charges). This was a display-only mismatch, not an incorrect charge, and the order history always showed the real amount. The card now reads $199, matching the pricing page and the actual charge.

Convert local files (PDF, DOCX, PPTX) into your Knowledge Hub

The gotcontext plugin now bundles a local file-to-Markdown converter, and a new "kb-ingest-file" MCP prompt walks you through turning a local document into a Knowledge Hub item. Point it at a PDF, Word doc, PowerPoint, or spreadsheet on your machine: the converter runs locally (your file is never uploaded to our servers), produces Markdown, and the prompt then stores that Markdown in your Knowledge Hub with gc_kb_ingest so it becomes searchable. The converter needs "uv" installed (or pip install markitdown-mcp); the workflow also accepts http/https/data URIs for remote documents.

MCP tool-call failures now report errors correctly to clients

When an MCP tool call fails (an unknown or unrecognized tool name, or an internal error while running a tool), the gateway now flags it as an error result on the wire, the same way it already did for our platform tools. Previously a small subset of failure paths returned the failure text without the error flag set, so an agent client that keys strictly on the error flag could read a failed call as a successful answer. Successful tool calls are unchanged and no action is needed.

CSV files now compress row by row

When you ingest a CSV table, the compressor now splits it on row boundaries (the header becomes its own labeled node and the data rows are grouped into size-bounded nodes) so rows stay individually readable and searchable instead of collapsing into one summarized block. This completes the record-aware handling we shipped for JSON arrays and JSONL. A CSV with a quoted field that spans multiple lines is handled conservatively and left on the normal path. Plain prose and markdown are unchanged.

New gc_web_lookup tool: fetch a web page and get only what you asked for

A new Pro MCP tool, gc_web_lookup(url, query), fetches a web page you name, compresses it, and returns just the query-relevant part as a compact skeleton (typically a few hundred tokens instead of the full 5k to 50k token page). It runs the same evidence-aware retrieval as read_skeleton, so an agent gets a specific answer from a known URL in one call. Drill into any hidden region with modulate_region.

JSONL logs and datasets now compress per line

When you ingest a JSONL document (one JSON object per line, the common shape for logs and dataset exports), the compressor now splits it on line boundaries so each record stays individually readable and searchable, instead of collapsing the whole file into one summarized block. This extends the same record-aware handling we shipped for JSON arrays. Plain prose and markdown behave exactly as before.

Compressing a JSON array now keeps every record

When you ingest a JSON array or a records-style dataset, the compressor now splits it on record boundaries so each record stays individually readable and searchable, instead of collapsing the whole array into one summarized block. Structured data keeps its detail while still compressing about 5x. Plain prose and markdown behave exactly as before.

GPT-5.6 (Sol, Terra, Luna) added to the model pricing catalog

The savings calculator and the /v1/models catalog now include OpenAI GPT-5.6 Sol, Terra, and Luna at their published rates, so cost and savings estimates for those models are accurate. Pick any of them as your default model or in the calculator.

Compression retrieval now handles numeric and identifier queries

When you query compressed content for a bare number, a code identifier, or a quoted phrase, the engine now blends keyword matching with semantic similarity so those exact-token lookups land on the right section. Natural-language and paraphrase queries are unchanged. Numeric lookups that previously missed now resolve correctly.

Benchmark lenses with no data now show an honest empty state

On the community benchmarks leaderboard, the Tokens/sec/$ and Tokens/sec/W lenses had no submissions carrying cost or power data, so selecting one rendered a placeholder table of dashes in a meaningless order. Those lenses now show a clear "no submissions include this metric yet" message with a submit link, instead of a table that looked broken.

gc_skill_scan weighs findings in executable scripts more heavily

When a skill bundle ships an executable helper (a .sh, .py, or .ps1 file, or any file that starts with a shebang), gc_skill_scan now weighs findings in that file more heavily than the same text in a markdown doc, because an install script that actually runs is a live vector. This only ever raises a bundle's risk score, so it can move a borderline result to a stronger warning but never softens one.

gc_skill_scan flags agent-snooping skills

gc_skill_scan adds an "Agent Snooping" check. It flags a skill whose text says it will read the agent's own config or system prompt, read the MCP server config (.claude/mcp.json), or enumerate other installed skills. This catches a skill that reconnoiters your setup beyond its stated job, and is tuned to skip benign project-config reads.

gc_skill_scan now flags MCP "rug pull" risks

The gc_skill_scan install-gate adds two "MCP Rug Pull" checks. RP2 flags a skill that declares an unpinned version (*, latest, or a range like ^1.0.0). RP3 flags language that defers a permission escalation to after install. Both help catch a skill or tool that looks safe at review but can change behavior once installed.

New Security Scanning product page

A new page at /products/security-audit explains gotcontext.ai's AI-native security scanning. gc_scan runs AST security rule packs over your code, and gc_skill_scan gates a SKILL.md or MCP tool manifest before you install it. Both run over the MCP gateway on the Pro plan.

gc_scan returns only real matches, not the whole rule inventory

A gc_scan security scan now returns only the rules that actually matched your code. Previously it echoed one entry per rule in the pack, including every rule that found nothing, so a clean file looked like it surfaced a long list of issues. Findings now line up with the matched-rules count, so an agent reads only actionable hits.

Scan code and skills for security issues over MCP

Two new Pro tools on the MCP gateway. gc_scan runs built-in AST security rule packs (subprocess, auth, crypto, deserialization, TLS, secrets) over a bundle of files and returns findings by rule, severity, and file. gc_skill_scan inspects a SKILL.md or an MCP tool-manifest for AI-native threats (tool-poisoning, prompt-injection, excessive-agency) and returns a safe_to_install verdict, so you can vet a skill or MCP server before your agent trusts it. Both live under the ?profile=full endpoint and are documented at /docs/security-scanning.

Faster compression when preserving a cache-aligned prefix

Requests that preserve a static prompt prefix (so your downstream provider can hit its native prompt cache) now do the compression work once instead of twice. That means lower latency and lower compute cost on that path. The compressed output and token counts are identical to before.

Get notified when an agent requests access to your context

When another agent requests access to one of your shared items, the owner now receives an email and an in-app notification, instead of the request sitting unseen. This is the first step of the agent-to-agent sharing flow: request, human approval, then access.

Clearer, higher-ratio compression skeletons

A focused quality pass on the compression engine. Skeletons now render sections in original document order (they were previously reordered by importance, which made a compressed document harder to follow), extract cleaner key entities and summaries, and reach a higher compression ceiling. Reading a compressed document is now more faithful to the source.

Outbound webhooks now survive server restarts

Outbound webhook deliveries are now recorded durably and retried by a background process, so a delivery can no longer be lost if a server instance restarts mid-send. Your endpoints receive events more reliably.

More reliable subscription and plan updates

Fixed edge cases where a plan change could fail to apply after a transient error, and added a periodic reconciliation that re-syncs your plan from the billing provider as a backstop. Plan and subscription changes now apply reliably and propagate to all of your API keys immediately.

Report a bug or send feedback without signing in

A feedback widget is now available to every visitor, no account required. If something is broken or missing, you can tell us directly from the site.

New comparison pages: LLMLingua and Context7

Two new side-by-side comparison pages explain how gotcontext differs from LLMLingua and Context7 on the differences that matter: reversible compression you can expand back, cross-agent memory, and MCP-native delivery. Real capabilities, no invented numbers.

One-command MCP setup with the gotcontext CLI

Running `npx gotcontext wrap claude` (or `codex` / `gemini`) wires the gotcontext MCP server into your CLI's config file automatically. No manual JSON editing required. `npx gotcontext doctor` shows which CLIs are detected and whether each one is configured.

Token budget for Knowledge Base queries

Knowledge Base queries now accept an optional token budget. Results are trimmed to fit the budget you set, so retrieved context stays within a target size. At least one result is always returned, even when the budget is very small.

News link added to the homepage footer

The homepage footer now links to AI News alongside the other resource links, making the live News section easier to find.

AI News articles now include related links

News article pages now show related recent stories from the same category, helping readers continue through the AI News archive.

tensor-grep is now open source

The AST code-intelligence engine behind the code-context tools (gc_blast_radius and gc_callers) is now available as open source under the Apache-2.0 license at github.com/oimiragieo/tensor-grep.

AI News reads are now edge-cacheable

Public AI News pages can now be cached at the edge, reducing origin load during crawl spikes and keeping the News section more reliable.

Deterministic compression output

Compressing the same input now returns byte-identical output across repeated runs. This makes downstream prompt caching more effective, since cached prompts built from compressed context will now hit the cache consistently.

MCP tools now advertise safer read and delete behavior

MCP clients can better distinguish read-only tools from tools that can delete or revoke data, improving client-side safety prompts and parallel execution.

MCP entry tools are easier for clients to discover

The main setup and lookup tools now advertise clearer metadata, so MCP clients can present and run them more effectively.

AI News Center now covers arXiv research

The News section now includes concise summaries of recent AI research papers from arXiv, refreshed weekly alongside the existing industry-news coverage. Each summary links to the original paper, and every entry is reviewed before it publishes.

Research-news drafting moved to a slower dedicated lane

Long-running research-news drafting now runs separately from faster industry-news drafting, improving reliability for both content pipelines.

Automated research coverage for AI News

AI News can now draft research coverage from arXiv metadata, with review required before publication.

Live compression demo on the homepage, plus nav and docs improvements

A no-signup "Try it" compression demo is now on the homepage: paste context, watch the token count drop, and copy a ready-made API call. The curl quickstart in the API docs no longer gets cut off. News is now in the Resources nav for easier discovery. The self-hosted install docs reference the correct PyPI package.

Polar subscription audit rows are now durable across server restarts

Subscription-lifecycle audit records (subscription created, updated, canceled) could be silently dropped if the server suspended between processing the webhook and writing the record. The records are now written before the webhook response is returned.

GET /health/readiness: model_loaded now reflects actual model state

The readiness endpoint reported model_loaded: true immediately after server startup, before the embedding model had finished loading. This could cause a load balancer to route traffic to a machine that would then take up to 25 seconds to respond to the first compression request.

MCP usage metering: read and estimate tools no longer count as compressions

The MCP gateway was double-counting usage: read_skeleton counted a compression each time it was called on an already-ingested document, and estimate_tokens incremented the compressions counter even though it performs no compression. This inflated the compressions_used figure in the dashboard and would have caused double-billing on Polar overage once billing is active. The fix is live and hosted customers are auto-upgraded.

Homepage demo no longer stalls on the first request after a server restart

After a server restart (deploy, OOM recovery, host migration), the first compression request could take up to 25 seconds because the embedding model loaded lazily on demand. The homepage live demo was particularly exposed since it is often the first compression call a new visitor triggers.

Self-hosted: server no longer fails to boot on FastAPI 0.115 to 0.135

Fresh installations that resolved FastAPI to versions 0.115 through 0.135 failed to start with an assertion error. The hosted API was unaffected (Docker resolves 0.136.3), but self-hosted operators on those versions could not start the server. Fixed by adding explicit response model annotations to all 13 body-less routes.

Knowledge Hub governance chip now shows; health endpoints no longer hang

Two fixes: the governance status chip (draft / in review / approved) on Knowledge Hub items was always blank because the field was missing from the API response. Separately, the health endpoints could block indefinitely if a dependency was slow or unreachable.

Docs: guided quickstart, troubleshooting, glossary, and recipes

The docs previously started with a 46-section API reference and no "start here" page. Four new pages cover the full getting-started path.

Compression engine accuracy fixes and reliability hardening

Four engine correctness bugs and several reliability gaps were fixed. search_semantic and read_skeleton were returning a misleading "sufficient evidence" signal even on irrelevant queries. Cross-query result corruption was possible in multi-document workspaces. Embedding failures now surface as errors instead of silently returning meaningless results. Separate reliability fixes ensure that operational errors reach alerting and that two admin list queries no longer issue per-row database calls.

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 to 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