apiPulse.app
This is a live demo. Register to save subscriptions and get email notifications.

Historical changes

1169 entries from demo-selected APIs

Add API
05-06-2026
Claude

2.1.132

Added CLAUDE_CODE_SESSION_ID environment variable to the Bash tool subprocess environment, matching the session_id passed to hooks Added CLAUDE_CODE_DISABLE_ALTERNATE_SCREEN=1 env var to opt out of the fullscreen alternate-screen renderer and keep the conversation in the terminal's native scrollback Added a "Pasting…" footer hint while a Ctrl+V image paste is being read from the clipboard Fixed external SIGINT (e.g. IDE stop button, kill -INT) not running graceful shutdown — terminal modes are now restored and the --resume hint is printed instead of an abrupt exit Fixed an uncaught exception when the terminal is closed or SSH disconnects mid-session under the native build Fixed --resume failing with no low surrogate in string when a tool error truncation split an emoji; pre-corrupted sessions are sanitized on load Fixed --permission-mode flag being ignored when resuming a plan-mode session with -p --continue/--resume, and plan mode not being re-applied after ExitPlanMode within the same session Fixed fullscreen mode showing a blank screen after laptop sleep/wake or Ctrl+Z/fg until the next keystroke or stream output Fixed cursor landing mid-grapheme on Ctrl+E/A/K/U/arrow keys when an Indic conjunct or ZWJ emoji wraps across lines Fixed vim operators corrupting text containing decomposed (NFD) accented characters Fixed pasting text starting with / silently swallowing the input or triggering an unknown-command reply Fixed pasting dumping stray escape sequences into the prompt when focus events or mouse-tracking reports interleave with the bracketed paste Fixed mouse wheel scrolling being too fast in Cursor and VS Code 1.92–1.104 due to an upstream xterm.js bug Fixed scroll-wheel handling in JetBrains IDE 2025.2 terminals (spurious arrow keys, wrong-direction events, runaway acceleration) Fixed /usage Ctrl+S hanging when copying the stats screenshot to the clipboard on Linux/X11 Fixed /terminal-setup showing a contradictory error in Windows Terminal — Shift+Enter is natively supported there Fixed /effort picker not reflecting the CLAUDE_CODE_EFFORT_LEVEL env var override Fixed /status showing the wrong default model for some users Fixed slash command autocomplete popup being capped at ~3–5 visible commands instead of scaling with terminal height Fixed statusline context_window token counts reflecting cumulative session totals instead of current context usage Fixed Alt+T (thinking toggle) not working on macOS terminals without "Option as Meta" enabled (iTerm2, Terminal.app defaults) Fixed dead keyboard input on Windows after re-opening a background session from claude agents Fixed unbounded memory growth (10GB+ RSS) when a stdio MCP server writes non-protocol data to stdout Fixed MCP servers that connect but fail tools/list silently showing 0 tools — they now retry once and show "connected · tools fetch failed" in /mcp Fixed unauthorized claude.ai MCP connectors showing as "failed" instead of "needs auth", and headless -p mode retrying non-transient 4xx connection failures Improved visual consistency in slash command dialogs and /login, /upgrade, /extra-usage dialog spacing Updated the /tui fullscreen startup banner to describe additional renderer benefits (lower memory usage, mouse support, auto-copy on select) Fixed Bedrock and Vertex 400 errors when ENABLE_PROMPT_CACHING_1H is set

Source
05-06-2026
Amazon SP-API

Update: May updates to listing attribute usage and enumeration values

Effective May 25, 2026 , Amazon will update the attribute usage and enumeration values of numerous product types across marketplaces. These adjustments eliminate redundant attributes and improve the curation of attributes and enumeration values that apply to the corresponding product types. For a co...

Source
05-06-2026
Claude

2.1.131

Fixed VS Code extension failing to activate on Windows due to a hardcoded build path in the bundled SDK (createRequire polyfill bug) Fixed Mantle endpoint authentication failing with missing x-api-key header

