TemprTempr
Changelog

What’s new in Tempr

Every release of every Tempr product, newest first. Everything here is live: the extensions update through their marketplaces, and the Gateway and the Portal update for everyone on the date shown.

235releases
975changes
Nov 4last update

Subscribe via RSS Read the docs

Latest release of each product

235 releases, 975 changes since Jul 31, 2026

November 2026

Portal

Update of Portal, Nov 4, 2026

Latest

Changed

  • Your Agents dashboard is your setup. Until your first message, the dashboard opens with the setup checklist, and each step shows how to do it right there: where to install Tempr Chat for Visual Studio, VS Code or JetBrains IDEs, how to sign in with your license key, and where to add a provider key. The sidebar's Get started link is gone: for the Gateway it pointed at the dashboard you were already on, so it seemed to do nothing.
  • One free trial per customer. Your first Standard or Pro plan starts with a 7-day free trial, as before. A later plan on the same account, or a plan paid with a card that already had a trial or a prepaid card, is charged right after checkout instead.
Gateway

Update of Gateway, Nov 2, 2026

Latest

Added

  • IONOS: models on IONOS AI Model Hub, hosted in Berlin, are available with your own IONOS Cloud API token as ionos/... (for example ionos/openai/gpt-oss-120b or ionos/Qwen/Qwen3.8-27B), so prompts and answers stay in Germany. Reasoning levels are offered per model, usage is priced from IONOS's published prices, and a reasoning level a model doesn't take falls back to the nearest one it does.
Portal

Update of Portal, Nov 2, 2026

Added

  • IONOS is now available as a provider key for Chat, the Gateway and organization keys. Its models run in Berlin. The key page explains which IONOS token to use: one for a user with only the AI Model Hub privilege.
Website

Update of Website, Nov 2, 2026

Latest

Changed

  • IONOS is on the providers page, which now lists 42 providers, and the providers docs say which IONOS token to use.
Gateway

Update of Gateway, Nov 1, 2026

