# ide A software application that supports multiple aspects of software development, including editing, debugging, and building projects. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Rune переходит на открытый исходный код и планирует делиться доходом с контрибьюторами DevFeed: [Rune переходит на открытый исходный код и планирует делиться доходом с контрибьюторами]() Original publisher: [Read original article]() Author: kseniiapashkoff (Selectel) Published: 2026-09-18T09:00:39Z Content type: news Language: ru Sources: [Tagir Valeev]() Topics: [ide](), [Open Source](), [GNU General Public License](), [Command-line interface](), [Linux](), [macOS](), [P2P](), [Go Language](), [OpenGL](), [GPU]() Tags: [alacritty](), [build](), [c](), [cli](), [github](), [go](), [gplv3](), [gpu](), [ide](), [linux](), [macos](), [network](), [open](), [open-source](), [opengl](), [peer-to-peer](), [rune](), [rust](), [selectel](), [tag-3d31226d5cbe](), [tag-8d66d519a360](), [unstable-build](), [zig]() ### AI overview Unstable Build has released the source code of its Rune IDE under the GPL-3.0-or-later license. Rune is a native Linux and macOS application that combines terminal sessions, code editing and debugging, CLI tools, package installation, and AI-agent commands. The article also describes its Go-based engine, GPU-accelerated rendering, peer-to-peer workspace access, and open-source development history. ### Source excerpt Компания Unstable Build выложила в открытый доступ исходный код своей IDE Rune под свободной лицензией GPL-3.0-or-later. Разберемся, почему в мире, где разработчики ПО все чаще переходят на проприетарные лицензии, это событие стало важным прецедентом для IT-индустрии. Читать далее ## Libreboot Build System Audit 5 DevFeed: [Libreboot Build System Audit 5]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: article Language: en Sources: [News about Libreboot releases and development]() Topics: [audit](), [opensource](), [boot](), [POSIX](), [ide](), [systems]() Tags: [audit](), [bios](), [bugs](), [canoeboot](), [clean-code](), [coreboot](), [efficiency](), [firmware](), [free-software](), [libre](), [libreboot](), [linux](), [opensource](), [operating-systems](), [posix](), [uefi]() ### AI overview This article describes the fifth audit of Libreboot's lbmk build system, covering changes made since the Libreboot 20240504 release. It reports a reduction in shell-script size, bug fixes, feature changes, and improvements aimed at cleaner and more efficient code. ### Source excerpt Article: Libreboot Build System Audit 5 Web link: https://libreboot.org/news/audit5.html ## Behind the Scenes: How the OpenTelemetry Plugin Maps Your Microservices in Real-Time DevFeed: [Behind the Scenes: How the OpenTelemetry Plugin Maps Your Microservices in Real-Time]() Original publisher: [Read original article]() Author: Egor Klimov Published: 2026-09-16T12:34:47Z Content type: article Language: en Sources: [The JetBrains Blog]() Topics: [OpenTelemetry](), [Microservices](), [observability](), [telemetry](), [Traces](), [ide]() Tags: [all-things-web](), [backstage](), [environment-variables](), [goland](), [ide](), [idea](), [intellij-idea](), [intellij-platform](), [jetbrains](), [microservices](), [observability](), [opentelemetry](), [performance-optimization](), [plugin-development](), [plugin-highlights](), [plugins](), [pycharm](), [research](), [rider](), [telemetry](), [traces](), [webstorm]() ### AI overview This article explains how the JetBrains OpenTelemetry Plugin generates a service map from runtime telemetry. It describes using logs, metrics, and especially standardized trace spans to visualize how microservices communicate, along with the plugin's lightweight local OpenTelemetry backend. ### Source excerpt We've all been there: you join a new project, and the first thing you ask for is the architecture diagram. You're handed a diagram that looks great, but after a week of debugging, you realize it's six months out of date. Service A hasn't talked to Service B since the spring, and there's a new [...] ## Toolbox App 3.8: Improves IDE Update Handling on macOS and Fixes Keyboard Navigation DevFeed: [Toolbox App 3.8: Improves IDE Update Handling on macOS and Fixes Keyboard Navigation]() Original publisher: [Read original article]() Author: Ivan Kuzmin Published: 2026-09-14T16:05:56Z Content type: release Language: en Sources: [The JetBrains Blog]() Topics: [App](), [ide](), [macOS]() Tags: [cleanup](), [ide](), [jetbrains-toolbox](), [macos](), [navigation](), [shortcuts](), [toolbox-app](), [update]() ### AI overview Toolbox App 3.8 improves IDE update handling on macOS, restores keyboard navigation in project and tool lists, and adds progress reporting and safeguards for cleanup of leftover IDE directories. ### Source excerpt Version 3.8 of the Toolbox App restores keyboard navigation in project and tool lists. On macOS, manual IDE updates stay available even when the system reports the installation directory as protected. IDE updates remain available on macOS macOS was sometimes incorrectly reporting an IDE installation directory as non-writable, causing the Toolbox App to needlessly disable [...] ## How to build an AI content generator for Webflow DevFeed: [How to build an AI content generator for Webflow]() Original publisher: [Read original article]() Author: Ismail Ajagbe Published: 2026-09-12T00:00:00Z Content type: tutorial Language: en Sources: [Webflow Blog]() Topics: [Artificial Intelligence](), [Content Management System](), [API](), [ide](), [App]() Tags: [ai](), [ai-content](), [api](), [authentication](), [code](), [guide](), [guides](), [how-to](), [next-js](), [openai](), [webflow]() ### AI overview Guide to building an AI content generator that uses OpenAI to create content and a Webflow Cloud App Route Handler to save drafts to Webflow CMS through the Data API. ### Source excerpt Learn how to build an AI content generator that writes Webflow CMS drafts via a Cloud App Route Handler. ## Get Gemini 3.8 Flash With 75% Off DevFeed: [Get Gemini 3.8 Flash With 75% Off]() Original publisher: [Read original article]() Author: Dmitry Savelev Published: 2026-09-09T14:18:17Z Content type: release Language: en Sources: [The JetBrains Blog]() Topics: [coding](), [Google](), [releases](), [Command-line interface](), [ide]() Tags: [agentic-ai](), [agents](), [benchmark](), [cli](), [coding](), [flash](), [gemini](), [google](), [ide](), [jetbrains-ai](), [junie](), [launch](), [model](), [promotion](), [sales](), [testing]() ### AI overview Gemini 3.8 Flash is now available in Junie's IDE plugin and CLI at a limited-time 75% discount. The article presents it as a coding model for multi-step engineering tasks that explores, tests, and verifies changes before finishing. ### Source excerpt Google's newest coding model, Gemini 3.8 Flash, is tuned for long jobs and comes with an incredible launch discount. Google shipped three Flash releases in six weeks, and the newest one is built for exactly the kind of work Junie does all day: multi-step engineering tasks that take real exploration to get right. Gemini 3.8 [...] ## Use a local and open source code assistant DevFeed: [Use a local and open source code assistant]() Original publisher: [Read original article]() Author: Seth Kenlon Published: 2026-09-09T14:01:45Z Content type: tutorial Language: en Sources: [Red Hat](), [Red Hat Developer]() Topics: [ai-coding](), [Local AI](), [Open Source Models & Datasets](), [Large Language Model](), [Model Context Protocol](), [ide](), [Security, Privacy and Abuse Prevention](), [Command-line interface](), [Homebrew](), [Linux](), [macOS]() Tags: [ai-coding](), [ai-inference](), [artificial-intelligence](), [command-line](), [developer-tools](), [ide](), [linux](), [llm](), [local-ai](), [macos](), [model-context-protocol](), [ollama](), [open-source](), [privacy]() ### AI overview This Red Hat Developer article explains how to use OpenCode as a local, open source AI coding assistant. It covers OpenCode's terminal, desktop, and IDE extension interfaces, its use of the Model Context Protocol, installation requirements, and the need to configure an LLM. For privacy-conscious local development, it recommends open source local AI tools such as Ollama or OpenVINO. ### Source excerpt There's a lot of excitement about AI coding assistants, but many of the available options either aren't open source, or don't respect your data privacy by sending what you're working on to the cloud for processing. If you're looking for an alternative to closed AI, then you need an open coding assistant and an open source IDE. The post Use a local and open source code assistant appeared first on Red Hat Developer. ## Debug Past an HTTP 403 Without Breaking Spring Security DevFeed: [Debug Past an HTTP 403 Without Breaking Spring Security]() Original publisher: [Read original article]() Author: Andrey Belyaev Published: 2026-09-08T12:34:18Z Content type: tutorial Language: en Sources: [The JetBrains Blog]() Topics: [debug](), [Authorization](), [IntelliJ IDEA](), [ide]() Tags: [debug](), [features](), [http](), [intellij-idea](), [security](), [spring](), [spring-debugger](), [tutorials]() ### AI overview The article explains how IntelliJ IDEA security inlays help debug Spring endpoints blocked by HTTP 403, 401, or login redirects. It covers inspecting runtime role requirements and temporarily unlocking an endpoint for a debug session, with a warning that unlocking affects all clients reaching that URI and method. ### Source excerpt You set a breakpoint inside a Spring MVC controller, or a service, send the request to an HTTP endpoint, and nothing happens. The response is back - and it is a 403 (or 401, or a redirect to a login page). At that point, the bug you were trying to catch is no longer the [...] ## TypeScript 7 in WebStorm: Faster Coding Assistance for Angular and React, No Migration Required DevFeed: [TypeScript 7 in WebStorm: Faster Coding Assistance for Angular and React, No Migration Required]() Original publisher: [Read original article]() Author: Piotr Tomiak Published: 2026-09-08T10:54:49Z Content type: release Language: en Sources: [The JetBrains Blog]() Topics: [ide](), [coding](), [Go Language](), [Node.js]() Tags: [2026-2](), [angular](), [go](), [node-js](), [performance](), [react](), [typescript](), [vue](), [webstorm]() ### AI overview WebStorm 2026.2 adds stable TypeScript 7 support for Angular and React projects without requiring project migration. Its native integration with TypeScript 7's Go-based engine aims to improve coding-assistance performance, especially in large codebases. ### Source excerpt TypeScript 7 is a real game-changer, and its new Go-based language engine fundamentally alters how IDEs integrate with TypeScript. And what's more, WebStorm 2026.2 ships stable support for it, including for Angular and React projects. No migration is required - if your team is locked on an older TypeScript version for infrastructure reasons, your project [...] ## Rust debugging survey 2026 results DevFeed: [Rust debugging survey 2026 results]() Original publisher: [Read original article]() Author: Sam Kellam Published: 2026-09-07T00:00:00Z Content type: article Language: en Sources: [Rust Blog]() Topics: [debugging](), [Rust](), [ide](), [Command-line interface]() Tags: [2026](), [command-line](), [debugger](), [debugging](), [developers](), [ide](), [rust](), [survey]() ### AI overview The Rust project reports results from its first Rust Debugging Survey, which received more than 2,300 responses. The article examines who uses debuggers, how Rust developers debug programs, and the debugging challenges they encounter. More than 46% of respondents currently use debuggers, while print debugging and the macro are widely used, followed by debugging inside an IDE and on the command line. ### Source excerpt One of the biggest challenges Rust developers report in our annual surveys is a subpar debugging experience. So, back in February, we ran our first Rust Debugging Survey, in the hopes of identifying how Rust developers are using debuggers and what problems they are facing when doing so. We received over 2,300 responses, and we'd like to thank everyone who took the time to participate in the survey! In this report, we'll go over some of the results of the survey. If you'd like, you can also check out the complete results of the survey. If you'd like to skip ahead to any particular section, you can do so with this index: Who Uses Debuggers? How Are Debuggers Used? Challenges Debugger Visualizers Closing Remarks Who Uses Debuggers? The first step to making sense of the survey results is understanding who took the survey. We asked respondents to rate their Rust expertise, from "Never used it" to "Advanced". Over 80% reported themselves as "Advanced" or "Intermediate", split roughly evenly between the two: [PNG] [SVG] We also asked respondents if they currently use or have used debuggers in Rust. Over 46% said they currently do, with the remaining responses split between "have in the past" and "never have". That means that over half of respondents do not currently use a debugger for Rust! [PNG] [SVG] Categorized by expertise, the responses reveal that roughly half of "beginners" have never used debuggers in Rust! On the other hand, nearly half of "advanced users" currently do use debuggers in Rust: [PNG] [SVG] For respondents who indicated they had previously used Rust but no longer did, we asked if challenges with debugging support were why they stopped. For nearly 3%, the answer was "yes", with an additional 24% reporting debugging issues as being partially responsible (though mind the small response count; most respondents were active users of Rust): [PNG] [SVG] How Are Debuggers Used? Knowing what debuggers developers are using and how is another important part of un ## Playco cut manual fixes 50% prototyping games with GPT-6 Astra DevFeed: [Playco cut manual fixes 50% prototyping games with GPT-6 Astra]() Original publisher: [Read original article]() Published: 2026-09-03T12:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [Game engine](), [ide](), [Code]() Tags: [ai](), [ai-models](), [bugs](), [game-development](), [gpt](), [ide](), [performance](), [prototypes](), [prototyping](), [reasoning](), [startup](), [ui](), [vision]() ### AI overview Playco reports that GPT-6 Astra helped it create three themed game prototypes from a shared grey-box foundation, with 50% fewer manual fixes than its previous model. The company uses the model in Playbot, an AI-powered IDE connected to game engines for editing, testing, validation, and bug finding. ### Source excerpt Using GPT-6 Astra, Playco built three themed game prototypes from one grey box foundation and reported 50% fewer manual fixes than with the previous model. ## Stop alt-tabbing into the wrong Visual Studio DevFeed: [Stop alt-tabbing into the wrong Visual Studio]() Original publisher: [Read original article]() Author: Mads Kristensen Published: 2026-09-02T14:00:12Z Content type: tutorial Language: en Sources: [Visual Studio Blog]() Topics: [Visual Studio 2026](), [ide]() Tags: [accessibility](), [customization](), [how-to](), [json](), [themes](), [visual-studio](), [visual-studio-2026]() ### AI overview The article explains how to set a color theme per Visual Studio solution through the new settings experience. Per-solution settings are stored in settings.VisualStudio.json and can be committed with the solution. ### Source excerpt A user asked for per-solution color themes. It already ships, and it goes further than they asked. You run several instances of Visual Studio side by side, one per solution, and they all look identical. Same taskbar icon, same alt-tab thumbnail, same chrome. So, you land in the wrong one, start typing, and realize thirty [...] The post Stop alt-tabbing into the wrong Visual Studio appeared first on Visual Studio Blog. ## PyCharm & Django Fall Fundraiser DevFeed: [PyCharm & Django Fall Fundraiser]() Original publisher: [Read original article]() Author: Jeff Triplett Published: 2026-08-25T19:45:00Z Content type: news Language: en Sources: [The Django weblog]() Topics: [Django](), [PyCharm](), [ide](), [Python]() Tags: [collaboration](), [community](), [developers](), [django](), [events](), [framework](), [growth](), [onboarding](), [open-source](), [partnership](), [pycharm](), [python](), [support]() ### AI overview Django and JetBrains are running a fall fundraiser in which new or renewed PyCharm licenses are offered at a 30% discount, with JetBrains matching the contribution to the Django Software Foundation. The campaign supports Django maintenance, community programs, events, contributor onboarding, and the Foundation's planned Executive Director role. ### Source excerpt We are back with our friends at JetBrains for the second of the two "Buy PyCharm, Support Django" fundraisers we run together each year. Our spring campaign was the first. It remains one of the most impactful ways the community can support the Django Software Foundation. Your support of this campaign helps fund key initiatives such as: A Django Executive Director: Funding our first Executive Director, who will lead fundraising, operations, and community coordination for the Foundation. Django Fellows: Ensuring the rapid development and maintenance of Django. Django Girls: Making the Django community accessible to programming beginners around the world. International events and conferences: Supporting DjangoCons, one-day events, meetups, and other community gatherings around the world. Djangonaut Space: Onboarding new contributors to the Django project. The Executive Director role is new, which is why this campaign matters more than usual. The DSF raises around $300,000 a year today. Reaching $500,000 is what makes a full-time Executive Director sustainable, and campaigns like this one are how we close that gap. If leading that work sounds like you, applications are open until September 14, 2026. How the campaign works The campaign runs until September 10, 2026. When you buy a new PyCharm license or renew an existing one at a 30% discount through our special campaign link, JetBrains will donate an equal amount to the Django Software Foundation. You get a professional IDE that is trusted by Django developers worldwide, and the DSF receives a matched contribution. Get 30% off PyCharm, Support Django Thank you, JetBrains Beyond this campaign, JetBrains contributes to the Django ecosystem in ways that are easy to overlook but hard to overstate. The 2026 Django Developers Survey was published earlier this summer, and along with the Python Developers Survey, it gives the entire community a clearer picture of where Django and Python are heading each year. "JetBrains is one ## LibreDB Studio: an open source, self-hosted SQL IDE for PostgreSQL in the browser DevFeed: [LibreDB Studio: an open source, self-hosted SQL IDE for PostgreSQL in the browser]() Original publisher: [Read original article]() Published: 2026-08-20T00:00:00Z Content type: article Language: en Sources: [PostgreSQL news]() Topics: [PostgreSQL](), [ide](), [SQL](), [browser](), [Open Source](), [API](), [Authentication](), [OpenID connect (OIDC)](), [Authorization](), [Back end]() Tags: [api](), [authentication](), [backend](), [browser](), [ide](), [monitoring](), [open-source](), [postgresql](), [release](), [self-hosted](), [sql]() ### AI overview LibreDB Studio is an MIT-licensed, self-hosted SQL IDE for PostgreSQL that runs in the browser and can be deployed as a container, Helm chart, or npm package. The article describes its database-aware query editing, transaction controls, schema introspection, monitoring, optional query assistant, and local-account or OIDC authentication with role-based access control. Release 0.12.0 is highlighted. ### Source excerpt LibreDB Studio is an MIT-licensed, self-hosted SQL IDE for PostgreSQL that runs in the browser and deploys as a container or Helm chart. It is deployed next to the database it manages, as a container, a Helm chart or an npm package, rather than installed on each developer's machine. PostgreSQL is its reference implementation: the provider is built on node-postgres, and the other supported engines follow the patterns established there. On a PostgreSQL connection the editor uses pooled connections, explicit BEGIN/COMMIT/ROLLBACK transactions with an auto-rollback timeout, and query cancellation through pg_cancel_backend on the tracked backend PID. Schema introspection is written to stay responsive on databases with hundreds of tables: the table tree renders from a first pass while relationships stream in from a second. Monitoring reads the pg_stat_* views, including pg_stat_statements where the extension is installed, and degrades to what the connected role can actually see instead of failing when superuser-only views are unavailable. The optional query assistant is constrained by the database rather than by prompt text. A run is given the real schema of the connected database before its first turn, so a drafted statement names objects that exist, and read-only runs execute inside BEGIN READ ONLY as a single statement over the extended protocol. Authentication is local accounts or OIDC, with role-based access control in front of every API route. The current release is 0.12.0. Source, documentation and the PostgreSQL provider reference are at github.com/libredb/libredb-studio and libredb.org. ## How Omit Can Collapse TypeScript Union Types into an Empty Object DevFeed: [How Omit Can Collapse TypeScript Union Types into an Empty Object]() Original publisher: [Read original article]() Author: Zlaylink (Яндекс) Published: 2026-08-19T07:23:14Z Content type: tutorial Language: ru Sources: [Яндекс - Как мы делаем Яндекс / Статьи]() Topics: [TypeScript](), [ide]() Tags: [distributive](), [ide](), [omit](), [tag-39f0c170b680](), [typescript]() ### AI overview This tutorial explains how applying TypeScript's Omit utility to union types can produce an empty object type instead of preserving each union branch. Using a user-data example and event interfaces, it describes how this can remove useful type checking and autocomplete, and introduces type distributivity as the underlying concept. ### Source excerpt Представьте ситуацию: вы выкатываете новую фичу, а бэкендер спрашивает вас: "Слушай, а почему вместо событий -- пустой объект?". Вы в шоке: "Как так -- пустой объект? У меня же TypeScript, всё типизировано, такого не могло быть!". Спойлер -- могло. Меня зовут Денис Платонов, я старший разработчик интерфейсов в Телемосте и я отвечаю за on-premise развёртывание веб-клиента Телемоста в инфраструктуре заказчика. В этой статье я расскажу о том, как безобидный на первый взгляд Omit превратил наш аккуратный тип событий в пустой объект. Заодно разберём, как работает дистрибутивность типов в TypeScript и поделимся, чему нас научил этот кейс. Читать далее ## Resilient Sync: Your IDE Keeps Helping even when your Build is Broken DevFeed: [Resilient Sync: Your IDE Keeps Helping even when your Build is Broken]() Original publisher: [Read original article]() Author: Laura Kassovic Published: 2026-08-13T04:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [IntelliJ IDEA](), [ide](), [2026.2](), [configuration]() Tags: [2026-2](), [autocomplete](), [build](), [feature](), [gradle](), [ide](), [intellij-idea](), [kotlin](), [upgrade]() ### AI overview Gradle 9.7 and IntelliJ IDEA 2026.2 introduce resilient sync, allowing the IDE to remain useful when parts of a Gradle build fail to configure. Instead of aborting the entire sync, Gradle provides partial project models, editor data for resolvable Kotlin DSL scripts, and structured failure information. ### Source excerpt You upgrade Gradle, hit sync, and watch every build script turn red. The IDE that was finishing your sentences five minutes ago suddenly has nothing to say, and you're left fixing build logic in what is effectively a very expensive text editor. And the API you need to fix the error is the exact API the IDE can no longer tell you anything about. To get autocomplete back, fix the build. To fix the build, it would help to have autocomplete. Chicken, meet egg. Gradle 9.7, together with IntelliJ IDEA 2026.2, fixes this. The feature is called resilient sync, and it is one of those changes you only notice by its absence once you have it. What goes wrong today Nobody designed the old behavior to be cruel. It falls out of two entirely reasonable decisions that happen to collide. The IDE reasons that if it cannot get a model back from Gradle, it has nothing accurate to show you, so it shows almost nothing. Gradle reasons that if configuration throws, the whole operation failed, so it reports the failure and stops. Both are correct. Together they produce a tool that abandons you precisely when you need it most. The worst version is the multi-project build. You have a hundred subprojects, and one of them (or one shared convention plugin in an included build) has a broken script. In the old world, that single failure takes down the sync for all one hundred. Ninety-nine healthy projects lose their IDE support over one bad line somewhere else in the tree. Power users had a workaround, as charming as workarounds usually are: # The old "please just give me some completion" incantation. Don't rely on this. org.gradle.jvmargs=-Dorg.gradle.kotlin.dsl.provider.mode=classpath It coaxed some completion out of a broken build, frequently broke Gradle's internal state in other ways, and often needed an IDE restart to load new API. Reader, it was not a fix. It was a coping mechanism. What is resilient sync? Resilient sync replaces all-or-nothing with best-effort. When part of your build fails ## Oji Udezue on Building Claude Skills for Product Managers DevFeed: [Oji Udezue on Building Claude Skills for Product Managers]() Original publisher: [Read original article]() Author: Aakash Gupta Published: 2026-08-06T20:17:48Z Content type: article Language: en Sources: [Product Growth]() Topics: [Claude Code](), [Claude](), [Development](), [ide](), [Code]() Tags: [claude](), [code](), [deep-dive](), [development](), [essential](), [how-to](), [ide](), [skills]() ### AI overview A podcast episode featuring Oji Udezue discusses the skills product managers need to improve product judgment and keep pace with engineering. It covers open-sourced business and product skills and demonstrates a system of 17 skill files used with Claude Code. ### Source excerpt Former CPO of Typeform, Parsable, and Calendly teaches how to build immaculate product judgment as skills. ## BrowserStack Newsletter July 2026 DevFeed: [BrowserStack Newsletter July 2026]() Original publisher: [Read original article]() Author: Devanshi Jain Published: 2026-08-05T10:02:29Z Content type: article Language: en Sources: [BrowserStack Blog]() Topics: [Testing](), [Test automation](), [Artificial Intelligence](), [Playwright](), [Selenium](), [Cypress](), [ide](), [Application Performance Management (APM)](), [dashboards](), [Extension](), [Emulator](), [simulator]() Tags: [2026](), [agentic-ai](), [automation](), [automation-testing](), [cursor](), [cypress](), [features](), [ide](), [newsletter](), [product](), [selenium](), [testing]() ### AI overview BrowserStack's July 2026 newsletter announces Test Companion, an agentic AI feature for IDE-based test automation, and BrowserStack Load Testing, which combines backend load generation, real-browser performance, and APM metrics. It also highlights updates for certificates, screenshots, emulators, simulators, mobile browsers, Chrome extensions, audio logs, and diagnostic data. ### Source excerpt Read what's new at BrowserStack in July 2026 - New launches, product features, and more! ## Meet Test Companion: AI That Helps QA Teams Keep Pace with Modern Development DevFeed: [Meet Test Companion: AI That Helps QA Teams Keep Pace with Modern Development]() Original publisher: [Read original article]() Author: Rajrupa Roychowdhury Published: 2026-07-29T13:05:29Z Content type: article Language: en Sources: [BrowserStack Blog]() Topics: [Testing](), [Artificial Intelligence](), [Test automation](), [MCP Server](), [ide](), [Mobile](), [Accessibility](), [API](), [selectors]() Tags: [accessibility](), [ai](), [ai-agents](), [api](), [ide](), [logs](), [mcp-server](), [mobile](), [qa](), [selectors](), [test-companion](), [testing](), [workflows]() ### AI overview The article introduces BrowserStack Test Companion, an agentic AI test-automation tool embedded in the IDE. It is designed to help SDETs and QA teams author, execute, debug, and maintain web and mobile tests faster while preserving their existing frameworks, tools, standards, and governance. Described capabilities include generating functional, visual, accessibility, and API tests; debugging failures; analyzing logs; suggesting fixes; repairing brittle selectors and assertions; and running exploratory testing. ### Source excerpt Test Companion builds on BrowserStack's growing AI portfolio, bringing intelligent testing directly into the IDE. Combined with our BrowserStack MCP Server and specialised AI agents, it helps QA teams move faster without changing the way they already work. ## Investigating a Suspected Memory Leak in JetBrains Jewel with JVM Heap Analysis DevFeed: [Investigating a Suspected Memory Leak in JetBrains Jewel with JVM Heap Analysis]() Original publisher: [Read original article]() Published: 2026-07-28T18:00:00Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Memory Leaks](), [Compose](), [compose-multiplatform](), [jetbrains](), [ide]() Tags: [compose](), [compose-multiplatform](), [dump](), [eclipse](), [heap](), [jetbrains](), [kotlin-multiplatform](), [memory-leak]() ### AI overview The article investigates a suspected memory leak in the JetBrains Jewel project, a Compose Multiplatform library targeting desktop applications. It explains using JVM-specific tools, including heap dumps and Eclipse Memory Analyzer Tool, to examine retained heap and identify possible memory-retention issues. ### Source excerpt A kinda-brief tale about a memory leak, a heap dump, and a one-line fix. ## Three Gradle Talks from KotlinConf 2026 (and What to Steal from Each) DevFeed: [Three Gradle Talks from KotlinConf 2026 (and What to Steal from Each)]() Original publisher: [Read original article]() Author: Laura Kassovic Published: 2026-07-28T04:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [Kotlin](), [Groovy](), [ide](), [Scripting](), [Refactoring]() Tags: [2026](), [best-practices](), [build](), [build-tool](), [conference](), [developer](), [dsl](), [event](), [gradle](), [groovy](), [ide](), [kotlin](), [kotlinconf](), [refactoring](), [script](), [scripting](), [talk](), [talks]() ### AI overview The article reviews three Gradle talks from KotlinConf 2026. It explains the progression from Groovy build scripts to the Kotlin DSL and early Declarative Gradle, emphasizing the problems each approach addresses. It also introduces Gradle best practices for organizing and optimizing builds. ### Source excerpt Every year I tell myself I'll watch every conference talk I missed. Every year I get through maybe three before a build breaks and I get pulled back into real life. KotlinConf is the one event where I actually follow through, partly because the talks are short and dense, and partly because a good chunk of my coworkers and friends are on stage. This year in Munich, three of them talked about Gradle: Paul Merlin on the history of our DSLs, Stefan Wolf on best practices, and Marcin Mycek on Declarative Gradle for Kotlin. I watched all three so you can decide which ones are worth your fifteen minutes. A Tale of the Gradle DSLs -- Paul Merlin Paul has been inside Gradle's DSL machinery for years, which makes him exactly the right person to tell this story and exactly the wrong person to pretend the early days were clean. The talk traces how build logic went from Groovy, to the Kotlin DSL, to Declarative Gradle. The useful part isn't the timeline. It's that each of those was solving a real problem the previous one couldn't. Groovy gave us a flexible, dynamic scripting language, which was great right up until you wanted your IDE to tell you what was valid. The Kotlin DSL brought static typing, real autocompletion, and refactoring that doesn't rely on hope. That's why the Kotlin DSL is now the default for new Gradle builds. Declarative Gradle is the next swing: describe what your build is rather than script how it runs. The honest through-line is that none of these fully replaces the last one. Kotlin DSL is where most people should be today. Groovy still runs an enormous amount of the world's build logic and isn't going anywhere fast. Declarative Gradle is early but points at where things are headed. Real talk: if your build scripts are still Groovy and still working, you don't have to panic-migrate this weekend. But if you're starting something new, reach for the Kotlin DSL and let the IDE carry some of the weight. 📺 Watch the talk 10 Gradle Best Practices Every Kotlin Deve ## Android Studio Quail 2 Patch 1 now available DevFeed: [Android Studio Quail 2 Patch 1 now available]() Original publisher: [Read original article]() Author: Android Studio Releaser (noreply@blogger.com) Published: 2026-07-23T14:05:36Z Content type: release Language: en Sources: [Android Studio Release Updates]() Topics: [Android Studio](), [Release notes](), [ide]() Tags: [android-studio](), [release](), [release-notes](), [stable-channel](), [update]() ### AI overview Android Studio Quail 2 Patch 1 is available in the Stable channel. Existing Stable channel users can update through the Help menu, while others can download the release. The source points readers to release notes and closed issues for feature and bug-fix details. ### Source excerpt Android Studio Quail 2 Patch 1 is now available in the Stable channel. If you already have an Android Studio build on the Stable channel, you can get the update by clicking Help > Check for Updates (or Android Studio > Check for Updates on macOS). Otherwise, you can download it here. For information on new features and changes in Android Studio Quail 2, see the Android Studio release notes. For details of bugs fixed in each previous release of Android Studio Quail 2, see closed issues. ## How To Build A Skills Library For Your Engineering Team DevFeed: [How To Build A Skills Library For Your Engineering Team]() Original publisher: [Read original article]() Author: Zohar Einy Published: 2026-07-22T11:47:55Z Content type: tutorial Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [ai-coding](), [coding](), [ide](), [Git](), [GitHub](), [incident](), [Pull Request]() Tags: [ai](), [ai-coding](), [best-practices](), [coding](), [engineering](), [git](), [github](), [how-to](), [ide](), [workflows]() ### AI overview A practical guide to building a centralized skills library for an engineering team's AI coding assistants. It covers storing skills in version control, discovering skills from sources such as GitHub and engineering documentation, organizing them into use-case groups, and distinguishing required skills from optional ones. ### Source excerpt Learn how to build a skills library for engineering teams to standardize AI workflows, share best practices, and ensure consistent outputs. ## How Codex became a collaborator for OpenAI's creative team DevFeed: [How Codex became a collaborator for OpenAI's creative team]() Original publisher: [Read original article]() Published: 2026-07-16T07:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [codex](), [OpenAI](), [Artificial Intelligence](), [API](), [ide](), [API keys]() Tags: [ai](), [api](), [apis](), [codex](), [creative-tools](), [design](), [developers](), [openai](), [openai-on-openai](), [tools](), [ui](), [user-interfaces](), [workflow](), [workflows]() ### AI overview OpenAI describes how its creative team uses Codex as a context-aware collaborator to develop custom tools, workflows, user interfaces, and campaign ideas. The article highlights Codex's ability to work with creative assets and project context while helping prototype visual controls and accelerate exploration. ### Source excerpt How OpenAI's creative team uses Codex to build custom creative tools, accelerate ideation, and prototype faster with context-aware AI. [Next page]()