Source
05-06-2026
Atlassian

[Removed] Node.js 20 runtime is no longer supported for Forge apps

What’s changing? The nodejs20.x runtime for Forge apps has reached the end of its deprecation period and is no longer supported.Starting May 6, 2026, Atlassian will progressively block the ability to deploy or update apps using the nodejs20.x runtime. Existing deployments will continue to function, but they are provided "as-is" without support or warranties. Over time, apps using unsupported runtimes may become non-functional or vulnerable to security issues.What you need to doYou must update your app's to a supported Node.js runtime (nodejs22.x or higher) to continue deploying updates.Edit your app’s manifest.yml fileUpdate the app.runtime.name property to nodejs22.x or nodejs24.xUpdate your local development environment to a supported Node runtimeUpdate your Forge CLI to the latest versionRun npm install to update your dependenciesTest your app for compatibility with any breaking changes in the Node runtimeDeploy your app to production using forge deploy -e production For detailed instructions, see the Node.js runtime documentation.

Source
05-06-2026
Claude

2.1.129

Added --plugin-url flag to fetch a plugin .zip archive from a URL for the current session Added CLAUDE_CODE_FORCE_SYNC_OUTPUT=1 env var to force-enable synchronized output on terminals that auto-detection misses (e.g. Emacs eat) Added CLAUDE_CODE_PACKAGE_MANAGER_AUTO_UPDATE: when set on Homebrew or WinGet installations, Claude Code runs the upgrade command in the background and prompts to restart Plugin manifests: themes and monitors should now be declared under "experimental": { ... }. Top-level declarations still work but claude plugin validate will warn Gateway /v1/models discovery for the /model picker is now opt-in via CLAUDE_CODE_ENABLE_GATEWAY_MODEL_DISCOVERY=1 (was automatic in 2.1.126–2.1.128) Ctrl+R history picker now defaults to searching all prompts across all projects, matching pre-2.1.124 behavior. Press Ctrl+S to narrow to the current project or session Third-party deployments (Bedrock, Vertex, Foundry, or ANTHROPIC_BASE_URL gateway) no longer see spinner tips pointing at first-party Anthropic surfaces skillOverrides setting now works: off hides from model and /, user-invocable-only hides from model only, name-only collapses description The claude_code.pull_request.count OTel metric now counts PRs/MRs created via MCP tools, not just shell commands Policy refusal error messages now include the API Request ID for easier support debugging Fixed API errors with unrecognized 400 status codes showing raw JSON instead of the underlying error message Fixed /clear not resetting the terminal tab title after a conversation Fixed session title chip from /rename disappearing while a permission or other dialog is active Fixed agent panel below the prompt being hidden when subagents are running (regression in 2.1.122) Fixed external-editor handoff (Ctrl+G) blanking the conversation history above the prompt Fixed /context dumping its rendered ASCII visualization grid into the conversation, wasting ~1.6k tokens per call Fixed /agents Library list arrow-key navigation: the highlighted agent now stays visible when the list exceeds the viewport Fixed /branch success message not including the new branch's session id for /resume Fixed bold headers with keycap/ZWJ/skin-tone emoji losing trailing characters in fullscreen mode Fixed server-managed settings policy not applying for enterprise/team users whose stored OAuth credentials lacked the user:inference scope Fixed OAuth refresh race after wake-from-sleep that could log out all running sessions Fixed 1-hour prompt cache TTL being silently downgraded to 5 minutes Fixed cache-miss warning appearing spuriously after /clear or compaction when changing /effort or /model Fixed Bash(mkdir *), Bash(touch *) and similar allow rules not being honored for in-project paths Fixed deniedMcpServers patterns with a *:// scheme wildcard not matching mixed-case hostnames Fixed harmless WebSocket warning being logged as an error in --debug during voice mode [VSCode] Fixed /clear not clearing the conversation context and displayed transcript