Added

  • Pools: ask for a model, not a host. any/openai/gpt-oss-120b runs on whichever of your providers serve that model, cheapest first, and hands over to the next on a rate limit or an error, trying at most three. /v1/models lists the pools you can use, the catalog lists them all, and the Portal's new Models page shows each one with your hosts' prices, limits and capabilities. The x-tempr-route header names the host that answered. See pools.
  • Host preferences in OpenRouter's provider object. A request can send only, ignore, order, sort, max_price and allow_fallbacks, under OpenRouter's names, for a pool or a fallback chain; fields Tempr doesn't support are ignored and named in x-tempr-ignored-provider-fields. A key can hold the same as its default, in the key editor's Routing section or as routing_policy on the management API, which a request can narrow but not widen. See host preferences.
  • Routing rules, on Pro and up. A key can send requests to another model, alias or pool by what they are: the model they name, x-tempr-metadata values, the end user, the team, a header, whether they use tools or images, or their prompt size. The first rule that matches wins, the x-tempr-rule header and the request log say which, and the key editor has a tester. Also routing_rules on the management API. On Free, saved rules are kept but not applied. See routing rules.
  • First-byte timeout. With first_byte_timeout_ms, a streamed request moves on from a host that hasn't started answering in time. See first-byte timeout.
  • The organization's dashboard, by team. A team picker beside the key filter narrows every figure, chart and breakdown to one team's keys, and a new "By team" table shows each team's requests, cost, share of the cost and errors, with its budget this month. A team's figures are the traffic of the keys in it now, revoked keys included. See teams on the Gateway.
  • Scaleway: models on Scaleway's Generative APIs, hosted in Paris, are available with your own key as scaleway/... (for example scaleway/gpt-oss-120b or scaleway/qwen3.8-27b), so prompts and answers stay in the EU. Reasoning levels are offered per model, usage is priced from models.dev's prices for Scaleway (converted from Scaleway's euro prices), and a max_tokens above a model's limit is retried once at the limit.
  • NVIDIA, for prototyping: NVIDIA's hosted models are available with your own free build.nvidia.com key as nvidia/... (for example nvidia/nvidia/nemotron-3-ultra-550b-a55b), at $0. Its terms allow evaluation and testing only, and popular models can queue on its free tier, so it isn't for production traffic. Ten models that answered promptly are offered, with reasoning levels per model. See providers.

Fixed

  • Fallback chains skip models that can't take the request. A model whose catalog entry says it has no tool calling, no JSON schema output or no image input, or whose context is clearly too short for the prompt, now sits out a request that needs it, instead of answering with a 400 that never handed over to the next model. A model whose output limit is short for the request is tried after the others. The request log lists the models left out and why, and a chain with nothing able to serve the request fails with no_capable_candidate without calling a provider. See models that can't take the request.
Portal

Update of Portal, Nov 1, 2026

Added

  • Scaleway is now available as a provider key for Chat, the Gateway and organization keys. Its models run in Paris. The key needs a Scaleway IAM policy that allows Generative APIs, and the key check says so if it doesn't.
  • NVIDIA, for prototyping: a free build.nvidia.com key lets you try NVIDIA's hosted models, such as Nemotron 3 Ultra, in Tempr Chat, the CLI and the Gateway as nvidia/..., at no cost. NVIDIA's terms allow its free API for evaluation and testing only, so the key is marked "prototyping only" wherever you add it. See providers.
Website

Update of Website, Nov 1, 2026

Changed

  • Scaleway and NVIDIA are on the providers page, NVIDIA marked prototyping only, and the page now lists 41 providers. The providers docs say what its free API allows.
  • Custom models explain adding a self-hosted NVIDIA NIM or a Baseten dedicated deployment.

October 2026

Gateway

Update of Gateway, Oct 31, 2026

Added

  • SambaNova: models on SambaNova Cloud are available with your own key as sambanova/... (for example sambanova/gpt-oss-120b). Reasoning levels are offered per model, and usage is priced from SambaNova's published prices. See providers.
  • Nebius: models on Nebius Token Factory are available with your own key as nebius/... (for example nebius/zai-org/GLM-5.3). Reasoning levels are offered per model, and usage is priced from Nebius's own prices, cached input included.
  • Baseten: models on Baseten Model APIs are available with your own key as baseten/... (for example baseten/moonshotai/Kimi-K3). Reasoning levels are offered per model, and usage is priced from Baseten's own prices, cached input included. Dedicated Baseten deployments work as custom models.

Fixed

  • A request whose prompt and max_tokens together overflow the model's context is retried once with a max_tokens that fits. When a provider rejects it as longer than the model's maximum context and says by how much, the Gateway lowers max_tokens by that amount and tries again, as it already does when a provider names its output limit.
  • The public model catalog lists open-weight Instruct models. GET /v1/catalog left out every model whose id contains "Instruct", such as Llama 3.3 70B Instruct and the Qwen and Kimi Instruct models, on every host, though the Gateway serves them. It now leaves out only OpenAI's own completions-only Instruct models.
  • The setup reminder no longer goes to accounts that have already used the Gateway. An account whose requests were all older than its plan's log retention could be told it had never sent one. Its usage now counts too.
  • Tool calls from Nebius's gpt-oss models arrive whole. Nebius streams the last piece of a tool call's arguments as if it were a new, nameless call, so a client saw the call's JSON cut short and a second empty call. The Gateway now puts that piece back on its call, for every streamed answer.
  • Turning reasoning off on Nebius's Nemotron 3 Nano and MiniCPM-V 4.5 no longer fails. Nemotron answered "off" with an empty reply and MiniCPM-V rejected it, so Nemotron now thinks at its lowest level and MiniCPM-V gets no reasoning setting. GLM-5.1 there now offers low, medium and high, and still switches off.
Portal

Update of Portal, Oct 31, 2026

Added

  • SambaNova, Nebius and Baseten are now available as provider keys for Chat, the Gateway and organization keys.
  • A Tavily key gives the agent web search on models whose provider has none of its own, when you have no Perplexity key. Add it on the API keys or organization keys page; each search is one Tavily credit ($0.008 pay-as-you-go, and Tavily's free plan includes 1,000 a month) and shows in your usage as tavily/search.

Changed

  • Every Tempr email has the same new look, matching temprhq.io: the subject as a heading, one clear button for the next step, and budget alerts that show your spend and budget side by side. What each email says is unchanged.

Fixed

  • A Tavily key is checked when you save it. It used to be saved unchecked and called valid, so a mistyped key only showed up as a failed search in an agent run. Tempr now asks Tavily, which costs no credits, on the API keys and organization keys pages and in tempr keys add.
  • A Tavily key is no longer treated as a Chat-only model key. The Gateway's provider keys page no longer warns that it doesn't work there, organization keys no longer label it "Chat and CLI only", and a Tavily key alone no longer ticks "provider key" on the getting-started checklist. Tavily has its own icon.
Website

Update of Website, Oct 31, 2026

Changed

  • Tempr is @temprhq.io on Bluesky. The footer link and the profile links search engines read now point to bsky.app/profile/temprhq.io.
  • SambaNova, Nebius and Baseten are on the providers page, which now lists 39 providers.
  • The privacy policy and the CLI reference cover Tavily: with no Perplexity key, an agent's web searches on models without their own search can go to Tavily on your Tavily key. The providers docs say what a Tavily key does and costs.
Gateway

Update of Gateway, Oct 30, 2026

Added

  • DigitalOcean and SiliconFlow: models on DigitalOcean's serverless inference and on SiliconFlow are available with your own key as digitalocean/... (for example digitalocean/openai-gpt-oss-120b) and siliconflow/... (for example siliconflow/zai-org/GLM-5.3). Reasoning levels are offered per model, and usage is priced from each host's published prices. DigitalOcean's Anthropic and OpenAI models need a DigitalOcean account on a tier that includes them. See providers.

Changed

  • A key that isn't a Tempr virtual key gets a 401 that says so. When the key you send doesn't start with tvk_, the invalid_api_key message now says it isn't a virtual key and, if it's a provider's API key, where to add that in the Portal. A management key (tmk_) is told it can't call models. The status, type and code are unchanged. See errors and the OpenCode guide, which now covers replacing a key saved with /connect.
VS Code

1.1.26 of VS Code, Oct 30, 2026

Latest

Added

  • Turn web search off. Settings > Tools & agents now has a Web search switch, on by default. Off, the agent can still open a page, but not search the web for one. Each search is billed to the model provider's key, or to your Perplexity key on models whose provider has no search of its own (about $1 per 1,000 searches).
JetBrains

1.1.26 of JetBrains, Oct 30, 2026

Latest

Added

  • Turn web search off. Settings > Tools & agents now has a Web search switch, on by default. Off, the agent can still open a page, but not search the web for one. Each search is billed to the model provider's key, or to your Perplexity key on models whose provider has no search of its own (about $1 per 1,000 searches).
Visual Studio

2.3.10 of Visual Studio, Oct 30, 2026

Latest

Added

  • Turn web search off. Settings > Tools & agents now has a Web search switch, on by default. Off, the agent can still open a page, but not search the web for one. Each search is billed to the model provider's key, or to your Perplexity key on models whose provider has no search of its own (about $1 per 1,000 searches).
CLI

Update of CLI, Oct 30, 2026

Latest

Added

  • Web search on every provider's models. A model whose provider has no search of its own, such as Groq, Cerebras, DeepSeek or Google, now searches the web through your Perplexity key, if you or your organization saved one. Each search returns up to five results with an extract of each page, shows as Searching the web for "…", and costs $1 per 1,000 searches on that key; the cost the CLI and the Portal show includes it. Anthropic, OpenAI and xAI models keep their provider's own search. --no-search and tempr config set-web-search off turn it off as before. It works the same in Tempr Code and the IDE extensions' agent, with no update needed. Where an organization limits its members' models, search needs perplexity/search (or perplexity/*) on the list. See Web search.
Portal

Update of Portal, Oct 30, 2026

Added

  • DigitalOcean and SiliconFlow are now available as provider keys for Chat, the Gateway and organization keys.

Changed

  • A Perplexity key also gives the agent web search on models whose provider has none of its own, and the API keys and organization keys pages say so. Each search is $1 per 1,000 on that key and shows in your usage as perplexity/search.
Gateway

Update of Gateway, Oct 29, 2026

Fixed

  • An MCP server's error in an unexpected shape no longer becomes a server error. If a server behind the MCP connector refuses a call with a JSON body that isn't an object, the connector now passes the refusal on instead of failing with a 500.
Portal

Update of Portal, Oct 29, 2026

Changed

  • Verify your email to use the Portal. Until your address is verified, signing in takes you to "Verify your email", where you can send the link again. Your profile and closing your account stay open. Setting your first password from an emailed link, or accepting an emailed team invite, counts as verifying.
  • Apps can't sign in with an unverified account. An app asking to connect to your MCP servers, or to the Gateway's MCP server, is turned away until the email is verified, and an existing sign-in stops refreshing.
  • Sign-up needs an address that can receive mail. Addresses at reserved names such as example.com or .test are refused.

Fixed

  • Opening the error page directly now says "Page not found" instead of reporting a server error.
Gateway

Update of Gateway, Oct 28, 2026

Fixed

  • The placeholder model's answer no longer counts as your first working request. If your tool has only reached tempr/add-a-provider-key, saving a provider key now offers the test message, and the onboarding reminder to add a provider key still arrives.
Portal

Update of Portal, Oct 28, 2026

Changed

  • Checkboxes and radio buttons are bigger on a phone, 18 pixels instead of 14, and small on/off switches are as tall, so they are easier to tap. Tablets and computers look the same as before.

Fixed

  • A new agent playbook rule on a phone: the "What the agent reads" preview no longer covers the Type choices below it.
  • Cloud agent tasks on a phone: the status filter fits inside its card.
  • New Tool Pack on a phone: Save pack stays on one line.
Portal

Update of Portal, Oct 27, 2026

Changed

  • On a phone, model names and keys in tables stay on one line. A table too wide for the screen scrolls sideways, instead of breaking a name like claude-sonnet-5-5 at every hyphen.
  • A week with no usage shows one short note. The "This week's usage" card on the Agents dashboard says there's no usage yet, instead of showing three empty charts.
  • Small links are easier to tap, such as Manage plan, Forgot password? and the dates in tables.
Website

Update of Website, Oct 27, 2026

Fixed

  • Footer links are only as wide as their words. Each one used to stretch across its whole column, so a click in the empty space beside it followed it. The Terms, Privacy, Cookies and EULA links are taller, so they are easier to tap on a phone.
  • The menu on a phone scrolls. With Products or Resources open it ran past the bottom of the screen, so its last links and Sign in could not be reached. Sign in is also bigger, lines up with the menu, and is no longer hidden behind the cookie notice while the menu is open.
  • Pages fit a phone screen. Wide tables in the docs scroll sideways on their own, and long names and addresses in code wrap, so no page scrolls sideways any more. The screenshot dots, the search boxes on the providers, models and MCP pages, and the Copy buttons on code are easier to tap.
  • The pricing table fits a tablet. At 768px wide all four Gateway plans show side by side, with their names pinned while you scroll, instead of the page scrolling sideways. Sign in in the header is easier to tap.
VS Code

1.1.25 of VS Code, Oct 26, 2026

Security

  • Safer connections to MCP servers. Tempr's MCP library is updated to 1.32.2, with fixes for its published advisories, among them sign-in details sent to a server the MCP server named and request headers sent on after a redirect to another site. The libraries it uses are updated too. MCP servers work as before.
Portal

Update of Portal, Oct 26, 2026

Added

  • A security contact. The Portal, the API and temprhq.io serve /.well-known/security.txt, which points security researchers to security@temprhq.io and to the vulnerability disclosure policy: what to include in a report, what's in scope, and what we commit to in return.
Website

Update of Website, Oct 26, 2026

Added

  • Claude Code on your team's Claude plans: how a team runs Claude Code on each member's own Claude Pro or Max plan through Tempr, with request logs, limits, guardrails and a fallback model, and what Anthropic's terms say.
  • Tempr Chat for Visual Studio: the bring-your-own-key assistant in Visual Studio 2022 and 2026, its agent, chat and inline completion, and the 34 providers it works with.
Gateway

Update of Gateway, Oct 25, 2026

Changed

  • A bigger response cache, sized by plan. An account now keeps up to 1,000 cached responses on Free, 10,000 on Pro and 50,000 on Scale and Enterprise, up from 200 on every plan. Past that, the least recently used are dropped first, so an answer that keeps being served stays cached; before, the oldest written went first. An answer over 256 KB is served but not cached. See response caching.
  • A key with no provider key behind it lists a placeholder instead of nothing. GET /v1/models lists tempr/add-a-provider-key, so a tool's model picker shows a next step rather than an empty list, and a request for it gets an ordinary answer saying where to add a provider key, on chat completions, /v1/messages and /v1/responses, streamed or not. It calls no model and costs nothing, and your logs show it as no_provider_keys. The placeholder goes once you add a key. See models.
CLI

0.9.22 of CLI, Oct 25, 2026

Changed

  • tempr run on its own with no terminal and nothing piped in, while signed out, now says how to sign in and exits with 0 instead of 3, as most command-line tools do. A prompt, --json or piped input while signed out still exits with 3.
  • Clearer wording in the model list, the README and the instructions the agent works from.

Fixed

  • Output when piped on some Linux hosts. Where TERM=linux and the output went to a pipe, every command printed nothing, tempr --version included. The CLI now prints at 80 columns there.
Portal

Update of Portal, Oct 25, 2026

Changed

  • Search engines index only the sign-in and sign-up pages. Every other Portal page is behind sign-in and now asks not to be indexed, and the sign-in page has one address for search results, whatever page it returns you to.
Website

Update of Website, Oct 25, 2026

Changed

  • Pricing says when Scale is worth it over Pro, with the arithmetic, and where single sign-on comes from: Gateway Enterprise, or Agents Teams.
  • Tempr is on Reddit: the footer links to r/TemprHQ, next to X, Bluesky and LinkedIn.
  • The privacy policy names the dates we keep on your account that outlast the Gateway's logs: when you first added a provider key and last removed one, when your keys first sent a request and first got an answer, and the last time an app listed your models while you had no provider key for them. They're deleted with your account.

Fixed

  • www.temprhq.io takes you to temprhq.io. It used to show every page at both addresses.
  • The page-not-found page answers as not found at its own address too, so search engines don't treat it as a page.
Gateway

Update of Gateway, Oct 24, 2026

Changed

  • A provider that refuses your stored key says so. When a provider answers 401 to the API key you stored in Tempr, the error keeps the 401 but names the provider and links Gateway provider keys, with code provider_auth_failed (see errors). This applies on chat completions, /v1/messages and /v1/responses, streamed or not. A 401 to your own Claude login or plan key, sent with the request, comes back as the provider sent it, so your client can sign in again.
  • Ollama Cloud's models match what ollama.com lists today: 23, up from 11, adding GLM-5.2, Kimi K2.6, MiniMax M3.1 Flash and M2.7, gpt-oss 20b, Mistral Large 3, Nemotron 3 Ultra and Nano, and others. See coding plans.
  • Quota alert headlines read slightly differently, in the alert email and in the headline of a gateway.quota_alert webhook: "Monthly request quota reached; new requests are refused until it resets", "Monthly request quota reached; overage billing applies" and "Overage at 1,200 requests, approaching your $50.00 cap". If something of yours matches on the headline, match on the event's stage instead: 1 at 80% of the quota, 2 at the quota, 3 close to the overage cap.
VS Code

1.1.24 of VS Code, Oct 24, 2026

Changed

  • Clearer wording. Error and sign-in messages, slash-command help, What's new and the Marketplace page read more plainly, and so do the instructions the agent works from.
JetBrains

1.1.24 of JetBrains, Oct 24, 2026

Changed

  • Clearer wording. Error and sign-in messages, slash-command help and the release notes read more plainly, and so do the instructions the agent works from.
Visual Studio

2.3.9 of Visual Studio, Oct 24, 2026

Changed

  • Clearer wording. Error and approval messages, What's new and the Marketplace page read more plainly, and so do the instructions the agent works from.
Portal

Update of Portal, Oct 24, 2026

Changed

  • Coding plans have their own section on Gateway provider keys, after the API providers, ending with a note that Claude and ChatGPT plans have no key to save: their sign-in stays in Claude Code or Codex. An organization's keys page groups its provider list the same way.
Website

Update of Website, Oct 24, 2026

Added

  • Providers lists the AI plans the Gateway works with: Claude Code on a Claude plan, Codex on a ChatGPT plan, and the coding plans, such as Ollama Cloud, Synthetic and the Z.AI GLM Coding Plan, each linking to its models, APIs and key on the coding plans page.

Changed

  • Section labels start with a small dot instead of a short line, on every page and in the preview image when you share a link.
  • Search results show each page whole. Page titles and summaries are short enough that search engines no longer cut them off, and the questions on the home, product and solution pages are marked up for search and answer engines.
  • Pricing lists member groups, each with its own budget and models, in the Agents Teams plan.
  • The FAQ and the docs describe Tempr as it is today: the Gateway for every AI tool your team uses, with Tempr's own agents on the same keys and rules, and 34 providers.
Portal

Update of Portal, Oct 22, 2026

Changed

  • A member group's budget, models and team key settings need the plan too: on a plan without member groups, the ones you set keep applying, but they can't be changed until you upgrade.
Portal

Update of Portal, Oct 21, 2026

Added

  • Popular remote MCP servers in "Add a server". The catalog list now offers 60 remote servers, such as Linear, Notion, Sentry, Atlassian, Stripe, GitHub, Datadog and GitLab, with their URL filled in. For the 49 that sign people in with OAuth, member sign-in is turned on as you save, so each member signs in with their own account. Asana, Box and HubSpot need an OAuth app you register, GitHub takes a token, and seven need no sign-in. Search the MCP registry below the list finds more remote servers from the official MCP registry, which Tempr hasn’t checked; picking one fills in its URL and headers, and turns member sign-in on if the server asks for it. A server on the publisher's own domain says so and ranks ahead of equally good matches; ones that run on Smithery's servers or charge per call come last, with a note. See remote servers.

Changed

  • Tool Packs and member groups come with Gateway Pro, Scale and Enterprise, and Tempr Agents Teams, as the pricing page says. On another plan, packs and groups you already have keep applying and can be deleted, but they can't be created or changed, and nobody can be added to or removed from a group, until you upgrade.
  • Removing an MCP server signs its members out with the provider first, as Sign out does, so their tokens stop working there too.
  • Your first request happens where you saved the key. After your first provider key, "Send a test message" sends one through the Gateway on the Provider keys page and shows the reply, or what went wrong. Then "Use it in your tool" creates a key and shows its setup for curl, Python, Node, Claude Code, OpenCode and Cursor on the same page. The Playground is still a click away.
Website

Update of Website, Oct 21, 2026

Added

  • Govern MCP tools shows per-tool permissions: a Tool Pack names tools one by one and goes to a group, a member or a key. Its FAQ says which plans include Tool Packs.
  • Datadog and Splunk on the integrations page, with a recipe for streaming request logs, agent traces and the audit log to them through an OpenTelemetry Collector in the Gateway reference.
  • The Portal's catalog of 60 remote MCP servers, such as Linear, Notion, Sentry, Atlassian and Stripe, with the URL and sign-in filled in, on the home page, the Gateway, Govern MCP tools, integrations, MCP servers and Compare pages.
  • Pricing lists Tool Packs in the Agents Teams plan.
  • Every Gateway plan compared lists the remote server catalog on every plan and Datadog or Splunk among Enterprise's log streaming destinations, and says cloud agents in your own cloud account are coming soon.

Changed

  • The header's Product menu is now Products, like Solutions and Resources beside it, and so is its column in the footer.
Portal

Update of Portal, Oct 19, 2026

Added

  • The key setup email. When a Gateway key keeps failing for a reason you can fix, or is refused, the email names the problem and links to the fix, at most once a week per key. Turn it off under "Key setup problems" in Gateway settings.
Website

Update of Website, Oct 19, 2026

Changed

  • The preview image when you share a temprhq.io link names Tempr Agents, next to the coding tools it works with.
  • The Gateway FAQ answers whether you can run cloud agents in your own AWS, Google Cloud or Azure account: it's coming soon, and today you can run Claude Code or OpenCode headless in your own CI or containers with a virtual key.
Gateway

Update of Gateway, Oct 18, 2026

Changed

  • Errors say how to fix them. A missing or invalid key links where to create one and to sign up. 402 provider_key_required names the provider, links Gateway provider keys, and lists the providers your keys cover, as 400 model_not_found does. Every OpenAI-shaped error carries a doc_url to its entry in errors. Status codes, types and codes are unchanged.
  • GET /v1/models for an account with no provider keys still answers an empty list, now with an x-tempr-hint header saying why.
VS Code

1.1.23 of VS Code, Oct 18, 2026

Changed

  • An empty model list says why. When you're signed in but haven't added a provider key yet, the model list says "No models yet: add a provider key" instead of opening to nothing. Its menu offers Add a provider key, which opens your provider keys in the Tempr Portal, and Check again, which fetches the list again once you've added one.
  • The walkthrough says where provider keys go. Get Started with Tempr now links to Provider keys in the Tempr Portal, and says a single OpenRouter key works for Chat (the Tempr Gateway doesn't take OpenRouter keys).
JetBrains

1.1.23 of JetBrains, Oct 18, 2026

Changed

  • An empty model list says why. When you're signed in but haven't added a provider key yet, the model list says "No models yet: add a provider key" instead of opening to nothing. Its menu offers Add a provider key, which opens your provider keys in the Tempr Portal, and Check again, which fetches the list again once you've added one.
Portal

Update of Portal, Oct 18, 2026

Added

  • A new key shows how to use it. Next to the key's secret: the base URL, and ready-to-copy setup for curl, Python, Node, Claude Code, OpenCode and Cursor, with your key and a model your provider keys can call. Until you've added a provider key, it says so first.
  • "Send a test request" after you save your first provider key opens the Playground with one of that provider's models chosen. Before any provider key, the Playground says what it needs instead of sending you elsewhere.
  • Onboarding tips: a welcome email when you verify a new Gateway account, and one reminder a day later if no request has worked yet. Turn them off on your Profile page.

Changed

  • A new sidebar. Gateway, Agents, MCP, Organization and Account are areas that fold open, with the one you're in open and any you open yourself kept open from page to page. Both products are listed together (no more switching between Chat and Gateway), each shared page appears once, and Get started stays at the top until you're set up.
  • Names that match across products: each product starts with its Dashboard, its own keys (Gateway keys, License keys) and Provider keys; Chat is now Agents, its plan the Agents plan, and Feature requests is in Account.
  • Signing in with both plans takes you to the Gateway dashboard; with only the Agents plan, to the Agents dashboard.
  • The plan you buy for Tempr Chat and the CLI is now the Agents plan: Agents Standard, Agents Pro and Agents Teams, on the pricing page, at sign-up, on your licenses and seats, and in the emails about your subscription. The plans, prices and what they include are the same, and the IDE extension is still called Tempr Chat.
  • Guardrails have their own page in the Gateway sidebar, and Team guardrails for an organization: the request and answer checks, the LLM check, your data-loss prevention rules and the guardrail tester, with the keys that set their own guardrails and the last 7 days of blocked and flagged requests. Settings keeps logs, caching, plan logins, overage, budget rules and alerts.
  • Card icons are in the site's blue, so a page of cards reads by section at a glance.
  • The Gateway's Quickstart starts with a provider key, and its example request uses a model one of your provider keys can call.
  • Creating a key asks only for a label; budgets, limits and the rest are under Advanced.
  • The two provider-key pages are named "Agent provider keys" and "Gateway provider keys", and Get started shows a Gateway-only account the Gateway's steps.
  • Signing in before verifying your email shows a page to resend the link.
  • An OpenRouter key saved for the Gateway, which the Gateway hasn't used since October 16, is flagged at the top of Gateway provider keys and on the Quickstart.
  • No provider key? The dashboard says you can use a Claude, ChatGPT or coding plan you already pay for.
Website

Update of Website, Oct 18, 2026

Changed

  • The Chat plans are now the Agents plans. One plan covers Tempr's agents, Tempr Chat in your IDE and the CLI: Agents Standard, Pro and Teams on the pricing page, the FAQ, the CLI and Chat pages and the comparison pages. Prices and what each plan includes haven't changed, and the IDE extension keeps its name, Tempr Chat.
  • The Gateway quickstart follows the Portal: sign up free, add a provider key, make a key, send a request. It shows how to list what your keys can call, what a 402 means, and how to use a plan you already pay for without a provider key.
  • Every tool guide says which provider key its example model needs, and the OpenCode guide what a 401 means there.
  • Errors has a link for every error code, and the privacy policy names the onboarding tips emails.
  • Models says the OpenRouter rows are for Chat and the CLI, not the Gateway.

Fixed

  • Outline buttons on dark sections, like Compare setups on the home page, keep a white label you can read, at rest and when you point at them.
  • The Gateway reference and management API pages each carried two copies of their dates for search engines, which disagreed; each now has one, with the date the page last changed.
VS Code

1.1.22 of VS Code, Oct 17, 2026

Fixed

  • Inline completion comes back on its own. When it pauses after repeated failures, it now tries one request every 5 minutes and picks up again as soon as one works, so a short drop in your connection no longer turns it off for the rest of the session.
  • Try again after a failed turn. A turn that failed now offers Try again, which runs it again without sending your message twice, and the error's Regenerate button does the same. A model list that failed to load offers Try again too, instead of asking you to reopen the view.
  • Deleted chats stay deleted. A synced chat deleted while Tempr's server couldn't be reached came back on the next start. The delete is now kept and sent again until the server confirms it.
  • Chat sync, custom agents and the MCP catalog stay signed in. They now renew your sign-in when it runs out, as the chat does, and give up after 30 seconds instead of waiting on a server that never answers. Signing in with a license key also gives up after 30 seconds and says so, and your custom agents are fetched again at start if the first try fails for a moment.
  • A turn is never started twice. Starting a chat is now sent again only when the connection was refused or Tempr was busy, not after a server error that could follow a turn that had already started.
  • Notices from Tempr are plain text. A notice can no longer carry links that run commands or open files; its only link is the Open button for its web page. A damaged notices file is ignored instead of breaking inline completion, and a pause Tempr sets for your version holds from the moment VS Code starts.
VS Code

1.1.21 of VS Code, Oct 17, 2026

Changed

  • Tempr can tell you about a problem in your version. When a version has a known problem, VS Code shows a short message with a link to the fix, at most once a day. If a feature misbehaves in one version, Tempr can pause it there (inline completion, uploads of your chats, automatic error reports) until an update fixes it, and tells you once.

Fixed

  • You stay signed in. When your sign-in runs out, Tempr renews it quietly and sends the request again; if the server has ended it, Tempr signs in again with your saved license key. Only when both are refused does it ask you to re-enter your key. A moment without a connection no longer signs you out.
  • A dropped connection is tried again. Requests that fail for a moment are tried again with growing waits, honoring the server's Retry-After, and a chat whose connection drops reconnects instead of ending. Starting a chat is only sent again when it can't have reached Tempr, so a turn is never started twice.
  • Stop works right away. Pressing Stop before a turn has started now cancels it as soon as it does, and Stop ends a reconnect wait at once.
  • MCP servers that fail to start are tried again, then named in one notice with Try again. Your organization's MCP tools keep working past 15 minutes, and an MCP error no longer leaves its process running.
  • Inline completion pauses after repeated failures. After three failures in a row it pauses for the session, with a notice and Try again.
JetBrains

1.1.22 of JetBrains, Oct 17, 2026

Fixed

  • A lost answer no longer signs you out. If the answer to renewing your sign-in never arrived, Tempr signed you out although your license key was saved. It now keeps the sign-in it has, and if the server refuses it, signs in again quietly with your saved license key. Two IDEs that share a sign-in no longer push each other out of it.
  • A renewal that fails for a moment is tried again. When the server can't be reached for a moment, the turn tries again or reconnects, instead of ending with "Tempr didn't accept your sign-in".
  • An ended sign-in shows as signed out. The settings page and the chat now say your sign-in has ended, instead of showing you signed in while every request failed.
  • A turn is never started twice. Starting a chat is now sent again only when the connection was refused or Tempr was busy, not after a server error that could follow a turn that had already started.
  • Stop cancels a turn that hasn't started yet. Pressing Stop right after sending left that turn running on the server for a few minutes; it's now cancelled as soon as it starts.
  • A long tool call no longer ends the turn. A tool that ran for more than about 12 minutes made the turn fail while it was still running; the chat now waits for it.
  • Inline completion comes back on its own. When it pauses after repeated failures, it now tries one request every 5 minutes and picks up again as soon as one works.
  • MCP servers start together. One slow MCP server no longer holds up the others. A restarted server no longer leaves its old process running, and a server Tempr gives up on is always named in a notification.
  • Deleted chats stay deleted. A synced chat deleted while Tempr's server couldn't be reached came back on the next start. The delete is now kept and sent again until the server confirms it.
  • Every chat panel crash says so. Once you closed the Reload notification without reloading, later page failures showed nothing; each one now shows its notification.
  • A pause Tempr sets for your version holds from the start, before the IDE has finished opening, and a notice shown once isn't shown again when Tempr can't save that it showed it.
JetBrains

1.1.21 of JetBrains, Oct 17, 2026

Changed

  • Tempr can tell you about a problem in your version. When a version has a known problem, the IDE shows a short notification with a link to the fix, at most once a day. If a feature misbehaves in one version, Tempr can pause it there (inline completion, uploads of your chats, automatic error reports) until an update fixes it, and tells you once.

Fixed

  • You stay signed in. Every project window shares one sign-in, so windows no longer race to renew it and lose. A long turn, inline completion and your organization's MCP tools keep working past 15 minutes. If Tempr has ended your sign-in, the chat says to sign in again instead of failing quietly.
  • A dropped connection is tried again. Starting a chat, tool results and approvals are sent again when a request fails for a moment, and a chat whose connection drops reconnects with growing waits. Starting a chat is only sent again when it can't have reached Tempr, so a turn is never started twice.
  • Stop stops everything. Stop now also ends a slow MCP server's start and the workspace search, and MCP servers get 30 seconds to start before the turn goes on without them.
  • MCP servers that fail to start are tried again. After three failures, a notification names them, with Try again.
  • Inline completion pauses after repeated failures. After five failures in a row it pauses for the session, with a notice and Try again.
  • The chat panel recovers. If it can't be built, it offers Try again; if its page fails to load or crashes, it offers Reload. Tempr no longer starts the chat's browser while a project opens.
  • Workspace search stays complete. A file whose search embedding failed is tried again later, instead of being skipped until you edit it.
Visual Studio

2.3.8 of Visual Studio, Oct 17, 2026

Fixed

  • A turn is never run twice. When starting a chat failed after the request may have reached Tempr, Visual Studio also ran the turn on its own, so it ran twice. It now does that only when the request never reached Tempr, and otherwise says to send the message again.
  • Reconnecting stops when it can't work. When a chat's run is gone or your sign-in was refused, reconnecting now stops at once and says why, instead of trying five times and saying the connection was lost. A busy server's Retry-After is honored.
  • The right message when a server behind Tempr refuses a request. When an MCP server or a provider refuses a request, the chat shows its own message instead of saying your sign-in ran out, and Tempr no longer renews your sign-in for every such call.
  • Long agent turns aren't cut short. A step tried again after a renewal or a dropped stream no longer counts toward the turn's step limit.
  • Certificate problems say so. A TLS or proxy certificate failure is no longer tried again as if you were offline, and the message says it's a certificate or proxy problem.
  • Fewer ways for Tempr to disturb Visual Studio. A failed read of your saved sign-in can no longer end Visual Studio from the renewal timer, or sign you out.
  • Your organization's rules stay. A moment offline no longer clears your organization's rules and skills.
  • Notices show without the chat window, as plain text. A notice from Tempr now shows in Visual Studio's info bar when the chat window isn't open, and as plain text, with only a web link to open. A damaged notices file no longer breaks inline completion, and a notice shown once isn't shown again when Tempr can't save that it showed it.
  • A pause on chat uploads pauses only uploads. When Tempr pauses uploads of your chats in a version, your chats, custom agents and tool preferences still come down from the server, as in the other IDEs.
  • Chat sync catches up. A chat that couldn't be uploaded is sent again at start or on its next save, a new chat saved twice in quick succession makes one copy on the server, and a chat deleted while offline no longer comes back.
Visual Studio

2.3.7 of Visual Studio, Oct 17, 2026

Changed

  • Tempr can tell you about a problem in your version. When a version has a known problem, the chat shows a short notice with a link to the fix, at most once a day. If a feature misbehaves in one version, Tempr can pause it there (inline completion, uploads of your chats, automatic error reports) until an update fixes it, and tells you once.

Fixed

  • You stay signed in. Tempr renews your sign-in on its own, also while the chat window is closed, so inline completion and inline chat no longer stop after 15 minutes with "Your license session has expired." A moment without a connection no longer signs you out or uses up an activation.
  • A dropped connection is tried again. A request that fails for a moment, because the server is busy or the connection dropped, is tried again before you see an error, and a chat whose connection drops picks up where it left off. Starting a chat is only sent again when the first try never reached Tempr, so a turn is never started twice.
  • When the chat view stops working, it says so. If the chat view's browser process ends, the chat area says it stopped working and offers Try again, which starts it afresh. The settings screen gets the same retries as the chat.
  • Inline completion pauses after repeated failures. After three failures in a row it pauses for the session, with a notice and Try again, instead of failing on every pause in typing.
  • Fewer ways for Tempr to disturb Visual Studio. Clicks and Visual Studio automation calls that could throw are now caught, and a failed error report no longer files another one.
CLI

0.9.21 of CLI, Oct 17, 2026

Added

  • Notices from Tempr. A chat's first line can carry a notice about your version, such as a known problem and its fix. Tempr can also switch a feature off for one version without a release (local models, or automatic error reports), and the CLI says so when it does; tempr doctor checks for the latest.
  • /mcp restart <name> starts an MCP server again; /mcp shows which ones are off.

Fixed

  • A dropped connection no longer ends the turn. The CLI reattaches to the running turn, retrying with backoff for a few minutes, and resends the answers and approvals that didn't get through.
  • Sign-in renews quietly and keeps you signed in. A sign-in that expires mid-session renews and the request goes again; a renewal that can't reach Tempr for a moment is retried and no longer signs you out, in a chat or in tempr acp. If Tempr refuses the renewal, the CLI signs in again with your license key (TEMPR_LICENSE_KEY, or the key you gave tempr auth, now kept encrypted) before giving up. In CI, a key is reported as rejected only when Tempr turned it down, not when Tempr couldn't be reached.
  • An MCP server that stops answering no longer holds up the turn. Each call has a deadline, and after three failures in a row the server's tools are turned off with a notice saying how to start it again. A server that failed to start is tried again, and your organization's assigned servers arrive once they can be fetched.
  • A local model that doesn't answer no longer hangs the turn. Connecting has 10 seconds, the first answer 5 minutes, and a stalled answer 2 minutes, each with a message naming the server.
  • tempr acp's MCP and language servers stop with it, even when the editor kills it.
  • An image that was too big no longer fails every later message. The message stays in the conversation without its images, and the error says what to do.
  • Ctrl+C during /compact, a summary or a slash command stops only that, and a failed step in a chat prints one line instead of ending the session.
Portal

Update of Portal, Oct 17, 2026

Added

  • Gateway keys say what's stopping them. A key whose requests keep failing for a reason you can fix shows the problem under it on Keys (and on an organization's shared keys), with a link to the fix: no key stored for a provider, a provider that refused your stored key, a model the key doesn't allow, a model name the Gateway doesn't know, or a key used after it expired or was revoked, or from an address it doesn't allow. A problem goes away once it's fixed. The dashboard names the keys that need attention.

Changed

  • The logs' Status filter has "no provider key" and "provider refused the key".
Website

Update of Website, Oct 17, 2026

Changed

  • The Gateway reference says what the Portal shows when something keeps a key from working: each problem it finds, how far back it looks, and when a problem goes away.
  • The privacy policy is corrected on error reports: the JetBrains plugin sends them by default, as the Visual Studio and VS Code extensions do, not only when you click "Report to Tempr". It also says what we keep for each distinct error after its reports are deleted: a summary made from its first report, with keys, tokens and email addresses removed.
  • The privacy policy says what a key keeps when the Gateway refuses it before anything is logged (expired, revoked, or used from an address it doesn't allow): only the time of the last refusal and its reason, not the address.
Gateway

Update of Gateway, Oct 16, 2026

Added

  • A public model catalog: GET /v1/catalog lists every model the Gateway serves on your own provider key, with prices, context sizes and the reasoning controls Tempr takes for each, and needs no key. It uses OpenRouter's model-list shape plus a tempr object, is rebuilt hourly, and answers If-None-Match with 304. See model catalog. /v1/models is still the list of what your key can call.

Removed

  • OpenRouter as a Gateway provider. The Gateway takes the keys you hold with each provider, as the FAQ says, so a request naming an openrouter/… model now gets 400 unsupported_provider on chat completions, /v1/responses, /v1/messages and /v1/embeddings (see errors). OpenRouter models are no longer listed in /v1/models, a fallback chain skips them, and they can't be a key's default or used-up model. Gateway → Provider keys no longer takes an OpenRouter key. OpenRouter keeps working in Tempr Chat and the CLI, and an OpenRouter key you already saved stays for them.
Visual Studio

2.3.6 of Visual Studio, Oct 16, 2026

Fixed

  • Visual Studio no longer closes when Tempr's chat view can't start. If WebView2, which shows the chat, failed to start, as can happen while another Visual Studio window is closing, Visual Studio itself shut down. Tempr now tries again twice, and if the chat view still can't start, the chat area says so and offers Try again. Your chats are kept and come back when it starts.
  • Error reports are only about Tempr, and say which version sent them. Automatic error reports also picked up crashes in other extensions, and always gave the version as 1.0.0.0. They now cover only Tempr's own errors and carry the version you're running.
CLI

0.9.20 of CLI, Oct 16, 2026

Added

  • Plugins from every Claude Code source. Besides a marketplace folder, GitHub and git, a plugin can now come from an npm package (its install scripts never run), a zip over HTTPS (its sha256 checked), or a command that prints its folder. A command is shown to you first and runs only when you say yes; tempr plugin install <name> --yes accepts it where nothing can ask.
  • Plugin settings. A plugin that asks for values (userConfig) asks when you install it, tempr plugin config <name> shows or changes them, and tempr plugin list shows what still needs setting. Sensitive values are kept encrypted, never in settings.json. MCP bundles (.mcpb) in a plugin become MCP servers.
  • Agent hooks ("type": "agent") check the work with a model that can read and search the workspace before it answers; its "no" goes back to the agent as feedback. Hooks can also run a program directly with "args", with no shell.
  • SubagentStart and SubagentStop hooks. SubagentStart adds context to a subagent; blocking SubagentStop keeps it going, up to 3 times.
CLI

0.9.19 of CLI, Oct 16, 2026

Changed

  • Your organization can turn local models off. When an owner or admin turns them off in the Portal (Agent playbook > Models), tempr models lists none and says so, and a turn on one is refused before anything is sent to the model's server. tempr doctor flags a local default model, and tempr acp leaves them out of the editor's model list too.
Portal

Update of Portal, Oct 16, 2026

Changed

  • A new look, matching temprhq.io: the Geist typeface, a navy sidebar with the Tempr wordmark, blue links and highlights, and dark primary buttons (white ones in the dark theme). The sign-in pages and the error page share the site's navy background.

Fixed

  • Gateway keys: a key's prefix (like tvk_…7e52) no longer breaks over several lines in the keys table.
Website

Update of Website, Oct 16, 2026

Changed

  • The OpenCode guide starts with your key. OpenCode already lists Tempr Gateway and its models, so /connect or TEMPR_API_KEY is all it needs. The guide also covers a minimal opencode.json, models outside OpenCode's catalog, the background requests small_model controls, and model-discovery plugins.
  • The privacy policy says how long server logs and error reports are kept. Server logs, including access logs, are kept 14 days. Each error report is kept 90 days at most, and only the latest 50 of any one error. It also says the servers record their own errors, and that Visual Studio versions up to 2.3.5 sent reports of other extensions' crashes, which have been deleted.

Fixed

  • temprhq.io/docs opens the docs. Without the trailing slash it showed a page-not-found, and so did any page address ending in a slash, such as /blog/.
  • Search engines get Tempr's logo as a clear square mark instead of a blurred wide image.
Gateway

Update of Gateway, Oct 15, 2026

Added

  • The Gateway's own MCP server, https://api.temprhq.io/mcp/admin, for Claude Code, Codex, claude.ai, ChatGPT and other MCP clients: read-only tools for usage and cost, request logs, one request's routing and its captured prompt and answer (secrets and personal data masked), keys, plan status, provider health and the guardrail tester. Send a management key, whose scopes decide the tools, or sign in through the app: you read your own Gateway, or your organization's as an owner or admin. Text from your apps, models and providers comes back marked as untrusted. Pro, Scale and Enterprise.
  • Key changes through the Gateway's MCP server, if you allow them: with a management key that has keys:write, an agent can create a key that expires within 90 days, tighten a key (a lower budget or rate limit, fewer models, an earlier expiry) or revoke one. A new key's secret never reaches the agent: it gets a one-time Portal link, valid 10 minutes, where you copy the key. At most 20 changes an hour, each in an organization's audit log.
  • Changes beyond reads through the Gateway's MCP server, while you allow changes by AI agents. An app you connect can make them too, if you tick "Also let it make changes" when you connect it. Agents can now read a key's end users and an organization's tool access requests and grants, cap or block an end user, decline a tool access request and revoke a grant. Anything that would loosen (a higher budget or limit, more models, a later expiry, another guardrail mode, lifting an end user's limits, approving tool access) an agent can only propose: it gets a Portal link, valid 24 hours, where you see each value beside the proposed one and approve or decline it.
  • Account settings by proposal: propose_account_settings asks to change your Gateway's guardrail modes, LLM check, redaction, content capture, log retention or prompt caching, within what your plan includes, for you to approve.
  • What became of a proposal: list_proposals on the Gateway's MCP server, and GET /v1/management/proposals and GET /v1/management/proposals/{id} (scope keys:read). A proposal made with a management key is also emailed to you, or to an organization's owners and admins, at most once an hour.
  • Plan status (GET /v1/management/plan, get_plan_status) shows the answer-scanning mode, the LLM check and prompt caching too.
  • Local models through the Gateway's MCP server, for an organization: get_agent_policies reads whether members' Tempr Code and CLI may use local models, turn_off_local_models turns them off, and propose_agent_policies asks an owner or admin to allow them again. The management API has GET and PATCH /v1/management/agent-config/settings (agent_config:read and agent_config:write).
  • Management API reads: GET /v1/management/logs with the Portal's filters and paging, GET /v1/management/logs/{request_id} (add include_content=true for the masked content; an organization's audit log records each read), GET /v1/management/metrics, GET /v1/management/plan and GET /v1/management/provider-health, and a logs:read scope for request logs.

Changed

  • Capping an end user through the MCP server sets a cap of the agent's own beside the end user's limits: it only ever lowers what applies, and setting their limits yourself replaces it. End users show caps in the management API.
  • Turning off Changes by AI agents withdraws every proposal still waiting, and nothing can be approved while it's off.
  • An app connected for an organization's Gateway is asked again on Tempr's consent page, which now lists the organization's agent policies, before it reads or changes them.
CLI

0.9.18 of CLI, Oct 15, 2026

Fixed

  • The plugin hints name the whole command, such as "tempr plugin marketplace add owner/repo" (or "/plugin …" in a chat); before, they left out tempr.
  • The README that comes with the CLI (in the download, and on npm and NuGet) now covers 0.9.17's features: local models, Claude Code's plugins, hooks and files, plan mode, worktrees, background commands, /compact, /rewind and history search.
CLI

0.9.17 of CLI, Oct 15, 2026

Added

  • Local models. The CLI finds Ollama and LM Studio running at their default ports; use one as --model ollama/<model>, and tempr models and tempr doctor list what they serve. Other OpenAI-compatible servers go under "provider" in ~/.tempr/settings.json, in OpenCode's shape with {env:NAME} for keys, and "disabled_providers" hides one. These turns run on your machine and cost nothing; they don't get sub-agents, web search or your organization's rules. --reasoning none or on turns thinking off or on for models that think. A tool call the model writes as plain text still runs as a call, and with Ollama the CLI tells you when a request didn't fit the model's real context window.
  • Plugins in Claude Code's format. tempr plugin install|uninstall|enable|disable|list and tempr plugin marketplace add|list|update|remove install plugins from Claude Code marketplaces (owner/repo, a git address, a folder or a marketplace.json); --plugin-dir <DIR> loads one from a folder for a single session, and /plugin lists them in a chat.
  • Hooks in Claude Code's format, on nine events (now also Notification, SessionEnd, PreCompact and PostCompact), including prompt hooks and PreToolUse's updatedInput. tempr hooks list shows them and /hooks in a chat; a folder's hooks, allow rules and .mcp.json servers wait until you run tempr hooks allow there, and ask again when they change.
  • Claude Code's project files work as they are: .claude/commands, .claude/agents, ~/.claude/skills and .mcp.json, plus lasting allow and deny rules in their settings files (/permissions lists the ones in force) and a to-do list the agent keeps.
  • Plan mode. --plan or /plan has the agent research with read-only tools and propose a plan; nothing changes until you approve it.
  • Worktrees. -w/--worktree <NAME> runs the session in a git worktree of its own on a new branch tempr/NAME; the same name goes back into it, and an empty one is removed when the session ends.
  • Background commands. The agent can start a command in the background and read its output or stop it later; /tasks lists them and /tasks stop <id> (or stop all) ends them. They stop when the session ends, and aren't available in the sandbox yet.
  • /compact [focus] summarizes the conversation so far to free up context, and a chat compacts by itself at 90% of the model's context. /rewind goes back to before an earlier message: the files its turns changed, the conversation from there on, or both (commands those turns ran can't be undone).
  • Code intelligence (LSP). Language servers from plugins or "lspServers" in ~/.tempr/settings.json report errors in the files the agent edits, and the agent can ask them about the code.
  • tempr history search <words> finds a session by what was said in it (--here for this folder's), and tempr history export (-o <file>) and /export [file] save one as Markdown. /init drafts an AGENTS.md for the project, as tempr init does.
  • "✻ Thought for Ns" shows when the model reasoned before a step; --verbose prints what it thought. In tempr acp, the editor gets the reasoning as thoughts, and there's a compact command.
Portal

Update of Portal, Oct 15, 2026

Added

  • The Gateway's MCP server on the MCP connectors page: its URL and setup, which Gateway it reads for you, and a switch for owners and admins to turn it off for the organization. Connected apps show what each one reaches.
  • Key changes by AI agents, a switch on the MCP connectors page (off until you turn it on), and a page to copy, once, the secret of a key an agent created.
  • Read request logs, a new scope for management keys.
  • The consent screen says which Gateway an app will read, with a box to let it make changes too (off unless you tick it).
  • Approving an AI agent's proposed change: a page that shows who proposed it, each setting beside the proposed value and the agent's note, with Approve and Decline. Changes waiting for approval are listed on the MCP connectors page, and connected apps show whether each may make changes.
  • The Compliance page shows which app a person acted through.
  • Approving account settings an agent proposed, each beside its current value, and an email when a management key proposes a change.
  • End users show a cap an AI agent set, and saving their limits or blocking them keeps the capped values as their own.

Changed

  • Changes by AI agents (formerly Key changes by AI agents) covers apps you let make changes as well as management keys, and the new end-user and tool access changes. Turning it off withdraws the changes still waiting for approval.
  • Connecting an app to the Gateway's MCP server again asks for consent once more if it was connected before the consent page listed what it now reads.
  • The consent screen for an organization's Gateway lists its agent policies (whether members may use local models), and the box to allow changes includes turning local models off.
  • Approving an AI agent's proposed change covers allowing local models again.

Fixed

  • The MCP connectors page's Gateway card showed stray text and a "turned off" warning to accounts on a paid plan.
Website

Update of Website, Oct 15, 2026

Added

  • A new temprhq.io. The site is rebuilt around one idea: let your team use any AI, and keep control of all of it. A new design on every page, with your AI plans, your keys, your guardrails and your agents' rules in one place.
  • New pages for what teams ask about: using your AI plans, controlling AI spend, keeping secrets out of AI, governing MCP tools and Tempr's agents.
  • Integrations lists every coding tool, AI plan, API, MCP app, identity provider and log destination Tempr works with, each with its logo and a link to its setup guide. Filter them by kind.
  • Every Gateway plan compared on Pricing: Free, Pro, Scale and Enterprise side by side, row by row, with the plan names pinned while you scroll.
  • A Resources menu in the header, with the blog, this changelog, models, providers, comparisons and the FAQ.
  • Tempr next to the AI gateways on Compare: Portkey, LiteLLM, OpenRouter and Cloudflare AI Gateway side by side, with when each one is the better pick and a link to every source.

Changed

  • The Gateway, Chat, CLI and Pricing pages are rebuilt in the new design. Screenshots open full size, the CLI's install steps, downloads and package managers sit together, and each plan's price and features are side by side.
  • Feature cards each have an icon of their own, and a card about one product shows its logo.
  • Fonts come from temprhq.io itself, so no page sends your browser to Google Fonts.
  • A new preview image when you share a temprhq.io link.
  • The coding-assistant comparisons are checked again: Cursor's plans, sold as X Subscription plans since October 12, and which of them take your own keys.
  • Providers are listed alphabetically, so the one you want is easy to find.

Fixed

  • Menus stay open while you move the pointer from a menu's name to its panel.
  • On phones, a menu opened inside the site menu is no longer hidden behind the Sign in and Start free buttons.
  • A link to part of a page lands just below the header instead of under it.
  • The header underlines the section you're in, Product, Solutions or Resources, on every page.
  • The Org rules & skills docs page fits a phone screen; its SKILL.md example used to scroll the whole page sideways.
Gateway

Update of Gateway, Oct 14, 2026

Added

  • Claude Code on your Claude plan. Leave Claude Code signed in to Claude Pro, Max, Team or Enterprise, set ANTHROPIC_BASE_URL to Tempr and send your virtual key in x-tempr-key: your plan pays for Claude, and each request is logged with the plan's 5-hour and weekly usage, a cost of $0 and what it would have cost at API prices. /v1/messages/count_tokens, HEAD /api/hello and /v1/models in Anthropic's shape (for CLAUDE_CODE_ENABLE_GATEWAY_MODEL_DISCOVERY) work with a virtual key too.
  • Codex on your ChatGPT plan. /backend-api/codex relays Codex's own ChatGPT sign-in to ChatGPT's Codex backend, so a Plus, Pro, Business, Enterprise or Edu plan pays for OpenAI's models. The model list and tools come from ChatGPT.
  • 30 coding plans as providers, each with its own id: Z.AI and Zhipu GLM, Kimi Code, MiniMax, Alibaba Cloud, Volcengine, BytePlus, Tencent, Xiaomi MiMo, StepFun, iFlytek and more (zai-coding/glm-5.3). Store the plan's key, or send it in Authorization with each request beside x-tempr-key. Claude Code can run on a plan with an Anthropic-compatible endpoint. Tempr forwards your tool's own User-Agent and never sends a different one.
  • A used-up model per key (when_used_up_model). When a plan says it's used up, or a dollar budget runs out, the request goes to this model instead of failing. A bad plan key or an outage doesn't hand over, so nothing is spent on the API by mistake.
  • Data-loss prevention rules for an account or team: values that are never flagged or masked, built-in categories turned off, and up to 20 patterns of your own. They apply to requests, answers, stored logs, the guardrail tester and MCP traffic.
  • More detectors: Anthropic, OpenAI project, GitHub, GitLab, Slack, Google, Stripe, npm and Tempr keys, and PEM private keys. Card numbers must pass the Luhn check. Four personal-data categories (phone, iban, ip-address, national-id) are checked once you turn them on.
  • Answer scanning. Flag or mask secrets and personal data in a model's answer before you see it, streams included, on chat completions, /v1/messages, /v1/responses and the Codex route. Set an account default and override it per key (response_guardrail_mode).
  • Budget rules. Up to five per key, team or account: an hour, day, week or month, a cost, token or request limit, and warn or block. Blocking answers 402 rule_budget_exceeded or 429 rule_limit_exceeded. A warning sends one gateway.budget_rule.warning webhook and one email per period, and later requests carry x-tempr-budget-warning.
  • Teams inside an organization. Put organization keys in a team with its own monthly budget, model list, budget rules and settings that owners and admins lock for every key in it (400 field_locked on a change). Over a team's hard cap: 402 group_budget_exceeded. Logs filter by team, and exports and streamed spans carry the team.
  • MCP connectors for claude.ai, ChatGPT, Claude Desktop and Claude Code. /mcp/connector gives an app every MCP server you can reach, and /mcp/connector/{server} gives it one. The app signs in to Tempr with OAuth 2.1 and PKCE, by a client metadata document or by registering itself, and every call goes through Tempr's MCP gateway with your credentials, Tool Packs, guardrails and logs. Organizations can turn connectors off or allow only listed apps. Enterprise Managed Auth signs in members of an organization with Team seats or Gateway Enterprise from their identity provider.
  • Tool description overrides. Rewrite an MCP tool's description for your organization, and every app and agent sees yours.
  • A default or forced model per key (default_model, force_default_model). A request without a model uses the default, and a forced one replaces the model asked for. The log keeps the model that was requested.
  • Balanced fallback chains spread requests across a chain's models, and keep a conversation on one model when it sends x-tempr-session-id or names an end user.
  • x-tempr-cost-usd on non-streamed answers, and 0 on a cache hit.
  • Stored OpenAI responses: GET and DELETE /v1/responses/{id}, GET /v1/responses/{id}/input_items and POST /v1/responses/{id}/cancel reach your OpenAI or Azure OpenAI key.
  • Log streaming has Langfuse and Opik presets. Every request span carries gen_ai.usage.cost, session.id and user.id, plus tempr.plan.kind, tempr.plan.value_usd and tempr.credential.source.
  • Management API: when_used_up_model, default_model, force_default_model, budget_rules, response_guardrail_mode and group_id on keys, and key_policy on groups.

Changed

  • What Free includes. Redaction, your own data-loss prevention rules, answer scanning, the LLM check and budget rules now come with Gateway Pro, Scale and Enterprise. On Free, guardrails flag or block with the built-in categories, and a key keeps its monthly budget and rate limits. Settings saved on a paid plan are kept and apply again after an upgrade; meanwhile a saved redact mode flags instead. Turning one on for an account on Free is refused with 403 plan_required.
  • Higher rate limits: 30 requests a minute on Free (was 10), 120 on Pro (was 60) and 480 on Scale (was 240), with the monthly quotas unchanged. Organization keys without a Gateway plan get Free's 30.

Fixed

  • Masking inside tool-call arguments keeps them valid JSON, and a secret right after an escaped line break is masked too.
  • Tempr's own keys are matched whole, so a tvk_ key with a hyphen or underscore in it is masked completely.
VS Code

1.1.20 of VS Code, Oct 14, 2026

Fixed

  • Signing out ends your session on the server. "Tempr: Sign Out" used to remove the sign-in from this machine only, so a copy of it kept working until it expired. It now ends the session on Tempr's server too. If the server can't be reached, it still signs this machine out and says so.
JetBrains

1.1.20 of JetBrains, Oct 14, 2026

Fixed

  • Signing out ends your session on the server. Sign out in Tempr's settings used to remove the sign-in from this machine only, so a copy of it kept working until it expired. It now ends the session on Tempr's server too. If the server can't be reached, it still signs this machine out and says so.
Visual Studio

2.3.5 of Visual Studio, Oct 14, 2026

Fixed

  • Deleting your license key ends your session on the server. Deleting the saved license key used to remove the sign-in from this machine only, so a copy of it kept working until it expired. It now ends the session on Tempr's server too. If the server can't be reached, it still signs this machine out and says so.
CLI

0.9.16 of CLI, Oct 14, 2026

Fixed

  • tempr logout now ends the session on the server too, so a copy of your sign-in can't be used afterwards; offline it still signs this machine out.
  • In tempr acp, the first message of a session can use your MCP tools; before, they could be missing until the second.
Portal

Update of Portal, Oct 14, 2026

Added

  • Plan logins: a setting for your account, your organization and each key that lets Claude Code and Codex use the member's own plan. An organization turns it on, since a plan login moves billing onto each member's plan.
  • When the plan or budget runs out: pick a key's used-up model on the key forms.
  • Coding plans among the Gateway's provider keys and on Org keys, and a Coding plans card on the dashboards with each plan's requests, value at API prices and latest usage.
  • Which plan paid on each request's page, with its usage windows; a "Paid by" filter on the logs; and the plan in the export.
  • Data-loss prevention rules and Answer scanning in the account and organization Gateway settings, with an answer-scanning override per key.
  • Budget rules on the key forms and in the account, organization and team settings, as lines such as day cost 20 block.
  • Team keys: on the Groups page, a team's budget, model list, budget rules and locked key settings, its keys and its spend. Org keys can be put in a team, and the team logs filter by team.
  • Default model on the key forms, with a switch to force it.
  • MCP connectors: connector URLs to copy, the apps you've connected (with Disconnect), and for owners and admins every member's apps, the organization's app list and Enterprise Managed Auth.
  • Your description for any MCP tool, on the Tool Packs page.
  • Langfuse and Opik presets for log streaming.

Changed

  • Pro controls on Free: the Gateway settings, Keys and Org keys pages show redaction, answer scanning, the LLM check, data-loss prevention rules and budget rules as Pro and up, mark any saved on a paid plan as not applied on Free, and refuse turning one on. Turning one off still works.
Portal

Update of Portal, Oct 13, 2026

Changed

  • Emails name the products as they are now: your Tempr account and the Tempr Portal, and Tempr Chat for the Chat plan. Every email with a license key says it signs you in to Tempr Chat in VS Code, Visual Studio or JetBrains and to the Tempr CLI.
  • A license key you asked to have resent arrives as a reminder, not as a purchase receipt, and says the key hasn't changed.

Fixed

  • A page you aren't allowed to open says "Not allowed" instead of "Page not found".
  • "Resend my license key" sends only keys that still work, not ones from a subscription that ended or an organization that removed you.
Gateway

Update of Gateway, Oct 10, 2026

Added

  • GCP Agent Platform (Vertex AI) as a provider. Bring a Google Cloud API key from Google's Gemini Enterprise Agent Platform and call Gemini models as gcp-agent-platform/google/gemini-2.5-pro, billed through your own Google Cloud project. The key goes to Google in a header, never in the URL. /v1/models lists the models you configured with the key; streaming, tool calls and reasoning levels work as with the Gemini API. Partner models on the platform, such as Claude, need a service account and aren't available yet.
Portal

Update of Portal, Oct 10, 2026

Added

  • GCP Agent Platform on the Provider keys, Org keys and Gateway keys pages: a Google Cloud API key plus the Gemini models you want, each checked against the key when you save, with a message saying whether the key or a model is the problem.

Changed

  • On Org keys, the Azure, AWS Bedrock and GCP Agent Platform fields only send what applies to the provider you picked.
Gateway

Update of Gateway, Oct 8, 2026

Added

  • Redact before the model. The pre-request guardrail has two new modes: redact_secrets replaces tokens, AWS keys and API secrets in a prompt with placeholders such as [REDACTED-AWS-KEY] before the model sees them, and redact_personal also replaces email addresses and card-like numbers. Only message text is changed (chat completions, /v1/messages, /v1/responses and embeddings); signed thinking blocks, tool schemas and images are left alone. Values aren't put back into the answer.
  • One guardrail for your members' own turns. An organization can flag, redact or block secrets and personal data in what its members send from the IDEs, the CLI and server-run agent turns, not only in Gateway API traffic.
  • x-tempr-guardrails says what the guardrail did to a request, as counts per kind (redacted=aws-key:1), never the values. Server-Timing gives Tempr's own time, the guardrails' time and the provider's time to first byte.
  • A reasoning policy per key: a default reasoning level plus the lowest and highest allowed. A request outside the range moves to the nearest allowed level and says so in x-tempr-reasoning-policy.
  • Group budgets and model access. A member group can have a monthly budget (soft alert or hard cap) and a list of models. Every budget on a member's path applies; a member may use the models any of their groups allows, within their own list. Over a hard cap: 402 group_budget_exceeded.
  • Requests for a tool. When a member's call is refused by Tool Packs, the relay's error now carries data.requestAccessUrl, a Portal page where they ask for the tool, and server-run turns add a Request access: line. Approved access lasts an hour, a day, a week or until revoked.
  • End-user limits for apps on the Gateway. Name your app's end user with x-tempr-end-user (or the request's own user field) and give each one a monthly budget and requests per minute on a key, with overrides or a block per end user. Errors end_user_budget_exceeded (402), end_user_rate_limit_exceeded (429) and end_user_blocked (403); x-tempr-end-user-budget-remaining on successful requests.
  • End-user ids are hashed before they reach a provider, per account, so a provider never sees your customers' ids.
  • Management API: reasoning_policy and end_user_limits on keys, budgets and models on groups, tool access requests and grants (list, approve, decline, revoke), and end users per key with their limits.
  • Cheapest or fastest fallback chains. A fallback chain can now try its models cheapest first for each request (by that request's estimated cost) or fastest first right now (by recent median time to first token), instead of in the order written: bulk (cheapest): …. Only the chain's own models are used, and a model that fails still hands over to the next. The response's x-tempr-fallback-order header and the request log say which order was used.
  • Management API: fallback_chains takes { "order": "cheapest", "models": [...] } (a plain list still means as written); keys read and write their MCP guardrail settings (mcp_argument_mode, mcp_result_mode, mcp_injection_mode); and POST /v1/management/guardrails/test shows what a key's guardrails would do with a piece of text, for checks in CI.

Fixed

  • Block and Flag catch a secret right after a line break in a JSON string; before, a key that followed an escaped newline could slip past both.
  • The LLM guardrail check works on reasoning models. On a model that thinks before it answers (gpt-oss, Qwen and others), the check ran out of room before its one-word answer and let every request through; it now has room to answer.
VS Code

1.1.19 of VS Code, Oct 8, 2026

Changed

  • Ask for a tool your organization's Tool Packs leave out. When a tool on one of your organization's MCP servers isn't in your Tool Packs, the tool call's "Not allowed by your organization" now comes with a Request access button, which opens a Portal page in your browser where you ask an owner or admin for it. Once they approve, your next turn can use it. The agent is told only that the tool can't be used, as before.
  • Access changes reach an open chat. A tool an owner or admin approves for you, or a change to your Tool Packs, now shows up on the next turn of a chat that's already open, without a reload.
JetBrains

1.1.19 of JetBrains, Oct 8, 2026

Changed

  • Ask for a tool your organization's Tool Packs leave out. When a tool on one of your organization's MCP servers isn't in your Tool Packs, its card now shows a Request access button next to "Not allowed by your organization". It opens a Portal page in your browser where you ask an owner or admin for the tool; once they approve, your next turn can use it. The agent is told only that the tool can't be used, as before.
  • Approved tools reach an open chat. A tool an owner or admin approves for you, or a change to your Tool Packs, now shows up on the next turn of a chat that's already open, without restarting the IDE.
Visual Studio

2.3.4 of Visual Studio, Oct 8, 2026

Changed

  • Ask for a tool your organization's Tool Packs leave out. When a tool on one of your organization's MCP servers isn't in your Tool Packs, the tool now shows a Request access button under "Your organization's Tool Packs don't include this tool." It opens a Portal page in your browser where you ask an owner or admin for the tool, and once they approve, your next turn can use it. The agent is told only that the tool isn't available, as before. An approved tool now shows up on the next turn of a chat that's already open.
CLI

0.9.15 of CLI, Oct 8, 2026

Changed

  • Ask for a tool your organization's Tool Packs leave out. When the agent calls a tool on one of your organization's MCP servers that your packs don't include, the CLI now prints "Request access: {link}" after "Your organization's Tool Packs don't include this tool." The link opens a Portal page where you ask an owner or admin for the tool; the CLI doesn't open it for you. Once they approve, your next turn can use it. That includes a chat that's already open, in tempr acp too: the tool shows up on its next turn, without restarting. In tempr acp, the editor gets the same link after the message. The agent is told only that the tool can't be used, as before.
Portal

Update of Portal, Oct 8, 2026

Added

  • Redaction in every guardrail setting: "Redact secrets" and "Redact secrets and personal data" next to Flag and Block, for your account, your organization and each key.
  • Guardrails for members' own turns: owners and admins choose how the organization checks what members send from the IDEs, the CLI and agent turns.
  • Group budgets and models: each group on the Groups page can have a monthly budget, soft alert or hard cap, with alerts at 80% and 100%, and a list of models its members may use.
  • Requests for a tool: a member who's refused a tool opens a page to ask for it, with a reason. Owners and admins see requests on a new Requests tab under Tool Packs, approve one for an hour, a day, a week or with no limit, decline with a note, and revoke access later. They get one email an hour at most when requests are waiting. Approved access ends on its own when its time is up.
  • End users: a new Gateway page lists the end users your apps send, with their requests, errors and spend per key, and lets you set each one's budget and rate or block them. The key editor sets the default limits for each end user.
  • Reasoning policy in the key editor: a default level and the lowest and highest allowed.
  • Test your guardrails. Next to every guardrail setting, paste text and see each match highlighted, the text after redaction, and whether the request or MCP tool call would be allowed, flagged, redacted or blocked, with the settings as they are on the form, saved or not. The text isn't kept. On your own settings and keys, you can also run the LLM check once with a model you pick.
  • Organization keys can be edited, with everything personal keys have, including fallback chains and the guardrail and MCP guardrail overrides, each showing what it would inherit.
  • The key editor shows each fallback chain's current ranking when it's ordered cheapest or fastest.
Gateway

Update of Gateway, Oct 7, 2026

Added

  • Org rules and skills in agent turns. Agent turns that run on Tempr's servers now carry the rules your organization publishes, before the workspace's own instructions, and list its skills, which the agent reads with a skill tool when a task matches one. Required rules always apply; members can switch off recommended ones. Rules and skills can go to everyone or to groups.
  • GET /config/agent gives a Tempr client the member's rules, skills, personas and slash commands in one response, with an ETag for 304s.
  • Management API: org rules and skills: create, change, order and assign rules and skills, upload a skill as a .zip, with an organization management key and the new agent_config:read and agent_config:write scopes.
  • MCP guardrails: the remote MCP relay now checks tool traffic in both directions. Secrets and personal data in a tool call's arguments are flagged (or blocked), the same in a tool's results are redacted before the model reads them (or flagged, or the result withheld), and text in results or tool descriptions shaped like instructions to the model is flagged (or withheld). Hidden Unicode characters are removed from results. Each request log row shows the MCP method, the tool, and what was flagged or redacted. Set the checks per account or organization, and override them per key.
  • Tool definitions are pinned. When a remote MCP server changes a tool's name, description or input schema, the change goes to your organization's audit log and to your Gateway webhook as mcp.tool_changed.
  • Per-member sign-in to remote MCP servers: a remote server can now sign each member in with their own account over OAuth, so tool calls run as that person instead of a shared token. Tempr registers itself with the server's OAuth provider (Client ID Metadata Document, dynamic registration, or an OAuth app you enter), keeps each member's tokens encrypted on its servers, and refreshes them. A member who hasn't signed in is asked to, with MCP's own sign-in request and a link to the Portal, on their first tool call; the Tempr clients that show it as a button ship separately.
  • New error codes mcp_connection_requires_user and mcp_sign_in_required.
  • MCP Tool Packs: an organization can give each member, group or key only the MCP tools it needs. The relay leaves tools outside someone's packs out of a server's tool list and refuses calls to them before they reach the server (-32601, logged as mcp_tool_not_allowed); a server with none of their tools is refused like a key's server allowlist. Agent turns that run on Tempr's servers never offer those tools to the model. An organization with no pack keeps today's access.
  • Management API: Tool Packs and groups: create, change and assign Tool Packs and member groups with an organization's management key.

Fixed

  • Server-run agent turns in an organization that never published its own personas had none to delegate to; they now get Tempr's, as the clients do.
  • The quota-reached alert (email and gateway.quota_alert webhook, stage 2) no longer says "overage billing applies" on an account with overage switched off or no overage cap; it says new requests are refused until the quota resets, which is what happens.
VS Code

1.1.18 of VS Code, Oct 7, 2026

Added

  • Your organization's rules and skills. When your organization publishes rules and skills for its agents, the agent follows its rules on every turn, next to your project's own instructions, and reads one of its skills when a task matches it. The Organization section of Tempr's settings lists them: switch off a recommended one there; a required one stays on.
  • Skills in your project. The agent finds skills in the standard SKILL.md format in .tempr/skills, .agents/skills and .claude/skills in your workspace, and in ~/.agents/skills, and reads one when a task matches it. A tool card shows "Skill: name" when it does.
  • AGENTS.md and other agents' files. Workspace instructions now come from AGENTS.md, CLAUDE.md, GEMINI.md, .cursorrules and Cursor's rules as well as .github/copilot-instructions.md, as in the CLI, and are read again on every turn.
VS Code

1.1.17 of VS Code, Oct 7, 2026

Added

  • Tool Packs: see which MCP tools your organization lets you use. If your organization uses Tool Packs, the MCP servers settings list your packs and mark the servers (and tools) that aren't in them as "Not in your Tool Packs", and your own servers as "Not managed by your organization" when only its servers are allowed.

Changed

  • A tool call your organization's Tool Packs don't include says so. The tool call shows "Not allowed by your organization" instead of a generic error, and the agent is told not to call it again.
VS Code

1.1.16 of VS Code, Oct 7, 2026

Changed

  • A remote MCP server that needs you to sign in shows a sign-in link. When a tool call needs you to sign in to its server first, the tool call shows "Sign-in needed" with a Sign in button, which opens the sign-in page in your browser, and a Retry button, which asks Tempr to try again once you've signed in. Before, the call just failed with an error.
JetBrains

1.1.18 of JetBrains, Oct 7, 2026

Added

  • Your organization's rules and skills. When your organization publishes rules and skills for its agents, the agent follows its rules on every turn, next to your project's own instructions, and reads one of its skills when a task matches it. The Organization section of Tempr's settings lists them: switch off a recommended one there; a required one stays on.
  • Skills in your project. The agent finds skills in the standard SKILL.md format in .tempr/skills, .agents/skills and .claude/skills in your workspace, and in ~/.agents/skills, and reads one when a task matches it. A tool card shows "Skill: name" when it does.
  • Slash commands. Type / in the chat for the commands your organization publishes, or Tempr's built-in ones, and your organization's personas replace the built-in ones.
  • AGENTS.md and other agents' files. Workspace instructions now come from AGENTS.md, CLAUDE.md, GEMINI.md, .cursorrules and Cursor's rules as well as .github/copilot-instructions.md, as in the CLI.
JetBrains

1.1.17 of JetBrains, Oct 7, 2026

Added

  • Tool Packs. When your organization limits the MCP tools you can use with Tool Packs, a tool outside your packs now shows "Not allowed by your organization" on its card instead of a bare error, and the agent is told not to call it again. The MCP settings show which of each server's tools your packs include. Each run also tells Tempr which of your organization's MCP servers a tool came from, so the right pack applies even when two servers have similar names.
JetBrains

1.1.16 of JetBrains, Oct 7, 2026

Added

  • Signing in to a remote MCP server from the chat. When a remote MCP server needs you to sign in before its tool can run, the tool's card now shows a sign-in link and a Retry button instead of a bare error. Sign in opens the link in your browser; Retry asks the agent to try again.
Visual Studio

2.3.3 of Visual Studio, Oct 7, 2026

Added

  • Your organization's rules and skills. When your organization publishes rules and skills for its agents, the agent follows its rules on every turn, next to your project's own instructions, and reads one of its skills when a task matches it. The Organization section of Tempr's settings lists them: switch off a recommended one there; a required one stays on.
  • Skills in your project. The agent finds skills in the standard SKILL.md format in .tempr/skills, .agents/skills and .claude/skills in your workspace, and in ~/.agents/skills, and reads one when a task matches it. A tool card shows "Skill: name" when it does.
  • AGENTS.md and other agents' files. Workspace instructions now come from AGENTS.md, CLAUDE.md, GEMINI.md, .cursorrules and Cursor's rules as well as .github/copilot-instructions.md, as in the CLI.
Visual Studio

2.3.2 of Visual Studio, Oct 7, 2026

Changed

  • A tool your organization's Tool Packs leave out says so. When your organization limits which MCP tools its members can use and a call is refused, the tool shows "Not allowed by your organization" with "Your organization's Tool Packs don't include this tool.", instead of a bare error. The agent is told only that the tool isn't available, and doesn't call it again.
  • The settings screen shows your organization's Tool Packs. The MCP servers list names the Tool Packs that apply to you, marks a team server none of them include as "Not in your Tool Packs", and, when your organization only allows its own servers, marks yours as "Not managed by your organization".
  • Each run tells Tempr which of your organization's MCP servers its tools come from, so Tool Packs match every tool to the right server, even when two servers have similar names.
Visual Studio

2.3.1 of Visual Studio, Oct 7, 2026

Changed

  • A remote MCP server that needs you to sign in says so. When a tool's server asks you to sign in first, the tool shows "Sign-in needed" with a Sign in button that opens the sign-in page in your browser, and a Retry button that asks the agent to try again once you have, instead of a bare error. The agent is told only that you need to sign in, and doesn't call the tool again in that turn.
CLI

0.9.14 of CLI, Oct 7, 2026

Added

  • Your organization's rules and skills. tempr rules and tempr skills (and /rules, /skills in a chat) list the rules and skills your organization gives you; tempr rules off <title> and tempr skills off <name> switch off a recommended one on this machine.
  • Skills in your project. The agent finds skills in the standard SKILL.md format in .tempr/skills, .agents/skills and .claude/skills in your workspace, and in ~/.agents/skills and ~/.tempr/skills, and reads one when a task matches it.
  • Your organization's personas and slash commands now reach the CLI, as they do the IDEs.
CLI

0.9.13 of CLI, Oct 7, 2026

Changed

  • A tool your organization's Tool Packs don't include now says so. When your organization limits which MCP tools you can use and the agent calls one that isn't included, the tool shows "Not allowed by your organization" and the CLI prints "Your organization's Tool Packs don't include this tool." The agent is told the tool can't be used, so it stops calling it. In tempr acp, the editor gets the same message.
  • tempr mcp list and /mcp show which MCP tools you can use. When your organization uses Tool Packs, both list your packs and, for each MCP server, which of its tools you can use, or that it isn't in your packs. If your organization doesn't use Tool Packs, nothing changes.
CLI

0.9.12 of CLI, Oct 7, 2026

Changed

  • MCP servers that need you to sign in show a sign-in link. When a remote MCP server needs you to sign in before its tools can run, the CLI prints "Sign in to {server}: {link}" and, in an interactive terminal outside CI, opens the link in your browser once per server. The tool shows "Sign-in needed" instead of a bare error, and the agent is told you've been asked to sign in, so it stops calling the tool for that turn. Once you've signed in, ask again. In tempr acp, the editor shows the same message with the link. Nothing else from the server reaches the agent.
Portal

Update of Portal, Oct 7, 2026

Added

  • Agent playbook. A new page under your organization for what every member's agent follows: rules (required or recommended, in the order you set), skills uploaded as a .zip or SKILL.md or written on the page, and the organization's personas and slash commands, now edited as forms. Give each rule or skill to everyone, or to groups and members. Every change keeps a version you can compare and restore, deleted items can be brought back, and "Preview as a member" shows exactly what one member's agent gets. It replaces the Personas & commands page.
  • The Groups page shows the rules and skills given to each group.
  • MCP guardrails. MCP credentials has a guardrails card for your account and, for owners and admins, for the organization: how strictly tool-call arguments, tool results and planted instructions are checked. Virtual keys can override them. Changes to an organization's settings are in the audit log.
  • Member sign-in for remote MCP servers. Each remote server's card has Sign-in settings: keep the stored headers, or sign each member in with their own account, with the scopes you choose. For providers that need it, enter an OAuth app's client ID and secret.
  • Who's signed in: owners and admins see each member's sign-in to a team server, with the account, scopes and when it was last used, and can revoke one member or everyone.
  • MCP sign-ins: a new page where you see the servers that sign you in, sign in or out, and renew a sign-in that has expired.
  • Agent traces show when an MCP tool's result contained text shaped like instructions or hidden characters.
  • Tool Packs. A new page under your organization for bundling MCP tools into packs: per server, all of its tools, all except some, or only the ones you pick, with a shortcut for a server's read-only tools and "Fetch tools" for a remote server nobody has used yet. Give packs to groups, members or keys, with a preview of how many tools and people a pack covers. "Who has what" shows any member's tools and where they came from. Turning packs on offers a default pack that keeps everyone's access. A switch can allow only your organization's own MCP servers.
  • Groups: make groups of members, or mirror the groups in your company directory so their members follow it.
  • Changes to packs and groups are in the audit log.
  • Install the Portal as an app: add it to your phone's home screen, or install it from Chrome or Edge on Android and desktop, and it opens in its own window with the Tempr icon.
Gateway

Update of Gateway, Oct 5, 2026

Fixed

  • Tool calls on gpt-6-luna, gpt-6-sol and gpt-6.1-sol: OpenAI's chat completions rejects function tools on these models unless reasoning is off, and rejects reasoning effort max outright. Tempr now sends those requests through OpenAI's Responses API, as it already did for gpt-6-astra and the gpt-5.6 models, so tools and max work on /v1/chat/completions.
  • Kimi K3 can switch reasoning off again: models.dev now lists Kimi K3 as always reasoning, so reasoning_effort: "none" had gone back to running it at its lowest level. Moonshot's API still switches it off, so Tempr does again.
CLI

0.9.11 of CLI, Oct 5, 2026

Changed

  • Piped input goes along with a prompt. git diff | tempr "Review this change" sends the prompt with the diff after it, as Claude Code and Codex do. Piped input used to be ignored whenever there was a prompt argument. If nothing arrives on stdin within 3 seconds, the prompt runs on its own and the CLI says so on stderr.

Fixed

  • Prompts reach the model exactly as written. Blank lines, indentation and lines holding only spaces were collapsed into single spaces, so a piped diff arrived with lines joined and a review could report formatting problems that weren't there. This also affected tempr acp.
  • tempr --ask no longer ends its answer with a raw <!-- follow-ups: … --> line.
Gateway

Update of Gateway, Oct 4, 2026

Added

  • Strict budgets: make a virtual key's budget, or an organization's hard cap, strict, and requests running at the same time can't spend past it together: each request's worst case is set aside while it runs, and a request whose worst case doesn't fit in what's left is refused with a message saying what it could cost. Set it in the Portal or with hold_worst_case in the management API. It adds about 5 milliseconds per request, up to about 30 when many share the budget at once, so it's off unless you turn it on. See strict budgets.
  • A budget refusal says what's left. virtual_key_budget_exceeded and organization_budget_exceeded responses carry x-tempr-budget-remaining, the dollars left of that budget this month. See errors.
  • Usage records keep your session ID. The x-tempr-session-id you send is stored on each request's usage record as well as in its log, so spend can be traced to the session that made it.

Changed

  • A paid MCP tool's refusal passes through whole. When a remote MCP server answers HTTP 402, the PAYMENT-REQUIRED and WWW-Authenticate headers that carry its terms now reach your client, and the request log records it as mcp_payment_required, with the price when the terms give one in USDC. Tempr never pays.
VS Code

1.1.15 of VS Code, Oct 4, 2026

Fixed

  • The settings and Browse MCP Servers screens are readable in light themes. Their cards, dropdowns and search boxes showed dark with dark text in any light theme; they now take your theme's colors.
  • Text is easier to read in light and high-contrast themes. Faint labels, the green "Done" status, links and badges were too pale against a light background, and green on black was too dim in High Contrast.
  • Your messages are readable in High Contrast Light. They showed white text on a white bubble.
VS Code

1.1.14 of VS Code, Oct 4, 2026

Added

  • Settings > General > Search the workspace on follow-ups, on by default. In Ask mode, Tempr searches your workspace for code related to every message. Turn it off to search only on a chat's first message; mentioning @workspace or #codebase still searches. Visual Studio and JetBrains IDEs have the same setting.
VS Code

1.1.13 of VS Code, Oct 4, 2026

Changed

  • Current screenshots on this page. The Marketplace and Open VSX listing shows the chat panel as it looks today, mid-turn with a proposed diff, and the current Portal dashboard and usage pages. Nothing in the extension itself changed from 1.1.12.
VS Code

1.1.12 of VS Code, Oct 4, 2026

Added

  • A dollar limit per agent turn. Settings > Agent limits has "Stop an agent turn after (US dollars)", blank by default. With an amount set, the server stops the turn before its next model call once its calls, sub-agents included, have cost that much, and the chat says what the turn spent against the limit; send another message to keep going. Your organization may set a lower limit. If a model's price isn't known, the chat says once that its calls count as free. A turn with a limit always runs on the server: if it can't start there, you see why, instead of the turn running without the limit.

Changed

  • Paid MCP tools say so, once. When an MCP server's tool asks to be paid before it runs, the agent is told plainly that the tool needs payment, at what price when the server says, and that Tempr doesn't pay for tools, so it stops calling it. The tool's row in the chat shows "Paid tool, not run" with the price, and later calls are answered, until the MCP servers restart, without contacting the server again. A tool the server lists as paid is marked as paid for the agent before it's ever called, and a server that asks for payment just to connect shows that as its startup error. Nothing else from the payment request reaches the agent.

Fixed

  • An MCP tool's error now reads as an error. A tool result the server flagged as an error came back to the agent as if the tool had worked. It now comes back as "Error: " and the tool's message, and the tool's row shows Error.
  • A remote MCP server that accepts a connection but never answers no longer holds up the agent's start: it's given up on after 5 seconds, as intended. The time limit never applied before.
JetBrains

1.1.15 of JetBrains, Oct 4, 2026

Fixed

  • The tags on Browse MCP Servers cards ("official", "files" and so on) are readable in light themes. They had white text on a light gray background.
  • Text is easier to read in light themes. Faint labels, the green "Done" status, links and badges were too pale against a light background.
JetBrains

1.1.14 of JetBrains, Oct 4, 2026

Added

  • Ask mode searches your project. Before answering in Ask mode, Tempr finds the code in your project most related to your message and gives it to the model, as in VS Code and Visual Studio, so questions about your codebase get answers about your code. Settings > General > "Search the workspace on follow-ups" (on by default) controls whether this happens on every message or only on a chat's first one; mentioning @workspace or #codebase always searches.

Fixed

  • The chat's keyboard and screen reader support works. The script behind it never loaded in JetBrains IDEs. Now: - screen readers announce chat updates; - menus and pickers work with the arrow keys; - the history panel, license panel and settings dialogs keep focus inside while open and give it back when closed; - history entries can be opened from the keyboard.
JetBrains

1.1.13 of JetBrains, Oct 4, 2026

Fixed

  • No more "IDE error occurred" from Go to File. On recent IntelliJ-platform IDEs (seen on IntelliJ IDEA 2026.2), the first Go to File or Search Everywhere raised a red error balloon because the "Send to Tempr" intention had no description. It now has one, which also fills in its entry under Settings > Editor > Intentions > Tempr.
JetBrains

1.1.12 of JetBrains, Oct 4, 2026

Added

  • A dollar limit per agent turn. Settings has "Stop an agent turn after (US dollars)", blank by default. With an amount set, the server stops the turn before its next model call once its calls, sub-agents included, have cost that much, and the chat says what the turn spent against the limit. Your organization may set a lower limit. If a model's price isn't known, the chat says once that its calls count as free.

Changed

  • Paid MCP tools say so, once. When an MCP server's tool asks to be paid before it runs (x402 or MPP), the agent is told plainly that the tool needs payment, at what price when the server says, and that Tempr doesn't pay for tools, so it stops calling it. The tool shows "Paid tool, not run" with the price, and later calls are answered without contacting the server again until the MCP servers restart. A tool the server lists as paid is marked as paid before it's ever called, and a server that asks for payment just to connect says so as its startup error. Nothing else from the payment request reaches the agent.

Fixed

  • An MCP tool's error reads as an error. A tool that reported an error had its message passed to the agent as if the tool had worked.
  • A turn that reaches its step limit says so in the chat, instead of stopping without a word.
  • An MCP server that answers with an HTTP error, or with something that isn't JSON, gives that error instead of "(no response from MCP server)", and a server that fails its handshake is stopped rather than left running.
Visual Studio

2.3.0 of Visual Studio, Oct 4, 2026

Changed

  • Settings moved into the Tempr chat window, as in VS Code and JetBrains IDEs. The gear at the top of the chat window, or Tools > Tempr Settings, opens the same settings screen those IDEs have, with search, a Reset button on every changed setting, and an Account card with your license status and cloud sync. Changes apply as you make them; there's no OK or Apply. Tools > Options > Tempr now has one button that opens the screen. Everything you set in Tools > Options before is carried over the first time this version starts.
  • Browse MCP Servers opens the same browse screen as in VS Code and JetBrains IDEs, instead of a separate window.
  • The chat and the settings screen stay in step. Picking a model, an approval mode or which tools are on in the chat changes the setting, and changing it on the settings screen changes the chat.
  • A call to a tool you've turned off is refused, even if a model asks for it anyway.

Fixed

  • The chat follows your Visual Studio theme in Light. It used its own built-in light colors instead of the theme's, and faint labels, links and badges were too pale to read comfortably. Links are now darkened just enough to be readable when a theme's own link color isn't.
Visual Studio

2.2.39 of Visual Studio, Oct 4, 2026

Added

  • A dollar limit per agent turn. Options has "Stop an agent turn after (US dollars)", blank by default. With an amount set, the server stops the turn before its next model call once its calls, sub-agents included, have cost that much, and the chat says what the turn spent against the limit. Your organization may set a lower limit. A turn with a limit always runs on the server: if it can't start there, you see why, instead of the turn running without the limit.

Changed

  • Paid MCP tools say so, once. When an MCP server's tool asks to be paid before it runs (x402 or MPP), the agent is told plainly that the tool needs payment, at what price when the server says, and that Tempr doesn't pay for tools, so it stops calling it. The tool shows "Paid tool, not run" with the price, and later calls are answered without contacting the server again until the MCP servers restart. A tool the server lists as paid is marked as paid before it's ever called, and a server that asks for payment just to connect says so as its startup error. Nothing else from the payment request reaches the agent.

Fixed

  • An MCP tool's error reads as an error for MCP servers run as a local command. A tool that reported an error had its message passed to the agent as if the tool had worked.
  • A refusal from Tempr's server shows the server's own message, instead of "Your license session has expired".
  • A local MCP server that doesn't answer its handshake is stopped rather than left running.
CLI

0.9.10 of CLI, Oct 4, 2026

Added

  • Your organization can limit what one agent run costs. A run that reaches the limit stops before its next model call, with exit code 6 and status cost-limit, but only that turn: the session carries on. --max-cost can only make it lower.

Changed

  • --max-cost is enforced by Tempr's server too. Each run is sent what's left of it, so a call the CLI didn't see billed still counts.
  • Paid MCP tools say so, once. When an MCP server's tool asks to be paid before it runs (x402 or MPP), the agent is told plainly that the tool needs payment, at what price when the server says, and that Tempr doesn't pay for tools, so it stops calling it. The tool shows "Paid tool, not run" with the price, and later calls are answered without contacting the server again until the MCP servers restart. A tool the server lists as paid is marked as paid before it's ever called, and a server that asks for payment just to connect says so as its startup error. Nothing else from the payment request reaches the agent.

Fixed

  • tempr update recognises a copy installed with npm and tells you to update it with npm install -g @tempr/cli@latest, instead of with the install script, which would have left npm with the old version.
Portal

Update of Portal, Oct 4, 2026

Added

  • Strict budgets: a "Strict" option on a virtual key's monthly budget, on each member's budget in an organization's key settings, and on an organization's hard cap: requests running at the same time can't spend past the budget together. It adds about 5 milliseconds per request, up to about 30 when many share the budget at once, so it's off unless you turn it on. Changes to an organization's budgets are in the audit log.
  • Most expensive agent runs. The Usage page, and an organization's Budget page for its owners and admins, list this month's costliest agent runs: when each started, who ran it, its model, its number of model calls and its cost, sub-agents included, with a link to its trace.
  • Agent run cost limit: on an organization's Budget page, owners and admins can set the most one agent run may cost, for every member. A run stops before its next model call once it reaches the limit; members can set a lower limit in their app, not a higher one. Changes are in the audit log.
Gateway

Update of Gateway, Oct 3, 2026

Added

  • Chat and CLI seats with Gateway Pro and Scale: Pro includes one Tempr Chat and CLI seat and Scale five, with every Chat Pro feature. A team adds more at $35 a seat a month with no minimum. A seat is a license key like any other, so the IDE extensions and the CLI sign in with it as they are. Its requests use your Gateway provider keys and count toward the plan's monthly requests, and they show in your request logs as agent and chat traffic, with tokens and cost but never their content. See pricing.
Portal

Update of Portal, Oct 3, 2026

Added

  • Seats on the Gateway plan page: each plan shows the Chat and CLI seats it includes. A team's owners and admins see how many are in use and change how many extra seats they buy, prorated like a plan change. Members get a seat as they join while one is free, and the Members page counts them.
  • Plan for a seat: when your Tempr Chat plan comes with a Gateway plan, the Plan page says so and links to the Gateway plan, instead of offering Chat billing.
Gateway

Update of Gateway, Oct 1, 2026

Added

  • Codex CLI sub-agents on every model: on /v1/responses, tools grouped in a namespace and a client-run tool_search now carry over to non-OpenAI models, so Codex CLI can start sub-agents on Claude and the rest. The Codex CLI guide also shows how to give Codex your models' details, which it needs before it offers apply_patch on them.

Fixed

  • Requests a client hung up on at the end are logged in full. Codex CLI disconnects as soon as a Responses stream's last event arrives, while OpenAI keeps the connection open a moment longer, and Tempr waited for the close: the request was logged without its status, tokens or cost. Streams now end at their last event (response.completed, Anthropic's message_stop, or [DONE]).
  • Gemini takes tools with full JSON Schema. A request to a Gemini or Gemma model failed with "Unknown name additionalProperties" when a tool's parameters used additionalProperties, $ref or other JSON Schema that Gemini's older tool format doesn't accept, as many MCP servers' tools do (JetBrains AI Assistant's own IDE tools among them). Tool schemas now go to Gemini as JSON Schema, unchanged.
Visual Studio

2.2.38 of Visual Studio, Oct 1, 2026

Fixed

  • Listing every file shows as "Listing files (all files)", as in VS Code and JetBrains, instead of "Listing files ()".
CLI

0.9.9 of CLI, Oct 1, 2026

Changed

  • An editor session starts on the model you last picked in an editor, so it matches what JetBrains AI Assistant shows from the start, and the model's reasoning levels are there before your first message. It used to start on your default model until the first message, with no reasoning levels to pick when the default had none. tempr config set-model makes your default the starting model again, and tempr config show lists the editor's pick.

Fixed

  • Listing every file shows as "Listing files (all files)", as in VS Code and JetBrains, instead of "Listing files ()".

September 2026

Gateway

Update of Gateway, Sep 30, 2026

Added

  • Alert webhooks: alert rules (Pro and up) send gateway.alert.triggered and gateway.alert.resolved to your webhook, with the rule, its threshold and filters, the value, and links to the Dashboard. Alert webhooks now documents every event the webhook sends, and how to check its signature.

Changed

  • Request logs now record the model you asked for (such as a fallback alias, before it resolved) and the reasoning level applied. Both show on the Portal's request page and in log exports.
VS Code

1.1.11 of VS Code, Sep 30, 2026

Fixed

  • PowerShell script output comes back whole. run_powershell_script output was cut at 120 characters with "…", or at 80 on macOS and Linux, where pwsh also added colour codes, so the agent got paths and table values with their ends missing. It now comes back whole and plain, and Windows PowerShell's padding at the end of table rows is taken off.
  • A failing PowerShell script's error comes back as text. run_powershell_script returned PowerShell's error messages as CLIXML (XML with escaped line breaks and colour codes, plus a progress record from Windows PowerShell), instead of the message itself.
  • run_powershell_script on Windows takes scripts up to about 11,000 characters. It ran through cmd.exe, whose command lines stop at 8,191 characters, about 3,000 characters of script.
JetBrains

1.1.11 of JetBrains, Sep 30, 2026

Fixed

  • PowerShell script output comes back whole. run_powershell_script output was cut at 120 characters with "…", or at 80 on macOS and Linux, where pwsh also added colour codes, so the agent got paths and table values with their ends missing. It now comes back whole and plain, and Windows PowerShell's padding at the end of table rows is taken off.
  • A failing PowerShell script's error comes back as text. run_powershell_script returned PowerShell's error messages as CLIXML (XML with escaped line breaks and colour codes, plus a progress record from Windows PowerShell), instead of the message itself.
  • On Linux, run_powershell_script now finds an installed PowerShell. It always reported PowerShell as not installed there.
Visual Studio

2.2.37 of Visual Studio, Sep 30, 2026

Fixed

  • Command output comes back whole. PowerShell cut run_command and run_powershell_script output at 120 characters with "…", so the agent got paths and table values with their ends missing. It also padded every table row with spaces, which filled much of the 8,000 characters kept of a result. Both are fixed.
  • A failing PowerShell script's error comes back as text. run_powershell_script returned Windows PowerShell's error messages as CLIXML, XML with escaped line breaks and a "Preparing modules for first use" progress record, instead of the message itself.
  • A sub-agent's reply (from a delegated agent such as @review) is no longer saved into the conversation as an answer of its own, which the next turn then read as something Tempr had said.
CLI

0.9.8 of CLI, Sep 30, 2026

Added

  • Tempr in your editor: tempr acp runs Tempr as an Agent Client Protocol agent, for Zed, JetBrains AI Assistant, Neovim, Emacs and other editors that speak it. The editor shows Tempr's replies, its tool calls with edits as diffs, and its questions, which you answer there; files you mention and images go with your message, and stopping a turn stops it. Tempr runs its tools itself, so the allow-list, the approval mode and the sandbox work as in the terminal. Sessions are saved to tempr history, show in the editor's session list, and reopen with their conversation. The editor sets the approval mode, the model, its reasoning level and web search for each session; your command templates, /undo, /diff and /agents work as slash commands; the editor's MCP servers, local or remote, run beside yours; a command's output streams into a terminal under its call in Zed; sub-agents answer under the call that delegated to them; and you can sign in from the editor. See Tempr in your editor.

Changed

  • --yolo runs its commands in the sandbox by default (Linux), as does autopilot in CI, with the network on, so installs, restores and tests that use localhost keep working while commands can change files only in the current folder, the temp folders and the package caches. Any command then runs without asking, except ones that delete, publish or force-push. Where the sandbox can't run (macOS, Windows, an older kernel) these runs go ahead as before. --no-sandbox or tempr config set-sandbox off opts out; --sandbox also cuts off the network. Other runs aren't sandboxed unless you ask.
  • On macOS and Linux, the agent's commands run in /bin/sh, even when PowerShell is installed, as in Claude Code and Codex. They used to run in PowerShell whenever it was installed, and the agent was told to write PowerShell.
  • dotnet and Go restore packages in the sandbox. NuGet's ~/.nuget/packages and Go's module cache are writable there, like npm's, Cargo's and Maven's already were. dotnet keeps its own per-user files in ~/.cache/tempr/sandbox-dotnet, so it runs even on a machine where it never ran before, while ~/.dotnet, which holds global tools, stays read-only.

Fixed

  • A sub-agent's reply (from a delegated agent such as @review) now shows on its own "↳ @review" line, and is never taken for the answer: a turn that ended right after one saved it, and reported it in --json, as the reply.
  • A command the agent runs no longer shares your terminal's input: one that asks for input gets end-of-input at once, instead of waiting until it times out.
  • On Windows, output from the agent's commands is no longer cut off. PowerShell cut tables and paths at 120 characters with "…". They now come back whole, and Windows PowerShell's padding at the end of table rows is taken off.
Portal

Update of Portal, Sep 30, 2026

Added

  • Gateway Dashboard. The Gateway's Overview is now a Dashboard: requests, cost, error rate, latency, time to first byte and tokens for the range you pick (24 hours up to your plan's log retention, or dates of your choosing), with charts over time, top models, providers, spend by key against its budget, prompt caching, guardrails and prompt templates. Filter it by key, provider or model. On Pro and up each figure shows its change against the period before. Team gateway is the same dashboard for your organization's keys.
  • Log explorer: Logs take a time range and filter by key, provider, model, status in plain words ("rate limited", "blocked by guardrail"), session, end user, operation, duration, a metadata entry or a request ID. Active filters show as chips you can remove, every view has its own address, and Export CSV exports exactly what's shown, now with cost, session, end user and metadata.
  • Request page: each request shows the model asked for and the one that answered, every model and provider key tried on the way, the prompt and response caches, its cost and reasoning level, and its key, session, end user, prompt template and metadata, each linking onward.
  • A key's stats. A Stats link beside each key on Gateway keys and Org keys opens the Dashboard for that key, headed by the key itself: its status, how much of its monthly budget is spent, its limits, allowed models and expiry, and links to edit it or open its logs.
  • Metadata: a new Metadata page groups your requests by a key of the x-tempr-metadata header (a team, a feature, a customer) and shows each value's requests, cost, error rate, median and p95 latency and tokens, each linking to its logs. A team's is on the Team gateway page.
  • Charts for sessions and end users: Sessions and End users chart their ten costliest. A session's page charts its requests in order, with how long each took and failures in red; an end user's charts their requests and cost for each day.
  • Alert rules: on Gateway Pro and up, the new Alerts page sets rules on the error rate, cost, cost against the usual, p95 latency or number of requests over the last 15 minutes to 24 hours, for all your keys or one key, provider or model. A rule emails you (or a team's owners and admins) or calls your webhook when it's crossed and again when it recovers, and the Dashboard shows any rule that's firing. Your error-rate and cost anomaly alerts become your first two rules, set as they were.
  • Weekly report: a Monday email of the week's requests, error rate, cost, tokens and latency, with the top models and keys by cost and the change from the week before. New Gateway accounts get it instead of the daily digest; turn either on or off in Gateway settings.

Changed

  • Gateway settings (overage billing, content capture, redaction, log retention, guardrails, prompt caching, alerts) moved from the Overview to their own Settings page, and a team's to Team gateway settings.
  • Analytics and Usage are part of the Dashboard now: their old links open it over the last 30 days and over this month.
  • Charts of small dollar amounts label their axis in fractions of a cent ($0.005, $0.010) instead of repeating the same label.
Gateway

Update of Gateway, Sep 29, 2026

Added

  • Enterprise plan. Gateway Enterprise is now a plan of its own, set up with Tempr under a contract: its own monthly requests, rate limit, log retention and billing. Talk to us to set one up.
  • Key expiry and IP allowlists: a virtual key can stop working on a date you choose (401 key_expired after it) and be limited to the addresses or CIDR ranges it's used from (403 ip_not_allowed from anywhere else). Set them when you create or edit a key. See what a virtual key scopes.
  • Management API: on the Pro, Scale and Enterprise plans, a tmk_ management key lets your own scripts create, change and revoke virtual keys and read usage and cost through /v1/management. Management keys have scopes, and can have an expiry and an IP allowlist. See the management API.
  • Log streaming (Enterprise): an organization can send its request logs and agent traces as spans to an OpenTelemetry endpoint, and its audit log there too or to a signed webhook, as they happen. See log streaming.

Changed

  • Organization keys stop while the organization's plan is past due or canceled (402 gateway_inactive), as personal keys already did.
  • Kimi K3 can switch reasoning off. On Moonshot's API, reasoning.enabled: false or reasoning_effort: "none" now stops Kimi K3 thinking; /v1/messages does the same with thinking.type: "disabled". Before, Tempr treated K3 as always reasoning and ran none at its lowest level. Its low, high and max levels work as before.

Fixed

  • Reasoning comes back in one shape on every model. Providers that return reasoning as reasoning_content (DeepSeek, Kimi, MiMo and GLM among them) or as a bare reasoning field (Groq, Cerebras) now also get reasoning text and reasoning_details, as the docs describe and as OpenRouter returns it, streaming or not. The provider's own field is still there.
  • Switching a conversation to Fireworks AI or Mistral keeps working. Both reject some of the reasoning fields an earlier assistant turn can carry. For Fireworks, reasoning now becomes reasoning_content and reasoning_details is removed; for Mistral, all three are removed before the request is sent.
  • Web search fees are recorded. A web search your own request asks for (Anthropic's web_search tool on /v1/messages, or OpenAI's on /v1/responses) now adds the provider's per-search fee to the recorded cost: $10 per 1,000 searches, or $25 per 1,000 for OpenAI's web_search_preview on models that don't reason. Usage, budgets and spend limits include it.
VS Code

1.1.10 of VS Code, Sep 29, 2026

Changed

  • Symbol search finds the definition first. search_symbols lists where a name is declared, and as what, before the places it's used, in C#, TypeScript and JavaScript, Python, Go, Rust, Java, Kotlin, C and C++, Swift, Ruby and PHP, the same as the CLI. It no longer builds the embedding index first, so it answers at once and costs nothing, and a definition in a later file is no longer pushed out by the first few mentions.

Fixed

  • The agent now sees a JavaScript monorepo's packages. Its file tools skipped every folder named packages (meant for NuGet's old packages folder), which hid a monorepo's whole source. That folder is now skipped only beside a .sln. Build output is left out where a build made it (Cargo's and Maven's target, Gradle's build, a package's dist and out) rather than every folder with those names, along with Python virtual environments and caches.
  • Searching the code now covers Kotlin build scripts (.kts), Vue, Svelte and Astro components, .NET project files, and build files with no extension such as Makefile and Dockerfile.
VS Code

Update of VS Code, Sep 29, 2026

Added

  • Web search: on a Claude model through your Anthropic key, or an OpenAI model through your OpenAI key, the agent can now search the web with the provider's own search. Each search shows as "Searching the web for …", and the pages it finds are ones the agent can then open. The provider bills each search to your key ($10 per 1,000 on both), and the cost the chat shows includes it.
  • Web search on Grok: xAI's models search the web with xAI's own search too, billed to your xAI key at $5 per 1,000 searches, where opening a page counts as one. The cost the chat shows includes it.

Changed

  • Claude filters what it finds: on Claude Opus and Sonnet 4.6 and later, and Claude Fable, a web search now runs through code Claude writes and runs on Anthropic's side, which reads the results and keeps only what matters before it reaches the conversation. Anthropic made it for more accurate answers from fewer tokens. A search costs the same, and the code runs free.
  • An agent turn on a Claude model caches its tool definitions apart from its instructions, so a call whose instructions changed (every turn's second call, which drops the project overview) reads the tools from the cache instead of paying to write them again.

Fixed

  • A turn in which Claude searched a lot no longer stops halfway: when Anthropic pauses a search partway through, the agent carries on where it paused.
JetBrains

1.1.10 of JetBrains, Sep 29, 2026

Changed

  • Symbol search finds the definition first. search_symbols lists where a name is declared, and as what, before the places it's used, in C#, TypeScript and JavaScript, Python, Go, Rust, Java, Kotlin, C and C++, Swift, Ruby and PHP, the same as the CLI. It used to list the first matches in file order, so a definition in a later file could be cut off.

Fixed

  • The agent now sees a JavaScript monorepo's packages. Its file tools skipped every folder named packages (meant for NuGet's old packages folder), which hid a monorepo's whole source. That folder is now skipped only beside a .sln. Build output is left out where a build made it (Cargo's and Maven's target, Gradle's build, a package's dist and out) rather than every folder with those names, along with Python virtual environments and caches.
  • Searching the code now covers Kotlin build scripts (.kts), Vue, Svelte and Astro components, .NET project files, and build files with no extension such as Makefile and Dockerfile.
JetBrains

Update of JetBrains, Sep 29, 2026

Added

  • Web search: on a Claude model through your Anthropic key, or an OpenAI model through your OpenAI key, the agent can now search the web with the provider's own search. Each search shows as "Searching the web for …", and the pages it finds are ones the agent can then open. The provider bills each search to your key ($10 per 1,000 on both), and the cost the chat shows includes it.
  • Web search on Grok: xAI's models search the web with xAI's own search too, billed to your xAI key at $5 per 1,000 searches, where opening a page counts as one. The cost the chat shows includes it.

Changed

  • Claude filters what it finds: on Claude Opus and Sonnet 4.6 and later, and Claude Fable, a web search now runs through code Claude writes and runs on Anthropic's side, which reads the results and keeps only what matters before it reaches the conversation. Anthropic made it for more accurate answers from fewer tokens. A search costs the same, and the code runs free.
  • An agent turn on a Claude model caches its tool definitions apart from its instructions, so a call whose instructions changed (every turn's second call, which drops the project overview) reads the tools from the cache instead of paying to write them again.

Fixed

  • A turn in which Claude searched a lot no longer stops halfway: when Anthropic pauses a search partway through, the agent carries on where it paused.
Visual Studio

2.2.36 of Visual Studio, Sep 29, 2026

Changed

  • Symbol search finds the definition first. search_symbols lists where a name is declared, and as what, before the places it's used, in C#, TypeScript and JavaScript, Python, Go, Rust, Java, Kotlin, C and C++, Swift, Ruby and PHP, the same as the CLI. It no longer builds the embedding index first, so it answers at once and costs nothing, and a definition in a later file is no longer pushed out by the first few mentions.

Fixed

  • The agent now sees a JavaScript monorepo's packages. Its file tools skipped every folder named packages (meant for NuGet's old packages folder), which hid a monorepo's whole source. That folder is now skipped only beside a .sln. Build output is left out where a build made it (Cargo's and Maven's target, Gradle's build, a package's dist and out) rather than every folder with those names, along with Python virtual environments and caches.
  • Searching the code now covers Rust, Kotlin, Swift, Scala, TOML, Vue and Svelte files and build files with no extension such as Makefile and Dockerfile, which it used to skip.
Visual Studio

Update of Visual Studio, Sep 29, 2026

Added

  • Web search: on a Claude model through your Anthropic key, or an OpenAI model through your OpenAI key, the agent can now search the web with the provider's own search. Each search shows as "Searching the web for …", and the pages it finds are ones the agent can then open. The provider bills each search to your key ($10 per 1,000 on both), and the cost the chat shows includes it.
  • Web search on Grok: xAI's models search the web with xAI's own search too, billed to your xAI key at $5 per 1,000 searches, where opening a page counts as one. The cost the chat shows includes it.

Changed

  • Claude filters what it finds: on Claude Opus and Sonnet 4.6 and later, and Claude Fable, a web search now runs through code Claude writes and runs on Anthropic's side, which reads the results and keeps only what matters before it reaches the conversation. Anthropic made it for more accurate answers from fewer tokens. A search costs the same, and the code runs free.
  • An agent turn on a Claude model caches its tool definitions apart from its instructions, so a call whose instructions changed (every turn's second call, which drops the project overview) reads the tools from the cache instead of paying to write them again.

Fixed

  • A turn in which Claude searched a lot no longer stops halfway: when Anthropic pauses a search partway through, the agent carries on where it paused.
CLI

0.9.7 of CLI, Sep 29, 2026

Added

  • A sandbox for the agent's commands (Linux): with --sandbox, or tempr config set-sandbox on, the agent's commands can change files only in the current folder, the temp folders and the package caches, and can't reach the network. Inside it any command runs without asking, even in a script, so an unattended run can build, test and try things that have no allow-list entry; commands that delete, publish or force-push still ask. When the sandbox blocks something the command needed, the agent can ask to run it outside, which always asks you first. Changes a command makes to git's hooks or config are put back. It uses the kernel's Landlock, so it needs no install and works in containers and on Ubuntu 24.04; on macOS and Windows it isn't available yet, and asking for it there stops the run (exit code 7) rather than run commands unsandboxed. --sandbox-network leaves the network on.

Fixed

  • A JavaScript package's out folder (beside package.json or tsconfig.json) is left out of searches, like dist, the same as in the IDEs.
  • The tool line for a symbol search counts the places found, not its "Defined at" and "Used at" headings.
CLI

0.9.6 of CLI, Sep 29, 2026

Added

  • Web search: on an Anthropic or OpenAI model, the agent can search the web with the provider's own search, shown as Searching the web for "…", and then open the pages it found. Each search is billed by the provider to your key ($10 per 1,000 on both), and the cost the CLI and the Portal show includes it. It's on in an interactive session and off in scripts (--json, piped input, CI); --search and --no-search decide for one run, and tempr config set-web-search off turns it off in interactive sessions too.
  • Sign in with your browser: tempr auth shows a code and opens the Tempr portal, where you approve the sign-in for your plan. It works from any device, so signing in over SSH or in a container is the same. tempr auth --browser goes straight there; a license key still works, pasted at the prompt, passed as tempr auth <key> or set in TEMPR_LICENSE_KEY.
  • A first run that sets you up: tempr on a new machine walks through signing in, adding a provider key and picking a default model, instead of stopping at the first thing missing. Every step can be skipped, and none of it runs in scripts or CI.
  • Keys are checked when you add them. tempr keys add asks the provider whether the key works before saving it, so a mistyped key is found now rather than on your first turn. A key the provider rejects isn't saved unless you confirm or pass --force; one that couldn't be checked (the provider was down, or has no way to check) is saved with a note.
  • !command in the REPL: !git status runs a command in this folder, shows its output, and puts it in front of your next message, so the agent sees what you saw. It's your own command, so nothing asks first.
  • --max-cost stops a run once its model calls have cost that many dollars, sub-agents included, and exits with code 6 and status cost-limit.
  • A ping when a long turn is done: a turn that ran 30 seconds or more rings the terminal bell when it finishes or needs your approval, with a desktop notification in terminals that show one (iTerm2, WezTerm, Ghostty, kitty, rxvt, foot, Konsole). tempr config set-notifications off turns it off; it never rings in CI.
  • More in --json: the stream starts with a session line (session id, model and settings), and each tool the CLI runs locally adds a tool-result line with the output the model was given.
  • Symbol search finds the definition first. search_symbols lists where a name is declared, and as what, before the places it's used, in C#, TypeScript and JavaScript, Python, Go, Rust, Java, Kotlin, C and C++, Swift, Ruby and PHP. It used to list the first matches in file order, so a definition in a later file could be cut off.
  • Other agents' instruction files: alongside AGENTS.md, each turn now carries CLAUDE.md, GEMINI.md, .cursorrules, and the Cursor rules in .cursor/rules that always apply, so a project set up for another agent keeps its rules. Cursor rules that apply only to some files are listed with their description for the agent to read when relevant. Where the files disagree, AGENTS.md wins.

Fixed

  • Searching the code now covers Rust, Kotlin, Swift, Scala, TOML, Vue and Svelte files and extensionless build files such as Makefile and Dockerfile, which it used to skip. A JavaScript monorepo's packages/ folder is searched and listed again: it was skipped as if it were NuGet's old packages folder, which is still skipped beside a .sln. Build output is left out where a build made it (Cargo's and Maven's target, Gradle's build, a package's dist), along with Python virtual environments and caches.
CLI

Update of CLI, Sep 29, 2026

Added

  • Web search on Grok: xAI's models search the web with xAI's own search too, billed to your xAI key at $5 per 1,000 searches, where opening a page counts as one. The cost the CLI and the Portal show includes it.

Changed

  • Claude filters what it finds: on Claude Opus and Sonnet 4.6 and later, and Claude Fable, a web search now runs through code Claude writes and runs on Anthropic's side, which reads the results and keeps only what matters before it reaches the conversation. Anthropic made it for more accurate answers from fewer tokens. A search costs the same, and the code runs free.
  • An agent run on a Claude model caches its tool definitions apart from its instructions, so a call whose instructions changed (every run's second call, which drops the project overview) reads the tools from the cache instead of paying to write them again.

Fixed

  • A turn in which Claude searched a lot no longer stops halfway: when Anthropic pauses a search partway through, the agent carries on where it paused.
Portal

Update of Portal, Sep 29, 2026

Added

  • Approve a CLI sign-in: tempr auth in CLI 0.9.6 shows a code and opens the Portal's Activate page, where you sign in and approve it for your plan. It works from any device, so a CLI running over SSH or in a container signs in the same way.
  • Key expiry and IP allowlists: the key forms on Gateway keys and Org keys take an expiry date and the addresses a key may be used from, and the key list shows when each key expires.
  • Management keys: Gateway keys (Pro, Scale and Enterprise) and Org keys have a Management keys card for creating and revoking keys for the management API. An organization's are revoked when the person who made them leaves or stops being an admin.
  • Log streaming: owners and admins of an Enterprise organization add, test, pause and remove log streaming destinations on the new Log streaming page, and see how far each has sent.
  • Enterprise plan: the Gateway plan page shows the Enterprise plan, and an Enterprise organization's Gateway page shows its contract.

Changed

  • The audit log now names who acted when it wasn't a person: a management key, Tempr support, or Tempr itself (for example stopping a log streaming destination that kept failing).
  • Invites can't overfill your seats. Several invites can be out at once, so accepting one now takes a seat only if one is free, and otherwise asks the person to try again once a seat is freed. Before, they could together join past the seats you'd bought.
  • Accepted invites in the audit log: when someone accepts an invite, the organization's audit log now records it as "Invite accepted", naming the person who joined.
Gateway

Update of Gateway, Sep 28, 2026

Changed

  • Your plan's rate limit is shared by all your keys. The requests-per-minute limit of your Gateway plan (10, 60 or 240 on Free, Pro or Scale) now counts every key on the account together, as the plan describes. Before, each key got the whole limit, so several keys together could go several times over it. A key's own rate limit still applies to that key.
  • A rate-limit 429 now carries a Retry-After header: the seconds until the current minute ends.
  • Organizations without a Gateway plan: organization keys get the Free plan's limits, 10 requests a minute and 10,000 requests a month, shared across the organization. They used to have no limit.
VS Code

1.1.9 of VS Code, Sep 28, 2026

Changed

  • Autopilot no longer runs every npm script. It used to run any package.json script unattended, npm run deploy included; now it runs npm test and the build, compile, test, lint and typecheck scripts, and asks before the rest. An allowed command covers whole words, so npm run build doesn't cover npm run build-and-deploy.
  • Trusting a command for the session trusts that script, not the whole tool: trusting npm run build no longer trusts every npm run script, and python -m pytest no longer trusts every Python module.
  • A build that also publishes (mvn test deploy, ./gradlew build publish) asks every time, like a delete.

Fixed

  • The agent remembers its own answers. Each message used to reach it with your earlier questions in the chat but none of its replies, so a follow-up like "now make it faster" came without what "it" was. Agent and Ask mode both.
VS Code

1.1.8 of VS Code, Sep 28, 2026

Added

  • The agent asks before opening a page it found itself: without asking, it opens a link from your messages, from a tool's result or from a page it has already read, and any page of a well-known documentation site. For any other address it now shows a card with the whole address: Open, Trust the site for this session, or Reject, the way Claude Code asks per site. It used to refuse.
  • Sites the agent can open: Settings > Permissions > Sites the agent can open lists sites whose pages open without asking: docs.example.com, or *.example.com for its subdomains. It stays on this machine, like your auto-approved commands.
  • Links from earlier turns: a link on a page the agent read earlier in a chat can be opened in a later turn of the same chat.

Changed

  • Page reads show as "Fetching <address>" and package lookups as "Looking up npm package react", instead of the tool's name.
VS Code

Update of VS Code, Sep 28, 2026

Changed

  • The agent can now open any page of a well-known documentation site, such as docs.python.org, developer.mozilla.org or learn.microsoft.com, without the link having appeared in the conversation first. Other addresses it didn't get from you, from a tool or from a page it read are still refused in this version.
  • A web address that carries a key, token or password is opened only if you typed that credential yourself, and an address on your own machine or network (localhost, an intranet name) is answered with a pointer to curl instead of a failed request.

Fixed

  • An agent turn on a model you reach through a provider's own API, such as Anthropic, OpenAI or DeepSeek directly, now shows what it cost. It showed $0 because only OpenRouter reports a price with each reply; the cost is now worked out from the model's price, the same figure the Portal's usage page always had.
JetBrains

1.1.9 of JetBrains, Sep 28, 2026

Changed

  • Autopilot no longer runs every npm script. It used to run any package.json script unattended, npm run deploy included; now it runs npm test and the build, compile, test, lint and typecheck scripts, and asks before the rest. An allowed command covers whole words, so npm run build doesn't cover npm run build-and-deploy.
  • Trusting a command for the session trusts that script, not the whole tool: trusting npm run build no longer trusts every npm run script, and python -m pytest no longer trusts every Python module.
  • A build that also publishes (mvn test deploy, ./gradlew build publish) asks every time, like a delete.

Fixed

  • The agent remembers the conversation. Each message used to reach it as the start of a new chat, with none of your earlier questions or its answers.
  • Workspace instructions and project context now reach the agent. It gets your .github/copilot-instructions.md with every message (Settings > General > Workspace instructions) and an overview of the project's files and README on each message's first step (Settings > Agent limits > Project context budget). Both settings were there but did nothing.
JetBrains

1.1.8 of JetBrains, Sep 28, 2026

Added

  • The agent asks before opening a page it found itself. Without asking, it opens a link from your messages, from a tool's result or from a page it has already read, and any page of a well-known documentation site. For any other address it now shows a card with the whole address: Open, Trust the site for this session, or Reject, the way Claude Code asks per site. It used to refuse.
  • Sites the agent can open: Settings > Permissions > Sites the agent can open lists sites whose pages open without asking: docs.example.com, or *.example.com for its subdomains. It stays on this machine, like your auto-approved commands.
  • Links from earlier turns: a link on a page the agent read earlier in a chat can be opened in a later turn of the same chat.

Changed

  • Page reads show as "Fetching <address>" and package lookups as "Looking up npm package react", instead of the tool's name.
JetBrains

Update of JetBrains, Sep 28, 2026

Changed

  • The agent can now open any page of a well-known documentation site, such as docs.python.org, developer.mozilla.org or learn.microsoft.com, without the link having appeared in the conversation first. Other addresses it didn't get from you, from a tool or from a page it read are still refused in this version.
  • A web address that carries a key, token or password is opened only if you typed that credential yourself, and an address on your own machine or network (localhost, an intranet name) is answered with a pointer to curl instead of a failed request.

Fixed

  • An agent turn on a model you reach through a provider's own API, such as Anthropic, OpenAI or DeepSeek directly, now shows what it cost. It showed $0 because only OpenRouter reports a price with each reply; the cost is now worked out from the model's price, the same figure the Portal's usage page always had.
Visual Studio

2.2.35 of Visual Studio, Sep 28, 2026

Changed

  • Autopilot no longer runs every npm script. It used to run any package.json script unattended, npm run deploy included; now it runs npm test and the build, compile, test, lint and typecheck scripts, and asks before the rest. An allowed command covers whole words, so npm run build doesn't cover npm run build-and-deploy.
  • Trusting a command for the session trusts that script, not the whole tool: trusting npm run build no longer trusts every npm run script, and python -m pytest no longer trusts every Python module.
  • A build that also publishes (mvn test deploy, ./gradlew build publish) asks every time, like a delete.

Fixed

  • The agent follows your .github/copilot-instructions.md for the whole chat. It was sent with a chat's first message only, so from the second message on the agent answered without it.
Visual Studio

2.2.34 of Visual Studio, Sep 28, 2026

Added

  • The agent asks before opening a page it found itself. Without asking, it opens a link from your messages, from a tool's result or from a page it has already read, and any page of a well-known documentation site. For any other address it now shows a card with the whole address: Open, Trust the site for this session, or Reject, the way Claude Code asks per site. It used to refuse.
  • Sites the agent can open: Tools > Options > Tempr > Agent Commands > Sites the agent can open lists sites whose pages open without asking: docs.example.com, or *.example.com for its subdomains. It stays on this machine, like your auto-approved commands.
  • Links from earlier turns: a link on a page the agent read earlier in a chat can be opened in a later turn of the same chat.

Changed

  • Page reads show as "Fetching <address>" and package lookups as "Looking up npm package react", instead of the tool's name.

Fixed

  • A finished page read or package lookup was remembered in the chat as "Delegated sub-agent completed". It's now recorded under its own name.
Visual Studio

Update of Visual Studio, Sep 28, 2026

Changed

  • The agent can now open any page of a well-known documentation site, such as docs.python.org, developer.mozilla.org or learn.microsoft.com, without the link having appeared in the conversation first. Other addresses it didn't get from you, from a tool or from a page it read are still refused in this version.
  • A web address that carries a key, token or password is opened only if you typed that credential yourself, and an address on your own machine or network (localhost, an intranet name) is answered with a pointer to curl instead of a failed request.

Fixed

  • An agent turn on a model you reach through a provider's own API, such as Anthropic, OpenAI or DeepSeek directly, now shows what it cost. It showed $0 because only OpenRouter reports a price with each reply; the cost is now worked out from the model's price, the same figure the Portal's usage page always had.
CLI

0.9.5 of CLI, Sep 28, 2026

Added

  • Knows your project, whatever it's written in. Each turn tells the agent which projects the folder holds and how each one builds, tests, lints and type-checks: .NET, TypeScript and JavaScript (npm, pnpm, yarn or bun, from your package.json scripts), Python (pip, uv, Poetry, Pipenv or PDM, with pytest, Ruff and mypy), Go, Rust, and Java or Kotlin with Maven or Gradle. It looks a few folders down, so each project in a monorepo is listed with its folder. tempr init drafts the same commands into AGENTS.md.
  • Commands in a subfolder: the agent can run a command in a folder inside the workspace, such as npm test in web/. Chaining cd web && npm test is still refused.
  • Your project's checks run in autopilot. Each ecosystem's build, test, lint and type-check commands are now on the default allow-list, so --yolo runs pytest, go test, cargo test, npm test or ./gradlew build without asking. Interactive mode still asks for every command.

Changed

  • A command is stopped after 2 minutes instead of 1, and the agent can ask for up to 10 for a long build or test run.
  • Long command output keeps its start and its end, where failures and summaries are, and says how much was cut. It used to reach the model whole.
  • npm run no longer covers every script. Autopilot used to run any package.json script unattended, npm run deploy included; now it runs only build, compile, test, lint and typecheck and asks for the rest. An allowed command covers whole words, so npm run build doesn't cover npm run build-and-deploy, and "trust for this session" on npm run test trusts npm run test, not every script.
  • A build that also publishes (mvn test deploy, ./gradlew build publish) asks every time, like a delete.
  • The .NET-only tools (projects, project references, tests, test results) are offered only where there's a .NET project, and diagnostics only for .NET or a TypeScript project at the root.
CLI

0.9.4 of CLI, Sep 28, 2026

Added

  • The agent asks before opening a page it found itself. Without asking, it opens a link from your messages, from a tool's result or from a page it has already read, and any page of a well-known documentation site such as docs.python.org, developer.mozilla.org or learn.microsoft.com. For any other address it now asks: Yes, Yes, and trust the site for this session, or No, the way Claude Code asks per site. It used to refuse. tempr config allow-site <site> stops the asking for a site for good (*.example.com covers its subdomains), and tempr config disallow-site <site> undoes it. With no terminal to ask on (--json, piped input or CI), such an address is still refused and the agent is told why.
  • Links from earlier turns: a link on a page the agent read earlier in the session can be opened later in it, including after -c or --id. The session remembers which links the agent may open.

Changed

  • --allowed-tools and --disallowed-tools now cover web_fetch and lookup_package, so --allowed-tools read_file keeps the agent off the web.
  • Page reads show as "Fetching <address>" and package lookups as "Looking up npm package react" instead of the raw tool call.
  • A web address that carries a key, token or password is opened only if you typed that credential yourself, and an address on your own machine or network (localhost, an intranet name) is answered with a pointer to curl instead of a failed request. These two work in 0.9.3 too.

Fixed

  • The progress spinner no longer draws over an approval prompt.
CLI

Update of CLI, Sep 28, 2026

Fixed

  • The agent follows your AGENTS.md for the whole session. It used to have the file only until its first tool call, and not at all on a later turn. A turn run as a persona (@test …) and an agent it delegates to now get it too, along with which operating system and shell their commands run in. Works in every CLI version.
  • An agent turn on a model you reach through a provider's own API, such as Anthropic, OpenAI or DeepSeek directly, now shows what it cost. It showed $0 because only OpenRouter reports a price with each reply; the cost is now worked out from the model's price, the same figure the Portal's usage page always had. Works in every CLI version.
Gateway

Update of Gateway, Sep 27, 2026

Added

  • Novita AI: Novita's hosted models are available with your Novita key as novita/… (for example novita/deepseek/deepseek-v4-flash). Reasoning levels are offered per model, and switching reasoning off works on every model that can stop. Usage is priced from Novita's own catalog.
  • An output limit that Novita AI rejects as too large is now lowered to the model's limit and the request retried, as it already was for OpenAI, Z.AI and Groq.
  • Cerebras: Cerebras' hosted models are available with your Cerebras key as cerebras/… (for example cerebras/gpt-oss-120b). Reasoning levels are offered per model, and usage is priced from Cerebras' own catalog. Conversations that switch to Cerebras from another model keep working: fields Cerebras rejects, such as prompt-cache markers, are removed before the request is sent.

Fixed

  • Long-prompt pricing: models that charge more once a prompt passes a size threshold are now recorded at that higher rate for the whole request, as the provider bills it. Before, every request was recorded at the base rate. This covers Gemini, Claude Sonnet and Grok above 200k tokens, Qwen above 32k, 128k or 256k, OpenAI's GPT models above 272k, and Novita's tiered models. Cache-write prices from each provider's own catalog are now kept too, where before a default rate was used.
VS Code

Update of VS Code, Sep 27, 2026

Added

  • The agent can read web pages and look up packages: give it a link to a docs page, a GitHub file or a changelog and it reads the page as Markdown; ask about a library and it looks up the latest version, release date and links on npm, PyPI, crates.io, the Go module proxy, NuGet or Maven Central. Both run on Tempr's servers, so they work in this version with no update, and neither needs a key; the chat shows them as "Running web_fetch" and "Running lookup_package" until the next release names the page or package. The agent only opens addresses that appeared in your messages, in its tools' results, or as links on a page it has already read, so it can't make up an address that sends your code somewhere. Tempr's servers can't reach your own network or localhost.
JetBrains

Update of JetBrains, Sep 27, 2026

Added

  • The agent can read web pages and look up packages. Give it a link to a docs page, a GitHub file or a changelog and it reads the page as Markdown; ask about a library and it looks up the latest version, release date and links on npm, PyPI, crates.io, the Go module proxy, NuGet or Maven Central. Both run on Tempr's servers, so they work in this version with no update, and neither needs a key; the chat shows them as "Running web_fetch" and "Running lookup_package" until the next release names the page or package. The agent only opens addresses that appeared in your messages, in its tools' results, or as links on a page it has already read, so it can't make up an address that sends your code somewhere. Tempr's servers can't reach your own network or localhost.
Visual Studio

Update of Visual Studio, Sep 27, 2026

Added

  • The agent can read web pages and look up packages. Give it a link to a docs page, a GitHub file or a changelog and it reads the page as Markdown; ask about a library and it looks up the latest version, release date and links on npm, PyPI, crates.io, the Go module proxy, NuGet or Maven Central. Both run on Tempr's servers, so they work in this version with no update, and neither needs a key; the chat shows them by their tool names until the next release names the page or package. The agent only opens addresses that appeared in your messages, in its tools' results, or as links on a page it has already read, so it can't make up an address that sends your code somewhere. Tempr's servers can't reach your own network or localhost.
CLI

0.9.3 of CLI, Sep 27, 2026

Added

  • Add your provider keys from the terminal. tempr keys add adds the key Tempr uses for a provider such as OpenAI, Anthropic or Google, with a picker when you don't name one; tempr keys lists your keys and tempr keys remove <provider> removes one. /keys does the same inside a session. The key is typed at a hidden prompt, piped in, or read with --from-env <VARIABLE>, never passed as an argument, where it would land in shell history. After saving, it says how many new models the key made available, and warns when it made none, which usually means the key is wrong. Azure, AWS Bedrock and custom endpoints still need the Portal's Provider keys page, since they take more than a key, and on a Team plan your organization's admin manages keys.

Changed

  • When your catalog is empty, tempr doctor, tempr auth, tempr models and /model now point you to tempr keys add instead of the Portal.
CLI

Update of CLI, Sep 27, 2026

Added

  • The agent can read web pages and look up packages. Give it a link to a docs page, a GitHub file or a changelog and it reads the page as Markdown; ask about a library and it looks up the latest version, release date and links on npm, PyPI, crates.io, the Go module proxy, NuGet or Maven Central. Both run on Tempr's servers, so they work in 0.9.3 with no update, and neither needs a key. The agent only opens addresses that appeared in your messages, in its tools' results, or as links on a page it has already read, so it can't make up an address that sends your code somewhere. Tempr's servers can't reach your own network or localhost; for those, the agent can still run curl with your approval. In 0.9.3, --allowed-tools and --disallowed-tools don't cover the two new tools; the next release does.
Portal

Update of Portal, Sep 27, 2026

Added

  • Novita AI: Novita AI is now available as a provider key for Chat, the Gateway and organization keys.
  • Cerebras: Cerebras is now available as a provider key for Chat, the Gateway and organization keys.
  • Rename your organization: owners and admins can rename the organization on the Members page. A new organization is named after the email its plan was bought with, and the page suggests a real name while it still is one. Each rename is recorded in the audit log.
  • Edit MCP servers. Each server on MCP credentials has an Edit panel for its name, command or URL, and variables. Saved values stay hidden: leave one empty to keep it, type a new one to replace it, or delete its line to remove it.
  • Page links: Logs, Sessions, End users, Agent traces and the Audit log now have Previous and Next, links to the first and last page, and "Page 4 of 8".
  • Creating a Gateway key now offers the same Content capture setting as editing one.

Changed

  • Saving a provider key on the Provider keys and Org keys pages now shows "Checking key…" with a spinner while Tempr checks the key with the provider, instead of the page appearing to hang.
  • The Playground's model box and the separate "Pick from your configured providers" list are now one field: it suggests your providers' models as you type and still takes any model id. It starts on one of your own models instead of Claude Sonnet.
  • Times across the Portal now show in your own time zone and in one format. They used to be the server's time (UTC), unlabelled.
  • Removing a key or server, revoking a key, signing out a device, regenerating a webhook secret and resetting personas now ask first, and slow buttons show that they're working.
  • Pages with nothing to show yet say what to do next, such as creating a key or trying the Playground, and settings messages, provider names and audit log entries read as plain words rather than codes like FlagOnly.
  • Get started now covers Visual Studio, VS Code and JetBrains IDEs, and points to View > Tempr in Visual Studio.
  • Members lists your people first, with the team-wide tools below. Org keys puts the shared provider keys first and shows Azure and AWS Bedrock settings only for those providers.
  • Wide tables scroll sideways on a phone instead of stretching the page.
  • New passwords need at least 10 characters everywhere, as they already did when creating an account.
  • Single sign-on setup is now two steps on the Single sign-on page: verify your email domains with a DNS record, then connect your identity provider. Tempr picks up both from the setup pages by itself, and only an email on a verified domain can sign in with SSO. Until single sign-on is available, the page says so and the sign-in page doesn't offer it.
  • Renaming your organization renames it on the single sign-on setup pages too.

Fixed

  • The Playground's model picker listed the models of only one of your providers when you had keys for several; the others were left out. It now lists every provider you have a key for.
  • Choosing the other plan on the Plan page started a second subscription with a second license key. It now switches your plan in Stripe's billing portal.
  • Saving a prompt template after restoring an older version failed.
  • Personas & commands rejected keys written the way its help text shows them ("name"), and a rejected publish threw away your edits. Both are fixed, and emoji and apostrophes no longer show as codes.
  • Reveal key on License keys stopped responding after you'd visited the page twice. The device list now shows only devices that are signed in, with when each sign-in expires.
  • A message that failed to send in the Playground stayed in the conversation, so retrying sent it twice.
  • Owners of a Gateway team couldn't invite anyone ("all purchased seats are in use"). Gateway teams have no per-seat limit, and joining one no longer comes with a Tempr Chat license.
  • An expired invite blocked inviting that person again. Inviting them again now sends a new link.
  • Org keys listed members' IDE sign-ins as virtual keys you could revoke.
  • Team members were told they had no license on Chat's Provider keys; the page now explains that their organization provides the keys.
  • Feature requests sent from an account without a Tempr Chat license didn't appear in its list.
  • Billing history kept warning about a failed payment after a later payment succeeded.
  • Signing in, resetting a password and resending a license key now find your account whatever capital letters you type your email with.
  • Chart axes no longer repeat labels such as "$0.5, $0.5".
  • The Playground's model field opened the browser's own suggestion list, which could appear beside the field, as tall as the window, with every model in it. It's now a list under the field that narrows as you type, and the arrow keys and Enter pick a model.
Portal

Update of Portal, Sep 26, 2026

Fixed

  • The confirmation and error messages on the Provider keys and Org keys pages now name the provider the way the page does, for example "Groq key saved." rather than "groq key saved.".
  • Fireworks AI is now listed as "Fireworks AI" on the Provider keys and Org keys pages, not "fireworks-ai".
  • The Gateway's Provider keys page labels each key field and Remove prompt with the provider's name ("Groq API key", not "groq API key"), and Org keys titles each provider's keys the same way.
Visual Studio

2.2.33 of Visual Studio, Sep 25, 2026

Fixed

  • On Visual Studio 2022 and early Visual Studio 2026 builds, signing in could fail with an assembly version error ("The located assembly's manifest definition does not match the assembly reference"). Every assembly the extension ships with is now registered, so Visual Studio loads the right one.
Visual Studio

2.2.32 of Visual Studio, Sep 24, 2026

Fixed

  • On Visual Studio 2022 and early Visual Studio 2026 builds, View > Tempr did nothing and Tools > Options > Tempr > General showed "An error occurred loading this property page". The extension now ships the System.Text.Json version it needs, with its dependencies.
Gateway

Update of Gateway, Sep 23, 2026

Added

  • Groq: Groq's hosted models are available with your Groq key as groq/… (for example groq/openai/gpt-oss-120b), with reasoning levels per model, and usage is priced from Groq's own catalog.
  • Cost tracking for Together AI, Fireworks AI and Hugging Face: usage on these providers used to be recorded at $0, so it didn't count toward spend limits, budgets or cost reports. It's now priced from each provider's own prices. A Fireworks request with service_tier: "priority" is charged Fireworks' Priority price, and a Hugging Face request is charged the rate of the provider that served it.
  • Model lists now show prices for Fireworks AI and Hugging Face models: the same prices usage is charged at.
  • Cohere's c4ai-aya-expanse-32b and command-a-03-2025 are now priced.

Changed

  • Together AI's model list now shows only models that can chat. Its image, video, audio and rerank models are no longer listed; its embedding models are still listed with ?type=embedding.

Removed

  • Meta's Llama API (meta-llama/…): Meta shut the Llama API down on 2026-07-06. A request naming one of its models now fails right away with 410 provider_retired, new keys for it aren't accepted, and its models are no longer listed.

Fixed

  • AWS Bedrock models that run only on Bedrock's Converse API: DeepSeek R1, Writer Palmyra X4 and X5, Pixtral Large and Mistral Large (2407) failed with a 404, because Tempr sent them to Bedrock's OpenAI-compatible endpoint, which doesn't serve them. They now work on /v1/chat/completions and /v1/messages, streaming or not, including tool calls. (Bedrock doesn't accept tools for DeepSeek R1.) A model Bedrock adds later that runs only on Converse is detected and routed there automatically.
Portal

Update of Portal, Sep 23, 2026

Added

  • Groq: Groq is now available as a provider key for Chat, the Gateway and organization keys.

Removed

  • Meta's Llama API: Meta shut the Llama API down on 2026-07-06, so it's no longer listed under provider keys and new keys for it aren't accepted. Llama models are still available through Together AI, DeepInfra, Hugging Face, Nscale, AWS Bedrock and OpenRouter. See Providers.

Fixed

  • Opening Stripe's billing portal from Billing history now brings you back to Billing history, including when you reached it from the Gateway section. It used to return to the Chat plan page.
  • Saving an AWS Bedrock key no longer fails with "the test request was rejected" when the model chosen for the test runs only on Bedrock's Converse API. The key is now checked there instead.
Gateway

Update of Gateway, Sep 22, 2026

Added

  • Other labs' models through Perplexity: your Perplexity key now also reaches the models Perplexity's Agent API serves directly, as perplexity/openai/gpt-5.6-luna, perplexity/anthropic/claude-opus-5, perplexity/google/gemini-3.8-flash and so on. They're listed with Perplexity's prices, billed at the cost Perplexity reports, and search the web with Perplexity's search tool. See Perplexity.
  • Other labs' reasoning on /v1/messages: when a Messages API request runs on a model that reasons outside Claude, such as DeepSeek, Z.AI, Moonshot or Xiaomi MiMo, its reasoning now comes back as a thinking block ahead of the text and tool calls, with thinking_delta events when streaming. Those blocks carry the signature tempr:reasoning. Send them back unchanged, as Claude Code does, and models that need their earlier reasoning across tool calls get it back as reasoning_content. When a later turn goes to Claude, Tempr leaves these blocks out, because Claude would reject their signature. See the Messages API section.

Changed

  • Perplexity now runs on Perplexity's Agent API, which replaces the Sonar chat completions it retires on 2026-09-27. Perplexity already refuses Sonar requests from newer API keys. The models are now its presets: perplexity/fast, low, medium, high and xhigh. The Sonar ids keep working, including in virtual-key allowlists, and run as the matching preset: sonar as fast, sonar-pro as low, sonar-reasoning-pro as medium, sonar-deep-research as high. Answers still return citations and search_results as Sonar did. Usage is billed at the cost Perplexity reports, which includes its web-search fees, and is returned as usage.cost. Presets set their own reasoning, so these models don't offer a reasoning level. See Perplexity.

Fixed

  • Perplexity rejected a function tool without a description. Tempr now sends the tool's name as its description.
  • Claude's thinking blocks on /v1/messages now keep Claude's own signature when Tempr translates the request: Claude on AWS Bedrock, OpenRouter's anthropic/… models, and Anthropic models with response caching. Claude 4.7 and later, whose thinking text is empty, now return their block instead of none, and redacted thinking comes back as a redacted_thinking block. Blocks you send back reach Claude on the next turn, so its reasoning carries through a tool call.
  • When Claude on AWS Bedrock or OpenRouter rejects a thinking block's signature sent back in a later turn, Tempr now retries once without that thinking instead of returning the 400, as it already did for Anthropic.
  • A response-cache hit for a request that was first answered as a stream now replays the model's reasoning along with the answer.
VS Code

1.1.7 of VS Code, Sep 22, 2026

Changed

  • Perplexity's Sonar models are now its Agent API presets, perplexity/fast, low, medium, high and xhigh, since Perplexity retires Sonar chat completions on 2026-09-27. A Sonar model you had picked moves to its replacement by itself, so it stays selected: sonar becomes fast, sonar-pro becomes low, sonar-reasoning-pro becomes medium, and sonar-deep-research becomes high. That covers your chat model, inline-completion model, per-agent models and each saved chat's model.

Fixed

  • The extension's Marketplace description now says what it does with your data: requests go through Tempr's server to the model you picked, on your own provider key, and chat history syncs to your Tempr account unless you turn Cloud sync off. It used to say chat history stayed on your machine. It also lists Teams plans as available, from $35 per seat per month (10-seat minimum), instead of coming soon.
JetBrains

1.1.7 of JetBrains, Sep 22, 2026

Changed

  • Perplexity's Sonar models are now its Agent API presets, perplexity/fast, low, medium, high and xhigh, since Perplexity retires Sonar chat completions on 2026-09-27. A Sonar model you had picked moves to its replacement by itself, so it stays selected: sonar becomes fast, sonar-pro becomes low, sonar-reasoning-pro becomes medium, and sonar-deep-research becomes high. That covers your chat model, inline-completion model and per-agent models.

Fixed

  • The plugin's Marketplace description now says what it does with your data: requests go through Tempr's server to the model you picked, on your own provider key; chat history syncs to your Tempr account unless you turn Cloud sync off; and error reports are sent automatically unless you turn them off. It used to say chat history stayed on your machine.
JetBrains

1.1.6 of JetBrains, Sep 22, 2026

Added

  • Cloud sync switch: Tempr Settings now has a Cloud sync switch in the Account card. Turn it off and Tempr stops storing your chats, custom agents and tool preferences on your Tempr account; your chats stay on this machine. The switch belongs to your account, so it covers every machine and every Tempr extension signed in to it, and you can also change it in the Tempr Portal. Turning it off offers to delete what's already stored, and Delete synced data does that at any time. Sync stays on unless you turn it off.
Visual Studio

2.2.31 of Visual Studio, Sep 22, 2026

Changed

  • Perplexity's Sonar models are now its Agent API presets, perplexity/fast, low, medium, high and xhigh, since Perplexity retires Sonar chat completions on 2026-09-27. A Sonar model you had picked moves to its replacement on its own, so it stays selected: sonar becomes fast, sonar-pro becomes low, sonar-reasoning-pro becomes medium, and sonar-deep-research becomes high. That covers your chat model, inline-completion model and per-persona models.
Visual Studio

2.2.30 of Visual Studio, Sep 22, 2026

Added

  • Cloud sync switch: Tools > Options > Tempr > General has a new setting, Sync chats and settings to your Tempr account. Turn it off and Tempr stops storing your chats, tool preferences, custom agents and code search index on your Tempr account. Your chats stay on this machine. The setting belongs to your account, so it covers every machine and every Tempr extension signed in to it, and it takes effect as soon as you change it. When you turn it off, Tempr asks whether to also delete what's already stored. Delete synced data... does that at any time and ends any share links. Sync stays on unless you turn it off.

Fixed

  • Your solution's code search index never reached your Tempr account: every upload failed without a message. Uploads now work, and each solution's existing local index is uploaded once. Until the synced index has caught up, search keeps ranking with the index on your machine, so results never get worse while it fills.
CLI

0.9.2 of CLI, Sep 22, 2026

Changed

  • Perplexity's Sonar models are now its Agent API presets, perplexity/fast, low, medium, high and xhigh, since Perplexity retires Sonar chat completions on 2026-09-27. A Sonar model you had saved moves to its replacement the next time the CLI starts, so it still matches tempr models: sonar becomes fast, sonar-pro becomes low, sonar-reasoning-pro becomes medium, and sonar-deep-research becomes high. That covers your default model, per-persona models and reasoning picks.
CLI

0.9.1 of CLI, Sep 22, 2026

Changed

  • An unknown flag is an error. A mistyped option such as --aproval-mode bypass now stops with "Unknown option" and exit code 2. Before, the CLI dropped it silently and ran anyway, in this case in the default approval mode. To send a prompt that starts with a dash, put -- before it.

Fixed

  • A command line that doesn't parse, such as an extra word after the prompt, now exits 2 as documented. It exited 255 (127 from Git Bash).
  • A run whose saved session can't be used, because it has no token or expired and couldn't be refreshed, now exits 3 (not signed in) instead of 1.
  • When tempr doctor can't reach the server, it now names the variable that sets it, TEMPRAPP_SERVER_URL (or serverUrl in config.json). It named TEMPR_SERVER_URL, which the CLI doesn't read.
Gateway

Update of Gateway, Sep 21, 2026

Added

  • POST /v1/embeddings. OpenAI's embeddings API on your own provider keys: OpenAI, Azure OpenAI, Azure AI Foundry, Google, Mistral, Cohere, AWS Bedrock (Titan Text and Cohere Embed), DeepInfra, Together AI, Fireworks AI, Nscale, OpenRouter and custom models. encoding_format: "base64" works on every provider, and input_type passes the document or query hint to Cohere and Gemini. The same keys, allowlists, limits, budgets, fallback chains and request logs apply as for chat, and cost is input tokens only. See Embeddings.
  • OpenAI's pro and codex models: OpenAI serves models such as gpt-5-pro, o3-pro and gpt-5.3-codex only on its Responses API, so they used to fail on /v1/chat/completions and /v1/messages. Tempr now bridges those calls to the Responses API and back, streaming included.
  • Xiaomi MiMo v2.6: MiMo v2.6 models are listed and priced.

Changed

  • /v1/models lists chat models only by default. Tools that fill a chat model picker from it no longer get embedding models. Add ?type=embedding for the embedding models, or ?type=all for both. Each model now has a type of language or embedding.
  • Reasoning effort max on newer OpenAI models: gpt-5.6, its luna, sol and terra variants, and gpt-6-astra take max only on OpenAI's Responses API. A request at max now goes there, and gets the deepest reasoning, instead of quietly running at the model's default.
  • Function tools on those models: a request with function tools and reasoning on now goes straight to the Responses API. The same model's other requests stay on chat completions, where parameters like stop and seed still apply.
  • When a provider rejects the reasoning level you asked for, Tempr now retries at the nearest level the provider lists instead of dropping reasoning altogether. x-tempr-reasoning-effort reports what the retry sent.
  • OpenAI models past their shutdown date, and OpenAI's completions-only models, are no longer listed.
  • Xiaomi's speech and transcription models are no longer listed, since they don't chat.

Deprecated

  • Xiaomi MiMo v2.5: mimo-v2.5 and mimo-v2.5-pro stop working at Xiaomi on 2026-10-21 at 02:00 UTC and leave the model list then. Move to MiMo v2.6.

Fixed

  • Tool calls from Google's Gemini and Gemma models came back with finish_reason: "stop" (end_turn on /v1/messages), so agent loops ended the turn instead of running the tool. They now return tool_calls (tool_use).
  • Turning reasoning off for Gemma 4 on the Gemini API failed with a 400, and turning it on had no effect. Both now work.
  • A connection to a provider that dropped before it answered ended in a 500. Tempr now retries it like a provider 5xx, and then answers 502 upstream_unreachable, so fallback chains and backup keys take over.
  • Usage on Xiaomi MiMo models was recorded at $0. It's now priced.
  • /v1/messages requests to gpt-6 models failed on max_tokens. GPT-6 models now get max_completion_tokens and no temperature, as GPT-5 models do.
VS Code

1.1.6 of VS Code, Sep 21, 2026

Added

  • Cloud sync switch. Tempr: Open Settings now has a Cloud sync switch in the Account card. Turn it off and Tempr stops storing your chats, custom agents and tool preferences on your Tempr account; your chats stay on this machine. The switch belongs to your account, so it covers every machine and every Tempr extension signed in to it, and you can also change it in the Tempr Portal. Turning it off offers to delete what's already stored, and Delete synced data does that at any time. Sync stays on unless you turn it off.
JetBrains

1.1.5 of JetBrains, Sep 21, 2026

Fixed

  • If your IDE can't run its built-in browser (JCEF), for example because it was started on a Java runtime without it, Tempr no longer raises an IDE error every time a project opens. The Tempr panel instead explains why the chat can't start, with a link to Choose Boot Java Runtime for the IDE so you can switch to a runtime that includes JCEF.
Visual Studio

2.2.29 of Visual Studio, Sep 21, 2026

Security

  • Automatic error reports no longer include your license key. A report is now linked to your account by your signed-in session. It carries only that session's activation ID, the error message and the stack trace.
Portal

Update of Portal, Sep 21, 2026

Added

  • Cloud sync switch: the Profile page has a Cloud sync card. Turn it off and the Visual Studio, VS Code and JetBrains extensions stop storing your chats, tool preferences, custom agents and code search index on Tempr's servers. It's one setting for your whole account, so it covers every machine and every extension signed in to it. Sync stays on unless you turn it off, and Delete synced data removes what's already stored at any time.
  • Team request logs: organization owners and admins can now read the requests made with the organization's keys, under Organization > Team request logs. The list shows metadata only; opening a request that holds captured content is recorded in the organization's audit log.

Changed

  • Closing your account takes effect straight away. Close account has moved to the Profile page, where every user can reach it. It now deletes your account and everything tied to it at once: license keys, synced chats and settings, provider keys, Gateway keys and logs, MCP credentials, prompt templates, sign-in history and usage history. Your subscriptions are cancelled, and any unbilled Gateway overage is charged first. If you own an organization, it closes too and its members are emailed; their own accounts stay. To use the rest of a paid period, cancel from the Plan page first and close your account later. See the privacy policy.
  • Sign-in locations on the Security page are now worked out on Tempr's own servers, so your sign-in IP addresses are no longer sent to an outside lookup service. The page also loads faster.
  • Very small Gateway costs now read "<$0.0001" instead of "$0.0000".

Fixed

  • Saving a custom model endpoint that answers slowly now shows a spinner while it's checked, ignores a second click, and ends with a clear timeout message naming the step that ran out of time. An endpoint that's out of credit says so.
  • The Playground's model list no longer repeats the provider name in model ids (such as openai/openai/gpt-5), which made those requests fail.
  • Azure OpenAI deployments that only work through OpenAI's Responses API can now be saved.
  • The org-wide Sessions and End users pages no longer link to a detail page that couldn't open.

Security

  • Captured Gateway request content is now redacted in every case where redaction applies.
  • When a Team subscription ends, or an owner removes a member, that member's Team access and signed-in devices end straight away.
  • Organization invitations can only grant the Member or Admin role.
Gateway

Update of Gateway, Sep 20, 2026

Added

  • Nscale: Nscale's hosted open-weight models are available with your Nscale key as nscale/…, and usage is priced from Nscale's catalog.
  • Reasoning control on inference hosts: the reasoning object and reasoning_effort now work on DeepInfra, AWS Bedrock, Together AI and Fireworks AI, each in the host's own format. On Bedrock, Claude gets thinking and effort, and Amazon Nova 2 gets its reasoning config. A few models report no levels because their host can't steer them reliably, such as GLM on Together AI. Hugging Face reports none because it routes each model to a host it picks. GET /v1/models shows each model's reasoning_options. See Reasoning.

Fixed

  • Claude on AWS Bedrock now returns its reasoning as reasoning and reasoning_details, and reasoning you send back reaches the model, which a thinking Claude needs across a tool call.
JetBrains

1.1.4 of JetBrains, Sep 20, 2026

Changed

  • Google's Gemini models are now listed as google/… instead of gemini/…, the same name OpenRouter, Vercel's AI Gateway and models.dev give them, so a model id copied from any of those works in Tempr as it is. Nothing you have set needs changing: your chat model, inline-completion model, per-agent models and reasoning levels follow the new name by themselves, and the old gemini/… name keeps working everywhere.
Visual Studio

2.2.28 of Visual Studio, Sep 20, 2026

Changed

  • Google's Gemini models are now listed as google/… instead of gemini/…. That's the name OpenRouter, Vercel's AI Gateway and models.dev give them, so a model ID copied from any of those works in Tempr as it is. You don't need to change anything: your chat model, inline-completion model, per-persona models and reasoning levels move to the new name on their own, and the old gemini/… name still works everywhere.
CLI

0.9.0 of CLI, Sep 20, 2026

Added

  • First public release: Tempr's bring-your-own-key coding agent in the terminal, on the same license, provider keys and models as the IDE extensions. Sign in with tempr auth, pick a default model with tempr config set-model <id>, and tempr doctor checks that everything is set up. The quickstart walks through it, and the command reference lists every command and flag.
  • Install in one line: curl -fsSL https://temprhq.io/cli/install.sh | sh on macOS and Linux, or irm https://temprhq.io/cli/install.ps1 | iex on Windows. The builds are self-contained, so nothing needs installing first. Direct downloads for Windows, macOS and Linux on x64 and Arm64 are on the CLI page, each with a .sha256 beside it, and tempr update tells you when a newer release is out and how to install it.
  • Three ways to run: tempr "<prompt>" runs one agent turn and exits, tempr on its own opens an interactive session with persistent history, line editing and Tab completion, and <something> | tempr reads its prompt from piped input for scripts. tempr --ask "<prompt>" is plain chat with no tools.
  • A real agent loop: the agent reads, writes and edits files, runs commands, searches your code by meaning and by symbol, reads build diagnostics, and discovers and runs tests, all against the current directory. Every file path is checked against the workspace, including through symbolic links and Windows junctions.
  • Approval modes: file edits, commands and MCP calls ask first by default (interactive). autopilot runs edits and allow-listed commands unattended and still asks before anything that deletes, force-pushes, resets or reboots; bypass runs edits and asks for every command. Set the default with tempr config set-approval-mode, or use --approval-mode or -y for one run. Add allow-listed commands with tempr config allow-command, or per repository in an .agentcommands.json file.
  • Personas and your own agents: tempr "@debugger why does this fail" runs a specialist persona, and /persona switches for the rest of a session. Your own slash commands and agents are Markdown files in .tempr/commands/ and .tempr/agents/, in a project or in your home folder.
  • Context in a message: @path/to/file attaches a file (images go in as images), @workspace adds an overview of the workspace, and @problems adds your current build errors. Every agent turn also carries AGENTS.md and .github/copilot-instructions.md from the current directory, plus a global ~/.tempr/AGENTS.md. tempr init drafts an AGENTS.md from a scan of the workspace.
  • Sessions you can pick up again: every session is saved and encrypted at rest. tempr -c resumes this folder's most recent one, /resume picks from a list, --id resumes a specific one, and tempr history lists, shows, renames, forks and deletes them. /diff shows what the last turn changed on disk and /undo puts it back, skipping any file that has changed since.
  • Models and reasoning: tempr models lists the models your license can use, with prices and context sizes, and /model opens a picker over them. -m overrides the model for one run. /reasoning sets how much the model reasons, saved per model, and --reasoning overrides it for one run.
  • MCP servers: tempr mcp add connects your own Model Context Protocol servers, tempr mcp browse installs one from Tempr's curated catalog, and list, remove, enable and disable manage them.
  • Scripting and CI: --json writes one event per line and then a final result object, and the exit code says how the run ended (finished, failed, a usage error, not signed in, step limit reached, a tool call refused, or interrupted). --max-turns, --allowed-tools, --disallowed-tools and --prompt-file shape an unattended run, and TEMPR_LICENSE_KEY signs in without putting the key on a command line. With no terminal to ask on, a tool call that would have asked is refused instead of waiting. See Scripts, pipes & CI.
  • Usage and cost: --verbose prints token usage and cost after each turn, and tempr usage shows what this machine's turns have cost, by model.
  • Shell completion: tempr completion bash|zsh|fish|powershell prints a completion script.
  • Crash reports are opt-in. The first interactive session asks once, and tempr config set-crash-reports on|off changes it. Nothing is sent without a terminal to ask on, or when CI, DO_NOT_TRACK or TEMPR_NO_CRASH_REPORTS is set. There's no other telemetry.
Portal

Update of Portal, Sep 20, 2026

Added

  • Nscale: Nscale is now available as a provider key for Chat, the Gateway and organization keys.
  • Reasoning in the Playground: a Reasoning dropdown in the Gateway Playground sets how much the model thinks before it answers, from Off to Max, or the model's own default. Each reply shows the level that was actually applied, since a level the model lacks is sent as the nearest one it has.

Changed

  • Google's Gemini API key is now listed as Google Gemini, and Gateway usage, logs and analytics show Gemini models under google/. Keys, allowlists and fallback chains you saved under the old name keep working.
Gateway

Update of Gateway, Sep 19, 2026

Added

  • Reasoning control: set how much a model thinks with OpenRouter's reasoning object or OpenAI's reasoning_effort on /v1/chat/completions, thinking and output_config.effort on /v1/messages, or reasoning.effort on /v1/responses. Tempr sends it in each lab's own format. A level the model lacks becomes the nearest one it has, and the x-tempr-reasoning-effort response header says what was applied. A malformed value returns 400 invalid_reasoning. See Reasoning.
  • Claude's reasoning on chat completions: Claude's thinking now comes back as reasoning and reasoning_details, streamed and not. Send the assistant message back with reasoning_details unchanged and Claude gets its thinking blocks, which a tool-calling turn needs.
  • Refusals you can see: a model that declines now finishes with content_filter, as in OpenAI's API, with Claude's explanation in the refusal field (delta.refusal when streaming). Before, Claude's refusals read as an empty, normal stop. Gemini's safety, recitation and blocked-prompt stops are content_filter too. /v1/messages reports a refusal with stop_details, and /v1/responses as a refusal content part. Refusals are never cached.

Changed

  • Google's Gemini models are now google/… instead of gemini/…, the same prefix OpenRouter, Vercel's AI Gateway and models.dev use. gemini/… keeps working permanently, and your keys' allowlists and fallback chains were updated to match.

Fixed

  • Requests to openrouter/… models were rejected by OpenRouter with a 400, and an OpenRouter stream could be cut off right after [DONE].
  • Gemini's thinking tokens are now counted in usage.
  • A model id using a provider's older name, such as azure_openai/…, could reach the provider with that prefix still on it and fail. Old names now resolve fully.
VS Code

1.1.4 of VS Code, Sep 19, 2026

Changed

  • Google's Gemini models are now listed as google/… instead of gemini/…, the same name OpenRouter, Vercel's AI Gateway and models.dev give them, so a model id copied from any of those works in Tempr as it is. Nothing you have set needs changing: your chat model, inline-completion model, per-agent models and reasoning levels follow the new name by themselves, and the old gemini/… name keeps working everywhere.
VS Code

1.1.3 of VS Code, Sep 19, 2026

Added

  • Reasoning level. A Reasoning dropdown beside the model dropdown sets how much the model thinks before it answers: Default (the model's own setting), Off, or the levels that model offers, from Minimal to Max. Tempr remembers your pick for each model, and it applies when you use a Tempr model from Copilot Chat too. The dropdown only appears for models that have reasoning control, and a level a model lacks is sent as the nearest one it has.

Fixed

  • After you first signed in, the model dropdown could stay empty for up to five minutes. It now fills in right away.
JetBrains

1.1.3 of JetBrains, Sep 19, 2026

Added

  • Reasoning level. A Reasoning dropdown beside the model dropdown sets how much the model thinks before it answers: Default (the model's own setting), Off, or the levels that model offers, from Minimal to Max. Tempr remembers your pick for each model. The dropdown only appears for models that have reasoning control, and a level a model lacks is sent as the nearest one it has.

Fixed

  • The Tempr tool window's sidebar icon was drawn at the full size of the logo. It's now the same size as the other tool window icons, in both the classic and the new UI.
Visual Studio

2.2.27 of Visual Studio, Sep 19, 2026

Added

  • Reasoning level: a new Reasoning dropdown beside the model dropdown sets how much the model thinks before it answers. The choices are Default (the model's own setting), Off, and whichever levels that model offers, from Minimal to Max. Tempr remembers your choice for each model. The dropdown only appears for models that support reasoning control, and a level a model doesn't have is sent as the nearest one it does.
VS Code

1.1.2 of VS Code, Sep 16, 2026

Added

  • Settings follow you with Settings Sync. With VS Code Settings Sync turned on, your Tempr settings reach your other machines: the chat model, approval mode, inline completions, agent limits, chat font size and the rest. MCP servers and auto-approved commands stay on each machine, and custom agents keep syncing through your Tempr account.

Security

  • A repository's .vscode/settings.json can no longer point Tempr at a different server. The development override moved from the tempr.serverUrl setting to the TEMPRAPP_SERVER_URL environment variable, the same one Visual Studio reads.
  • A repository's .vscode/settings.json can no longer change Tempr's settings, such as switching approval mode to Autopilot, pre-approving commands, or adding MCP servers or custom agents. Tempr now reads tempr.* values only from your user settings.
  • A symbolic link or Windows junction inside your workspace can no longer lead Tempr's file tools outside it. Reading, writing, patching and searching files now follow a link to where it really goes, and refuse it when that's outside the workspace.
  • Every spelling of a delete command is now treated as destructive, so it asks for approval every time, in every approval mode, and can't be trusted for the session. Before, rm -fr and Remove-Item -Force -Recurse weren't recognized, so approving rm -fr build once trusted rm -fr on any path for the rest of the session. Tempr now goes by the command itself (rm, rmdir, rd, del, erase, Remove-Item, ri, unlink), whatever its flags or a sudo in front.
JetBrains

1.1.2 of JetBrains, Sep 16, 2026

Security

  • A symbolic link or Windows junction inside your project can no longer lead Tempr's file tools outside it. Reading, writing, patching, listing and searching files now follow a link to where it really goes, and refuse it when that's outside the project.
  • Every spelling of a delete command is now treated as destructive, so it asks for approval every time, in every approval mode, and can't be trusted for the session. Before, rm -fr and Remove-Item -Force -Recurse weren't recognized, so approving rm -fr build once trusted rm -fr on any path for the rest of the session. Tempr now goes by the command itself (rm, rmdir, rd, del, erase, Remove-Item, ri, unlink), whatever its flags or a sudo in front.
Visual Studio

2.2.26 of Visual Studio, Sep 16, 2026

Security

  • A symbolic link or Windows junction inside your solution can no longer lead Tempr's file tools outside it. Reading, writing, patching, listing and searching files now follow a link to where it really goes, and refuse it if that's outside the solution. A link that points back at one of its own parent folders no longer sends a search into a loop.
  • Every spelling of a delete command now counts as destructive, so it asks for approval every time, in every approval mode, and can't be trusted for the session. Before, rm -fr and Remove-Item -Force -Recurse weren't recognized, so approving rm -fr build once trusted rm -fr on any path for the rest of the session. Tempr now goes by the command itself (rm, rmdir, rd, del, erase, Remove-Item, ri, unlink), whatever its flags and even with sudo in front.
Gateway

Update of Gateway, Sep 15, 2026

Added

  • Custom models: call models on your own OpenAI-compatible server (vLLM, SGLang, LiteLLM and others) as custom/<alias>, on every Gateway plan. Add the endpoint and its models in the Portal; Tempr checks each with a test call before saving, and you can give each model its own prices. See Custom models.

Fixed

  • An error from a custom endpoint now names the endpoint, for example "The custom endpoint 'Prod vLLM' rejected its key (401)".
  • A provider error whose error field is a plain string, such as {"error": "Model is loading"}, came back as a 500 from Tempr. It now comes back as the provider's error.

Security

  • Tempr doesn't follow redirects from a custom endpoint. A redirect is answered with a 502 that says so.
Portal

Update of Portal, Sep 15, 2026

Added

  • Authenticator app sign-in: on the Profile page you can set up an authenticator app (such as Google Authenticator, Microsoft Authenticator or 1Password) and get ten single-use recovery codes. Sign-in then asks for a code from the app. Unlike an emailed code, it still protects your account if someone gets into your email, so emailed codes stop working once an app is set up. Signing in with a recovery code emails you with how many are left.
  • Require two-factor for owners and admins: an organization owner can require an authenticator app for the organization's owners and admins. Anyone it covers is asked to set one up before using the rest of the Portal. Members who sign in with single sign-on are exempt, since your identity provider handles that.
  • Dark mode: choose System, Light or Dark from the theme menu in the sidebar or the Appearance card on the Profile page. System follows your device.
  • Custom models: connect your own OpenAI-compatible endpoint (vLLM, a hosted inference service and so on) and add its models under your own names. Tempr tests the endpoint before saving it and can list the models it serves. It's on the Gateway's Provider keys page, on Org keys for teams, and on Chat's Provider keys page for Pro licenses. Custom models have no price, so budget pages show their token use separately. See custom models.
  • The Security page's sign-in history now shows how each sign-in was made.
  • Chat's Provider keys page now reminds accounts that also have the Gateway that Gateway provider keys are set up separately.

Changed

  • Text and form field borders now meet WCAG contrast guidelines in both light and dark themes.
Gateway

Update of Gateway, Sep 14, 2026

Changed

  • Quotas follow your billing period. The monthly allotment, overage cap and overage metering now count from the day your paid plan started, not the calendar month, and x-tempr-quota-resets reports that date. Free plans keep the calendar month. Quota alerts now fire again each period; before, an account alerted once was never alerted again.
  • Changing paid plans: moving between Gateway Pro and Scale, or between team plans, now updates your subscription in place and takes effect right away, prorated, instead of starting a second subscription.

Fixed

  • Cancelling and resubscribing, or changing plan, within a month could bill that month's overage twice.
  • Overage used in the last hour of a billing period, or before a cancellation, is now billed on that period's invoice.
JetBrains

1.1.1 of JetBrains, Sep 14, 2026

Fixed

  • Agent turns no longer lose their connection when the chat goes quiet for more than ten seconds, such as while a model thinks or a tool waits for your confirmation. Before, a long enough quiet stretch could end the turn with "Lost connection to the agent run".
Portal

Update of Portal, Sep 14, 2026

Added

  • Gateway billing: personal and team Gateway plans now have a Manage billing button, and Billing history lists Gateway invoices, labelled by plan.
  • Manage Team seats: owners and admins see their Team plan and seats in use on the Plan page, with a Manage seats & billing button to add or release seats.
  • Allowed MCP servers per key: Gateway keys and org keys can be limited to a list of MCP servers.
  • Gateway-only accounts get a Try Tempr Chat link in the sidebar.

Changed

  • A new look: every Portal page has been redesigned with the same type and colours as temprhq.io, a lighter sidebar with your account at its foot, and a slide-out menu on small screens. Some pages have clearer names: BYOK is now Provider keys, Org config is Personas & commands, SSO is Single sign-on, Compliance is Audit log, and Gateway home is Overview.
  • Switching between Gateway Pro and Scale, for yourself or your team, now changes your current plan straight away with a prorated charge, instead of starting a new checkout.
  • Gateway quotas and overage now count from the start of your billing period instead of the calendar month, so resubscribing starts you with a fresh allowance. Quota alert emails now arrive again each period.
  • The Org keys page now explains that Team chat, like the Gateway, moves on to your organization's backup keys when a key is rejected or rate-limited.
  • Error text in agent traces is now always redacted.

Fixed

  • Turning on emailed two-factor codes from the Profile page didn't take effect.
  • Cancelling and resubscribing to a Gateway plan in the same month could bill that month's overage twice.
  • Budget charts could break when you went back to the Budget page from the sidebar.
  • Messages shown after a redirect, such as being sent to Provider keys from the Playground, were sometimes lost.
Gateway

Update of Gateway, Sep 13, 2026

Removed

  • /v1/chat/stream and /v1/chat/tools: these older organization-key chat routes now answer 410 endpoint_retired. Use /v1/chat/completions, which takes the same keys and enforces the same limits.

Security

  • Tightened checks on webhook and remote MCP server addresses each time Tempr connects to them. Tempr no longer follows redirects from either; a remote MCP server that answers with a redirect returns 502.

Fixed

  • Usage from many simultaneous requests on one account could go partly unrecorded, under-counting spend in budgets and analytics.
VS Code

1.1.0 of VS Code, Sep 13, 2026

Added

  • Explain, Fix, and Write Tests from the editor: right-click in a file and choose Tempr to send the selection (or the whole file, with nothing selected) to the chat as /explain, /fix, or /tests. They're in the Command Palette too, as Tempr: Explain, Tempr: Fix, and Tempr: Write Tests.
  • Generate Commit Message: a sparkle button in a Git repository's Source Control title bar writes a message for the staged changes (or the unstaged ones, when nothing is staged) into the commit box, following the style of the repository's recent commits. It asks before replacing a message you've already typed.
  • Open Chat shortcut: Ctrl+Shift+Alt+T (Ctrl+Cmd+T on macOS).
  • Get Started with Tempr. A walkthrough on VS Code's Welcome page: sign in, open the chat, the editor menu, and settings.
  • Accessibility: screen readers now hear when a reply finishes, when a reply fails, and when a tool call is waiting for confirmation. Chat tabs, the mode, approval mode, and model dropdowns, the attach menu, and chat history all work from the keyboard. The history, license, and tools panels and the settings dialogs behave as dialogs (focus moves in, stays in, and returns when they close), and keyboard focus is always visible.

Changed

  • The Tempr Settings screen uses Tempr's own theme colors, matching the chat panel beside it, instead of the current VS Code theme's.
  • Editing a message you've already sent is hidden for now: saving an edit never worked in VS Code, and it comes back once it does.
  • If the Tempr server speaks a newer agent-run protocol than this version understands, the extension says so once per session, instead of failing in unclear ways.
  • When an agent turn can't start on the server and falls back to running in the extension, that is now counted in the anonymous error diagnostics (still controlled by the diagnostics setting in Tempr Settings).

Fixed

  • A tool call Tempr ran in VS Code could have its result overwritten by the server's summary, for example "Read 12 lines." becoming "Done", or a rejected call turning into an error.
  • In @tempr chat, a tool call the server rejected as unknown could show a stray "Error" progress line.
  • The chevron on the pending changes panel did nothing when clicked.
JetBrains

1.1.0 of JetBrains, Sep 13, 2026

Added

  • Accessibility: screen readers now hear when a reply finishes, when it fails, and when a tool call is waiting for confirmation. Chat tabs, the mode, approval mode, and model dropdowns, the attach menu, and chat history all work from the keyboard. The history, license, and tools panels and the settings dialogs behave as dialogs, and keyboard focus is always visible.
  • Vault MCP servers in settings: MCP servers assigned to your account in Tempr's vault now appear in the Tempr Settings MCP list, as read-only cards.
  • Sub-agent cards: when the agent delegates work to a sub-agent on the server, the delegation now shows as a tool card in the chat, with the sub-agent's messages under it.

Changed

  • If the Tempr server speaks a newer agent-run protocol than this version understands, the plugin says so once per session instead of failing in unclear ways.
  • Editing a message you've already sent is hidden for now: saving an edit never worked in JetBrains IDEs, and it comes back once it does.
Visual Studio

2.2.25 of Visual Studio, Sep 13, 2026

Changed

  • If the Tempr server uses a newer agent protocol than your version of the extension understands, Tempr tells you so instead of failing in unclear ways.
  • The extension's Marketplace description no longer mentions inline chat, which is turned off for now.

Fixed

  • When the agent ran on the Tempr server, a tool you approved and Visual Studio ran could have its result replaced by the server's generic summary. For example, "Read 12 lines." became "Done", or a rejected call showed as an error. Results now keep their real summaries.
Portal

Update of Portal, Sep 13, 2026

Added

  • Prompt caching settings: turn on automatic prompt caching for Anthropic models across your Gateway account or team, choose a 5-minute or 1-hour cache, and override it per key. Request logs and Analytics show cache reads, writes and savings.
  • DeepInfra: DeepInfra is now available as a provider key for Chat, the Gateway and organization keys, with usage priced at DeepInfra's own rates.
  • Backup keys for teams: Org keys can hold more than one key per provider, used in turn and skipped while a key is rate-limited or failing. Analytics and Provider keys show when a key or model is cooling down, and until when.
  • Content capture per key: each Gateway key can now turn request and response capture on or off, or follow the account setting, so a development key can keep full logs while a production key keeps metadata only. Redaction of captured content is on by default for new Gateway accounts.

Changed

  • Webhook and remote MCP server URLs must now point to public internet addresses.

Fixed

  • Errors and missing pages now show a proper error page instead of a blank one.

Security

  • The Portal now sends standard browser security headers and enforces HTTPS on every page.
Gateway

Update of Gateway, Sep 11, 2026

Added

  • POST /v1/responses: OpenAI's Responses API, the format Codex CLI speaks. OpenAI models and Azure OpenAI deployments pass straight through, so reasoning items, hosted tools and previous_response_id work as they do directly. Every other model is translated: hosted tools are dropped and named in the x-tempr-unsupported-tools header. See the Codex CLI guide.
  • Native Anthropic on /v1/messages: anthropic/… models now pass straight through to Anthropic, so extended thinking, server tools, anthropic-beta features and cache breakpoints work as they do against Anthropic directly.
  • Fallback chains and backup keys on every endpoint: /v1/messages and /v1/responses now try the next model in a chain, and the next key for a provider, just as chat completions does.
  • DeepInfra: DeepInfra's models are available with your DeepInfra key as deepinfra/…, priced from DeepInfra's catalog, cached input included.
  • Content capture per key: each virtual key can now inherit the account's content capture setting or turn it on or off, so a development key can keep full request logs while a production key logs metadata only. Redaction of captured content is now on by default for new accounts.

Changed

  • Rate limits: a 429 now sits out only the model it was for, not the provider's other models, and a wait the provider asks for is honored from the first failure. When that wait is longer than ten seconds, the 429 or 503 comes back at once with Retry-After instead of Tempr waiting it out. See retries and fallback.

Fixed

  • OpenAI's o-series and GPT-5 models were rejected when a request set max_tokens or temperature. They now get max_completion_tokens and no temperature.
  • OpenAI's dated model snapshots, Claude's dashed model ids, Azure deployments, and Amazon and Anthropic models on Bedrock could be recorded at $0. They're now priced.
Gateway

Update of Gateway, Sep 10, 2026

Added

  • Prompt caching: turn it on for the account (5-minute or 1-hour cache), per key, or per request with x-tempr-prompt-cache, and Tempr places Anthropic's cache breakpoints for you, sorts tools into a stable order, and keeps requests that share a prompt on the same provider key. Cache reads and writes are billed at their own prices, and request logs show cached tokens and estimated savings. See prompt caching.

Changed

  • /v1/messages keeps the cache breakpoints a client sets itself, like Claude Code's, and returns Anthropic's split of input, cache-read and cache-write tokens in usage.

Fixed

  • A streamed /v1/messages response on a translated model reported 0 output tokens.
Portal

Update of Portal, Sep 9, 2026

Added

  • Gateway sign-up and paid plans: you can now create a free Gateway account from the Portal's sign-up page, no card or Chat license needed, and upgrade to Pro or Scale from the Gateway Plan page. Choosing a paid plan on temprhq.io takes you straight to checkout once you've verified your email, even if you open the email on another device.

Changed

  • The Gateway Plan page is now for managing your plan; compare plans on the pricing page.

Fixed

  • Azure OpenAI, Azure AI Foundry and AWS Bedrock keys can now be fully set up on the Gateway's Provider keys page, with the endpoint, deployment, region and model fields and the live check Chat already had. Before, the key saved but couldn't be used.
VS Code

1.0.8 of VS Code, Sep 8, 2026

Fixed

  • MCP tool calls to Anthropic models could fail outright: qualified MCP tool names ({server}.{tool}) contained a ., which Anthropic's API rejects in a tool name. Qualified names now use {server}__{tool} instead, matching the Tempr CLI and the Visual Studio and JetBrains extensions.
JetBrains

1.0.2 of JetBrains, Sep 8, 2026

Fixed

  • MCP tool calls to Anthropic models could fail outright: qualified MCP tool names ({server}.{tool}) contained a ., which Anthropic's API rejects in a tool name. Qualified names now use {server}__{tool} instead, the same as Tempr's other extensions and the CLI.
  • An agent turn no longer fails when the connection drops or stalls partway through. Tempr reconnects and picks the turn up where it left off, without repeating anything you've already seen, and only gives up after several attempts.
Visual Studio

2.2.24 of Visual Studio, Sep 8, 2026

Fixed

  • MCP tool calls to Anthropic models could fail outright. MCP tool names were shown to the model as {server}.{tool}, and Anthropic's API doesn't allow a . in a tool name. They are now {server}__{tool}, the same as in Tempr's other extensions.
Portal

Update of Portal, Sep 5, 2026

Added

  • Prompt templates: keep a system prompt in the Portal and update it without releasing new code. Every change is kept as a version, and you choose which one is live.
  • Sessions and End users: two new Gateway pages group your requests by the session id or end-user id your application sends, with a timeline for each. Organization owners and admins get the same views for their team.
  • Request cost: Gateway requests now record their cost. Sessions and End users show what each one cost, and Analytics breaks cost down by prompt template.
  • LLM guardrail: a Gateway account or key can have each request screened for prompt-injection and jailbreak attempts before it is sent. It uses one extra call to your own provider, at that provider's normal rate.
  • Guardrail activity: Gateway Analytics shows how many requests the guardrails blocked or flagged, and for what.
  • Model list in the Playground: the Playground now offers the models your provider keys can reach, instead of only a text box.
  • Product switcher: accounts with both Chat and the Gateway switch between them at the top of the sidebar.
  • Organization owners and admins now have an Organization section in the sidebar.

Fixed

  • The Gateway page's Resend verification button didn't work.

Security

  • A closed or deactivated account's Portal sessions now stop working right away.
  • Opening a sign-in, password reset or license key link now always starts from a signed-out page.
Gateway

Update of Gateway, Sep 3, 2026

Added

  • Prompt templates: keep a system prompt in the Portal, with versions, and name it on a request with the x-tempr-prompt header. Its {{variables}} are filled from the header, and it goes in front of the request as the first system message.
  • Prompt-injection check: an optional guardrail, per account or per key, that asks the request's model whether the prompt is an injection or jailbreak attempt before sending it on. In Block mode a match returns 400 guardrail_blocked.
  • Sessions and end users: send x-tempr-session-id to group a conversation's or agent run's requests into one session in the Portal, and the request's own end-user field (safety_identifier or user, or metadata.user_id on /v1/messages) to see usage per customer. Each request log now records its cost.
Gateway

Update of Gateway, Sep 1, 2026

Fixed

  • Requests that used a fallback chain, or rotated between several keys for a provider, could fail with a spurious 503.
Portal

Update of Portal, Sep 1, 2026

Fixed

  • With emailed two-factor codes turned on, entering the code sent you back to the sign-in page instead of signing you in.
  • After regenerating a license key, the new key wasn't shown on the page.
  • If starting a checkout or opening billing fails, you now get a message and can try again instead of an error page.

August 2026

Gateway

Update of Gateway, Aug 30, 2026

Added

  • Several keys per provider: add more than one key for a provider and Tempr spreads requests across them, skips a key that's cooling down, and moves to the next key when one fails. 502 all_keys_failed means every key was tried.
  • Sensitive-content guardrail: scan requests for emails, card numbers, JWTs, bearer tokens, AWS keys and other secrets before they reach a provider. Flag mode records what matched on the request log; Block mode returns 400 guardrail_blocked.
  • Redacted request logs: optionally mask the same kinds of sensitive content in captured request and response bodies before they're stored.
  • Cost anomaly alerts: a webhook fires when the last hour's spend is several times the account's usual hourly spend.
VS Code

1.0.7 of VS Code, Aug 30, 2026

Added

  • Vault MCP servers: MCP servers assigned to your account in Tempr's server-side vault now show up in the extension automatically, merged in with your local tempr.mcpServers entries (a vault entry wins on a name collision, and vault servers appear as read-only cards in the Tempr Settings MCP list).
  • Remote MCP servers: vault-assigned remote servers connect over MCP's Streamable HTTP transport through Tempr's own proxy relay instead of to the remote server directly, so the real remote URL and its credentials never leave the Tempr server.

Fixed

  • A vault-fetch failure or a slow/hanging remote MCP connect (now capped at 5 seconds) no longer delays or blocks local MCP servers from starting.
JetBrains

1.0.1 of JetBrains, Aug 30, 2026

Added

  • Vault MCP servers: MCP servers assigned to your account in Tempr's server-side vault now start alongside the ones you've configured yourself, and their tools are available to the agent. When a vault server and one of yours share a name, the vault's entry wins.
  • Remote MCP servers: vault-assigned remote servers connect over MCP's Streamable HTTP transport through Tempr's own relay instead of to the remote server directly, so the real remote URL and its credentials never leave the Tempr server.

Changed

  • The plugin is now called Tempr Chat on the JetBrains Marketplace and in the IDE's plugin list.

Fixed

  • A vault fetch that fails or hangs (now capped at five seconds) no longer delays or blocks your own MCP servers from starting.
  • Works with newer IDE versions, which deprecated or changed some of the platform APIs the plugin used, including the one that serves the chat panel into the IDE's built-in browser.
Visual Studio

2.2.22 of Visual Studio, Aug 30, 2026

Added

  • Vault MCP servers: MCP servers assigned to you in Tempr's server-side vault, your own or shared by your team, now show up in the extension automatically alongside the servers you set up yourself. Tools > Options > Tempr > MCP Servers lists them in a read-only Vault-managed servers table. You manage them in the Tempr Portal.
  • Remote MCP servers: remote servers from the vault connect through Tempr's own relay, not to the remote server directly, so the real remote URL and its credentials never leave the Tempr server. You need to be signed in to use them. A remote server that can't connect is skipped, and your other servers keep working.
Portal

Update of Portal, Aug 30, 2026

Added

  • Audit log: organization owners and admins can review who changed what in the organization, filter by action, and export it to CSV.
  • Gateway log controls: export request logs to CSV, turn on redaction of emails, tokens, API keys and card numbers in captured content, and shorten how long logs are kept.
  • Multiple keys per provider: Gateway provider keys can hold backup keys, used in turn and routed around a key that's rate-limited or revoked. Each key can be turned on or off.
  • Request guardrails: scan each Gateway request for emails, tokens, API keys and card numbers before it reaches a provider, and choose to flag or block it. Set it for the account and override it per key.
  • Cost anomaly webhook: get a webhook when Gateway spending jumps.
Gateway

Update of Gateway, Aug 26, 2026

Added

  • POST /v1/messages: Anthropic's Messages API, so Claude Code and tools built on Anthropic's SDK can point at Tempr and run on any model you have a key for, streaming included. Send the key as a bearer token or in x-api-key; errors come back in Anthropic's format. See the Claude Code guide.
  • Remote MCP proxy: POST /mcp/proxy/{serverSlug} relays MCP requests to a remote MCP server you've added in the Portal, with the virtual key's limits, logs and an optional MCP server allowlist.
  • Gateway for teams: an organization can hold one Gateway plan whose quota its keys share, with a monthly organization budget (402 organization_budget_exceeded, with x-tempr-org-budget-limit). Alert and digest emails go to the organization's owners and admins.
Portal

Update of Portal, Aug 26, 2026

Added

  • Team Gateway. Organizations can take a Gateway plan together: one pooled quota and one bill shared across every member's keys, with team-wide alerts and analytics.
  • Gateway alerts and webhooks: email alerts as you near your monthly quota or overage cap, a signed webhook when the error rate spikes, a daily digest email, and a Send test webhook button.
  • MCP credentials: store MCP server connection details and secrets in the Portal instead of in each machine's mcp.json, and pick servers from a catalog. Owners and admins can add team credentials shared with every member. See MCP.
  • Agent traces. A record of each finished agent run from your IDE: its steps, tool calls, tokens, cost and errors. Organization owners and admins can see their team's runs.
Gateway

Update of Gateway, Aug 25, 2026

Added

  • Webhooks and alerts: set a webhook URL to receive quota and budget alerts, signed with HMAC-SHA256 in x-tempr-webhook-signature. Optional error-rate alerts fire when a sustained share of recent requests fails, and a daily digest email summarizes usage.

Changed

  • Provider ids use hyphens: azure_openai, aws_bedrock, azure_ai_foundry, together_ai, fireworks_ai, xiaomi_mimo, meta_llama and aleph_alpha became azure-openai, aws-bedrock and so on. The old names are still accepted.
JetBrains

1.0.0 of JetBrains, Aug 25, 2026

Added

  • Initial Marketplace release: a bring-your-own-key AI coding assistant for the JetBrains IDE family, working with your own keys for 20+ model providers or a gateway like OpenRouter.
  • Agent mode: a tool-calling agent that reads and searches your project, edits files, and runs shell commands, pausing for your approval before anything that changes something (interactive, autopilot, or bypass approval modes).
  • "@" persona modes: run the conversation as a specialist persona (plan, debugger, test, profiler, modernize, security, review, docs, refactor, git), or define your own custom agents (Pro).
  • Inline completions: optional ghost-text suggestions as you type.
  • "Send to Tempr" quick-fix: send any diagnostic straight to chat with the surrounding code attached.
  • Chat history: saved locally and encrypted at rest, searchable, pinnable and renameable, with cross-machine sync.
  • Multiple chat tabs: run several conversations side by side, each with its own model, mode, and history.
  • Live usage and cost footer: token and cost totals for the active conversation, updated as you go.
  • MCP servers: browse and install from the built-in catalog, or configure your own; their tools become available to the agent alongside the built-in ones.
  • Attachments: attach the active editor document, pick or paste images, or use #file/#symbol and drag-and-drop to add specific files to a message.
  • In-chat settings for your license key, approval mode, response style, iteration limits, disabled tools, and more.
VS Code

1.0.6 of VS Code, Aug 24, 2026

Fixed

  • Chat scrollbar: the message list's scrollbar (and its clickable/hoverable area) now stops above the input bar instead of running down behind it.
  • Chat input box: after switching chat tabs, the input box's auto-resize height sometimes computed too tall while its layout was still settling; it now recalculates once the box's width has actually settled.
Gateway

Update of Gateway, Aug 23, 2026

Added

  • Azure AI Foundry: call models deployed in your Azure AI Foundry resource as azure-ai-foundry/….
  • Hugging Face: Hugging Face's inference router is available with your Hugging Face token.
  • Microsoft Entra ID for Azure OpenAI: authenticate Azure OpenAI with a service principal instead of an API key. If Tempr can't sign in with it, the request returns 402 provider_auth_failed with a message saying what to fix.
VS Code

1.0.5 of VS Code, Aug 23, 2026

Fixed

  • The tools/skills panel's "Select all" is now a single panel-level toggle that flips to "Deselect all" once every tool is enabled, replacing two redundant "Select all" links (one panel-level, one scoped to the "Built-in" section).
  • Settings key-value editors (custom headers, environment variables, etc.) now drop a removed row from view immediately when its Remove button is clicked, instead of leaving it on screen until it lost focus.
Visual Studio

2.2.12 of Visual Studio, Aug 23, 2026

Changed

  • In the tools picker, the button that switches every tool on or off now says Deselect all once every tool is on. Each group's button is now called Toggle all.

Fixed

  • On plans that include delegation to sub-agents, every Agent-mode and persona turn could fail with a "Tool names must be unique" error from the model provider. Those turns work again.
Portal

Update of Portal, Aug 23, 2026

Added

  • Gateway Playground: send a test message through your own Gateway setup to check that a provider key works.
  • Fallback chains: give a Gateway key named aliases that try a list of models in order, skipping providers that are rate-limited or not set up. Key settings can now be edited after the key is created.
  • Provider health: Gateway Analytics shows each provider's error rate and latency over the last 30 days.
  • AWS Bedrock: add an Amazon Bedrock API key and region; your available models are found automatically.
  • Azure AI Foundry and Hugging Face provider keys.
  • Entra ID for Azure: Azure OpenAI and Azure AI Foundry keys can use an Entra ID service principal instead of an API key.
  • The sign-up page now asks whether you're here for Tempr Chat or the Tempr Gateway.

Changed

  • The sidebar shows the Chat and Gateway sections only for the products you have.
  • Provider keys are sorted by provider name.

Fixed

  • Remember me on the sign-in page didn't keep you signed in.
Visual Studio

2.2.10 of Visual Studio, Aug 21, 2026

Changed

  • Tiered delegation concurrency. How many delegated sub-agents can run at the same time now depends on your plan: 2 on Standard and 8 on Pro. Before, every plan could run 8. When the agent asks for more at once, the extra sub-agents wait their turn.
Gateway

Update of Gateway, Aug 20, 2026

Added

  • AWS Bedrock: call Bedrock models with your Bedrock API key, including models served through Bedrock's Converse API. Your Bedrock and Azure OpenAI models now appear in GET /v1/models, and a Bedrock error comes back with Bedrock's own message instead of a generic one.
  • Fallback chains: give a key an alias with an ordered list of models; when one fails with repeated 429s or 5xx errors, Tempr moves to the next, before any bytes reach your client, streams included. A model that keeps failing sits out for a while. See fallback chains.
  • Response caching: add x-tempr-cache-ttl: <seconds> to serve an identical request from cache without calling the provider. x-tempr-cache says HIT or MISS.
VS Code

1.0.4 of VS Code, Aug 20, 2026

Changed

  • Tiered delegation concurrency. The cap on concurrently-running delegated sub-agents ("delegate_to_agent") is now tier-based (Standard: 2, Pro/Team: 8) instead of a flat 8, matching the JetBrains/Visual Studio entitlement limits. The cap is re-applied on every delegation, so a sign-in, sign-out, or plan upgrade mid-session takes effect immediately.
VS Code

1.0.3 of VS Code, Aug 19, 2026

Added

  • Server-side agent loop: agent tool-calling turns can now be driven by the Tempr server, with MCP tool catalogs resolved server-side. Tool results are delivered with automatic retries, so a transient network hiccup no longer leaves a chat frozen mid-turn.
  • Session-scoped tool trust: confirmation cards for shell commands offer "Trust <prefix> for this session" (e.g. npm run), and PowerShell script approvals can be remembered per tool. Session prefixes match on exact command tokens, so trusting npm run never accidentally trusts npm runbook.
  • The responding indicator now stays pinned under the streaming reply with a live elapsed-time and token-estimate ticker, instead of disappearing at the first token.

Fixed

  • Assorted chat-window rendering issues and markdown formatting fixes.
Visual Studio

2.2.8 of Visual Studio, Aug 19, 2026

Added

  • Server-side agent loop: agent turns can now run on the Tempr server, and from 2.2.10 so can Ask-mode turns. Tools still run in Visual Studio, with your approval where it's needed. Tool results are sent with automatic retries, so a brief network problem no longer leaves a chat stuck partway through a turn.
  • Browse MCP Servers: a new plug button in the chat toolbar opens a catalog of MCP servers you can install in one click. If a server needs environment variables, such as an API key, Tempr asks for them. A newly installed server starts on your next agent turn, with no restart needed. Before, a server you added didn't start until Visual Studio restarted.

Changed

  • Between a tool call and the model's next reply, the status line under the transcript now says "Working…" instead of disappearing, so a long turn no longer looks frozen.

Fixed

  • A scrollbar no longer flashes in and out each time you send a message.
Gateway

Update of Gateway, Aug 17, 2026

Added

  • Tempr Gateway. One OpenAI-compatible API at api.temprhq.io in front of your own provider keys: OpenAI, Anthropic, Google Gemini, Mistral, xAI, DeepSeek, OpenRouter, Together AI, Fireworks AI and more. POST /v1/chat/completions takes OpenAI's request shape for every model, and Anthropic, Gemini and Cohere are translated to it and back, streaming included. GET /v1/models lists the models your keys can reach. See the Gateway quickstart.
  • Virtual keys: tvk_ keys you create in the Portal, each with its own model allowlist, spend budget, and requests-per-minute and tokens-per-minute limits, so your provider keys never leave Tempr. See Authentication & virtual keys.
  • Plans and limits: Free, Pro and Scale plans with a monthly request allotment, a plan-level rate limit, and metered overage on Pro and Scale up to a cap you set. Limit errors carry headers saying where you stand, and alert emails go out as you approach the allotment. See pricing.
  • Request logs: every request is logged with its key, model, status, latency, tokens and cost, and x-tempr-metadata attaches your own fields to filter by. Each response carries x-tempr-request-id to match it to its log. Errors use OpenAI's error format; see the error reference.
Visual Studio

2.2.2 of Visual Studio, Aug 17, 2026

Added

  • Session tool trust: confirmation cards for commands now offer "Trust <prefix> for this session" (for example npm run), and PowerShell script approvals can be trusted for the whole session. Prefixes match whole words, so trusting npm run never trusts npm runbook. Destructive commands can never be trusted this way, and neither can anything in Bypass mode.
  • Confirmation cards for commands and PowerShell scripts now show the complete command or script, not just a one-line summary, and it stays visible after you decide.
  • While a reply streams, the status line stays below it with an elapsed-time counter and a running token estimate, instead of disappearing at the first word.

Changed

  • The toolbar's usage line no longer shows a lifetime token and cost total, and the Reset lifetime usage button is gone. Your lifetime usage is in the Tempr Portal. The monthly budget now counts the current calendar month and resets itself when the month changes.

Security

  • PowerShell commands that download and run code, or that send data out, now always ask for approval, in every approval mode and even when PowerShell scripts are trusted for the session.

Fixed

  • A command or script that started a background process could freeze the whole chat after it timed out. Timeouts now stop the command and everything it started, and the chat moves on.
  • The chat now scrolls along with a streaming reply. Before, it never did.
Portal

Update of Portal, Aug 17, 2026

Added

  • Tempr Gateway (preview). A Gateway section for the invite-only preview: an overview with your monthly quota and optional metered overage with a cap, Gateway keys with allowed models, monthly spend and rate limits, Gateway provider keys checked live when saved, usage by key and model, searchable request logs, and analytics. You can choose whether request and response content is stored with your logs.
  • Create an account without a license: sign up with an email and password, confirmed by a verification email.
VS Code

1.0.1 of VS Code, Aug 16, 2026

Added

  • Tempr Settings. A dedicated settings page inside the Tempr chat view (gear icon in the chat toolbar, or Tempr: Open Settings from the Command Palette). Every Tempr setting now lives here instead of VS Code's native Settings UI: approval mode, response style, models and sampling, budgets, agent limits, disabled tools, per-persona model overrides, custom agents, and MCP servers.
  • Built-in editors for structured settings: validated add/edit dialogs for custom agents (with preset icon colors and an allowed-tools checklist) and MCP servers (single command-line field with live preview, masked environment variables), plus chip editors for auto-approved command prefixes and per-persona model rows.
  • Settings are searchable, grouped into collapsible sections, and show at a glance which values differ from their defaults.
  • Entitlements in the UI: custom agents show a Pro upgrade path on Standard licenses, and agent-loop iteration limits are clearly capped to your license tier.
  • Editing MCP servers now applies without reloading the window; running servers restart on the next chat turn.

Changed

  • Settings are stored in Tempr's own extension storage instead of settings.json. Existing tempr.* values in settings.json keep applying automatically, with nothing to migrate by hand, and any value you change on the settings page takes over from then on.

Fixed

  • Agent-loop iteration limits are now capped to your license tier up front, instead of failing a turn mid-flight with a limit error.
  • Settings toggles now show clearly blue when enabled (previously gray in both states).
  • Unchanged settings no longer show a "modified" indicator when an empty default value is present in settings.json.
  • Custom-agent cloud sync follows server URL changes made mid-session.
VS Code

1.0.0 of VS Code, Aug 15, 2026

Added

  • Agent mode: a multi-step, tool-calling agent that reads/searches your workspace, edits files, and runs commands, pausing for your approval before anything mutating happens. Accept-all/undo controls for AI-made file edits.
  • Ask mode, plus persona-based sub-agents (plan, debugger, test, profiler, modernize, security, review, docs, refactor, git) for delegating specialized work, including custom personas you define yourself.
  • Workspace-aware semantic and symbol search, with code-intelligence-backed caller/callee lookup.
  • Inline ghost-text code completions.
  • File and image attachments, drag-and-drop, clipboard paste, and @workspace, @terminal, @problems context mentions.
  • "Send to Tempr" quick fix for sending a diagnostic straight to chat.
  • Model Context Protocol (MCP) server support for connecting custom tools.
  • Slash commands (/explain, /fix, /optimize, /refactor, /tests, /doc, /new, /clear, /help, /run).
  • Multi-tab chat history with search, pin, rename, and delete.
  • In-chat settings: license key management, approval mode, response style, model selection, font size, and a structured editor for MCP servers, custom agents, and per-persona model overrides.
  • Live token and cost usage tracking, with optional monthly budget alerts.
  • Chat sessions encrypted at rest on disk.

Fixed

  • Various startup, theming, and dropdown-loading issues from early builds.
Visual Studio

2.1.372 of Visual Studio, Aug 15, 2026

Changed

  • The Tools > Options > Tempr pages for allowed command prefixes, custom agents, MCP servers and per-persona models are now editable tables with Add and Remove buttons. They replace the pipe-delimited text boxes. A custom agent's system prompt opens in its own editor, and per-persona model overrides offer a dropdown of your models.
Visual Studio

2.1.366 of Visual Studio, Aug 13, 2026

Added

  • Chat history across machines: chats saved from another machine signed in to your license now download to this one. A fresh install starts with your history instead of an empty list.

Changed

  • Chat font size moved from the chat panel to Tools > Options > Tempr > General. It applies to open chats right away, and Ctrl+=, Ctrl+- and Ctrl+0 still adjust it in the chat window.
  • The chat toolbar's gear button now opens Tools > Options > Tempr. A new key button opens your license key and a link to manage it in the Tempr Portal.
  • The header above each chat has been removed. Its message count now appears at the start of the toolbar's usage line.

Fixed

  • Reopening a chat from history no longer leaves a large blank gap above the last message.
Portal

Update of Portal, Aug 11, 2026

Added

  • Team plan: an organization with shared seats. Owners and admins invite members by email as Member or Admin, change roles and remove members.
  • Org keys: shared provider keys for the whole organization, organization keys with allowed models, monthly budgets and rate limits, and per-member limits for everyday chat.
  • Org budget: a monthly organization budget as a soft email alert or a hard cap, with spend by day, by member and by model.
  • Personas & commands: publish your organization's own personas and slash commands to every member.
  • Single sign-on: members can sign in through your own identity provider, limited to your email domains, with optional automatic sign-up on first sign-in and an option to require SSO. See Teams and SSO.
Portal

Update of Portal, Aug 9, 2026

Added

  • Dashboard: this week's spend, requests and tokens by model, your most-used models, and notices about failed sign-ins or a reached budget.
  • Budget: month-to-date spend per license, a projection to month end, average cost per request, your top model, and a daily spend chart.
  • Billing: see your payment method, lifetime total, next invoice, and a notice with a link to fix it when a payment fails.
  • Close account: close your account from the Plan page after confirming your password.
  • Security alerts: an email when your account signs in from a new IP address and when your password changes. The Security page shows where each sign-in came from and counts failed attempts.
  • You can now set a username.
  • Usage has charts of spend, requests and tokens by model over the last 30 days.

Changed

  • Resetting your password now signs out every device using your license key, and emails you.
  • After changing your password, the Portal suggests reviewing your signed-in devices.
  • Too many failed sign-in attempts now pause sign-in for a few minutes.
Visual Studio

2.0.342 of Visual Studio, Aug 8, 2026

Changed

  • The Feature/Bug request button now opens the feature request page in the Tempr Portal instead of a form inside Visual Studio.

Fixed

  • The agent's run_tests tool always failed before it ran any tests. It now runs your tests and reports the results.
Visual Studio

2.0.338 of Visual Studio, Aug 7, 2026

Fixed

  • A chat's title now comes from the question you typed. Before, it could come from code attached to the message, such as a snippet sent with Send to Tempr.
Visual Studio

2.0.330 of Visual Studio, Aug 6, 2026

Initial release.

Added

  • Bring your own keys: chat with models from 20+ first-party providers, such as OpenAI, Anthropic, Google Gemini, xAI, Mistral and DeepSeek, or through OpenRouter, using your own API keys. You pick the model from a dropdown in the chat panel.
  • Agent mode: a multi-step, tool-calling agent that reads, searches and edits files in your solution and runs commands. It has three approval modes: Interactive asks before every change, Bypass applies edits for you to review afterwards, and Autopilot works hands-off. Commands are checked against an allow list you control in Tools > Options, and destructive commands always ask first.
  • Review changes: every file the agent edits shows up in a changes panel with a diff per file, plus Accept All and Undo All.
  • Debugger, test and solution awareness: the agent can read the live debugger state and evaluate expressions, run your tests with structured pass/fail results, and use compiler diagnostics, project references and callers and callees.
  • Ask mode: a plain chat that adds your active file, a solution overview and your package dependencies as context.
  • Personas and delegation: @plan, @debugger, @test, @profiler, @modernize, @security, @review, @docs, @refactor and @git switch to a specialist prompt and set of tools. The agent can also hand focused sub-tasks to these personas mid-turn. You can define your own custom agents and pick a model for each persona.
  • Semantic code search: your solution is indexed automatically for embedding-based search, so the agent finds related code even when the words don't match.
  • Precise context: #file and #symbol attach exactly the code you mean. @workspace, @terminal and @problems add a solution overview, terminal output or the Error List. You can attach or paste images too.
  • Inline completions: ghost-text suggestions as you type. Press Tab to accept.
  • Send to Tempr: the light bulb on an error or warning sends it to the chat with the surrounding code.
  • Slash commands: /explain, /fix, /tests, /doc, /refactor, /optimize, /run, /new, /clear and /help.
  • MCP servers: connect your own Model Context Protocol servers (stdio) to give the agent more tools.
  • Chat tabs and history: several chats side by side, each with its own model and mode. Your history is saved automatically and encrypted on disk, and you can search, pin, rename and delete chats.
  • Usage and budget: token and cost figures for each chat, plus an optional monthly budget alert.
  • Cloud sync: when you're signed in, your chats, settings and custom agents follow you to your other machines.
  • Open the chat from View > Tempr or with Ctrl+\\, Ctrl+O.
Portal

Update of Portal, Aug 4, 2026

Added

  • Subscribe from the Portal: choose Standard or Pro and check out, with a 7-day free trial. Your license key and Portal account are set up for you, and Manage subscription handles your billing afterwards.
  • Get started: a checklist that walks you through installing the extension, signing in with your license key and adding a provider key.
  • License keys: reveal a license key after confirming your password, or regenerate it, which signs out every device using the old one.
  • Budget alerts: set a monthly spend alert per license and get an email once when it's reached. It never limits your access.
  • Resend license key: lost your key? Enter your email and we'll resend every license key on the account.

Changed

  • Revealing a saved provider key now asks for your password.
  • Turning emailed two-factor codes on or off now asks for your password.
  • The Portal's address now opens the sign-in page directly.

July 2026

Portal

Update of Portal, Jul 31, 2026

Added

  • The Tempr Portal launches. One place to manage your Tempr account: sign in with your email and password (with optional emailed two-factor codes) and reset a forgotten password, see your licenses and signed-in devices and sign devices out, add provider keys for the models you use, compare plans, see your invoices, track lifetime usage and a daily breakdown by provider and model, review recent sign-in activity, change your password, and send feature requests.