Source
05-06-2026
Cloudflare

Cloudflare One - IPv6 CIDR routes for Cloudflare Mesh

Cloudflare Mesh nodes now support IPv6 CIDR routes. You can advertise both IPv4 and IPv6 subnets through your Mesh nodes, making IPv6-only or dual-stack private networks reachable from any enrolled device. To add an IPv6 route, follow the same steps as adding an IPv4 route — enter the IPv6 CIDR (for example, fd00::/64) when configuring the route in the dashboard or via the API.

Source
05-06-2026
Cloudflare

Radar - TLD Nameserver Performance in Cloudflare Radar

Radar now provides TLD authoritative nameserver performance insights, measuring response time (latency) as observed from Cloudflare's 1.1.1.1 resolver infrastructure when forwarding queries upstream to TLD nameservers. New widgets on TLD detail pages: Aggregate nameserver latency: Response time percentiles (p25/p50/p75) for all authoritative nameservers of the selected TLD. Latency per nameserver: Median response time (p50) broken down by each authoritative nameserver over time. Median latency geographic distribution: p50 response time by Cloudflare data center country, displayed on a choropleth map. TLD ranking over time: Daily DNS magnitude rank and magnitude value with a Rank/Magnitude toggle. Rank change deltas: 1 week, 4 weeks, and 3 months rank changes added to the TLD magnitude table and the TLD detail info panel. The new TLD Performance API provides the following endpoints: /tlds/performance/summary/{dimension} — TLD nameserver performance summarized by dimension. /tlds/performance/timeseries_groups/{dimension} — TLD nameserver performance over time grouped by dimension. Available dimensions: LATENCY (aggregate p25/p50/p75), NAMESERVER_LATENCY (per-nameserver p50), LOCATION_LATENCY (per-data-center-country p50). TLD Performance is also available as a dataset in the Data Explorer. Check out the updated TLD detail page.

Source
05-06-2026
Cloudflare

Security Center - TAXII support added to Threat Events API

The Cloudforce One Threat Events API now supports TAXII as an output format, enabling standardized, automated sharing of cyber threat intelligence with your existing security stack. Why this matters You can now ingest Cloudforce One threat data directly into your SIEM, TIP or SOAR tools that prefer TAXII-formatted streams without needing custom translation scripts. By supporting the TAXII format parameter in our API, security teams can automate the synchronization of indicator data, reducing the manual overhead of updating blocklists and detection rules. This alignment with industry standards ensures that your threat data remains consistent across different security ecosystems and partner integrations. How to use it When calling the Threat Events API, you can now specify taxii in the format query parameter: GET /accounts/{account_id}/cloudforce_one/threat_events?format=taxii You can find the updated documentation in the Cloudflare API Reference.

Source
05-05-2026
Atlassian

[Added] Bitbucket Connect → Forge migration tooling: new addon clientKey endpoint

What’s changing We’ve introduced a new Bitbucket REST API endpoint that allows a Forge app to retrieve the clientKey of its linked Connect app installation.This endpoint supports the migration process from Connect to Forge. By retrieving the clientKey, the installed Forge app can identify the equivalent Connect app installation, enabling you to perform data migration or cleanup tasks effectively.What you need to do To use this endpoint, ensure you have configured the linkage between your Connect and Forge apps.Add the forgeAppId key to your Connect app descriptor.Use the new endpoint to fetch the clientKey during your app's migration logic.

Source
05-05-2026
Atlassian

[Deprecation Notice] Deprecating Jira Issue Glance Forge Module

We are announcing the deprecation of  https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-issue-glance/  (jira:issueGlance), as we have replaced with  https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-issue-context/  (jira:issueContext) module. The Jira Issue Glance module will soon be removed from the work items completely. Please refer to the following documentation for more details -  https://developer.atlassian.com/cloud/jira/platform/future-proof-issue-glance-implementation/ 

Source
On demo you can only see one page. Register for full history and email notifications.