# plugin Published articles for plugin. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Reimagining advertising with AI DevFeed: [Reimagining advertising with AI]() Original publisher: [Read original article]() Published: 2026-09-16T13:00:00Z Content type: release Language: en Sources: [OpenAI News]() Topics: [Artificial Intelligence](), [OpenAI](), [ChatGPT](), [hubspot](), [Shopify]() Tags: [advertising](), [agents](), [ai](), [chatgpt](), [hubspot](), [integrations](), [openai](), [plugin](), [product](), [shopify](), [sponsored]() ### AI overview OpenAI introduces AI-powered advertising features in ChatGPT, including Sponsored Agents that let users converse with select business-sponsored agents after viewing an ad. It also adds prompt-based campaign tools and AI creative tools, plus integrations with HubSpot and Shopify. ### Source excerpt Explore new AI-powered advertising experiences from OpenAI, including Sponsored Agents, tools for marketers, and integrations with HubSpot and Shopify. ## Babel in Khan Academy's i18n Toolchain DevFeed: [Babel in Khan Academy's i18n Toolchain]() Original publisher: [Read original article]() Author: Khan Academy Published: 2015-06-22T22:00:00Z Content type: tutorial Language: en Sources: [Khan Academy]() Topics: [Babel](), [Internationalization (i18n)](), [toolchain](), [es6](), [JavaScript](), [Parser](), [Universal Syntax Tree.](), [Open Source]() Tags: [api](), [architecture](), [babel](), [build](), [build-system](), [code](), [engineering](), [es6](), [eslint](), [frontend](), [javascript](), [news](), [plugin](), [source](), [structure](), [syntax](), [tests](), [toolchain](), [types](), [web-frontend](), [workflow]() ### AI overview Khan Academy describes switching its ES6 and JSX frontend compilation from jstransform to Babel. The article explains a custom Babel plugin for preserving the project's internationalization behavior and discusses matching generated output, line numbers, whitespace, and the existing build chain. ### Source excerpt By Kevin Barabash We've been using ES6 (along with JSX) for sometime at Khan Academy. Right now, we're ... Read more ## Laravel Vet: Review Composer Code Before It Installs DevFeed: [Laravel Vet: Review Composer Code Before It Installs]() Original publisher: [Read original article]() Author: Eric L. Barnes Published: 2026-09-15T13:33:11Z Content type: release Language: en Sources: [Laravel]() Topics: [Composer](), [Laravel](), [PHP](), [Security]() Tags: [dependency](), [laravel](), [news](), [php](), [plugin](), [security](), [supply-chain](), [trust]() ### AI overview Laravel Vet is a first-party Composer plugin that displays dependency code changes before installation, records trusted package files in vet.json, and blocks updates containing untrusted changes. It can also send changes to local coding agents for review. ### Source excerpt Laravel Vet is a new first-party Composer plugin that shows you the code in every dependency update and records the packages you trust in vet.json. The post Laravel Vet: Review Composer Code Before It Installs appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox. ## Design in KiCad, Quote with AIVON: A Faster Path to PCB Prototyping (Sponsored) DevFeed: [Design in KiCad, Quote with AIVON: A Faster Path to PCB Prototyping (Sponsored)]() Original publisher: [Read original article]() Author: Sponsored Post Published: 2026-09-15T02:00:57Z Content type: article Language: en Sources: [CNX Software - Embedded Systems News]() Topics: [Hardware](), [systems]() Tags: [aivon](), [engineering](), [hardware](), [kicad](), [manufacturing](), [pcb](), [plugin](), [prototyping](), [sponsored](), [verification](), [workflow]() ### AI overview AIVON's official KiCad Plugin connects a completed PCB layout to an online quotation form. After design-rule checking, it prepares manufacturing data and reduces manual exporting, zipping, uploading, and form entry during PCB prototyping. ### Source excerpt Finished your PCB layout in KiCad? You don't necessarily need to leave the PCB Editor, export a separate set of manufacturing files, and manually upload them to a PCB manufacturer. AIVON's KiCad Plugin creates a direct path from your PCB design to an online PCB quote. AIVON has integrated an official KiCad plugin that connects a finished PCB layout to the company's online quotation page. After DRC, users can click the plugin in the PCB Editor, automatically prepare manufacturing data, and land on a pre-filled quote form instead of exporting, zipping, and uploading files by hand. Rather than introducing a new plugin framework, AIVON's integration leverages KiCad's existing Plugin and Content Manager ecosystem. For developers who already use KiCad for schematic capture and PCB layout, the integration provides another way to connect the design stage with PCB fabrication without manually repeating every manufacturing-file preparation step. Connecting KiCad PCB Design with [...] The post Design in KiCad, Quote with AIVON: A Faster Path to PCB Prototyping (Sponsored) appeared first on CNX Software - Embedded Systems News. ## Agent Plugins package your skills, tools, and more DevFeed: [Agent Plugins package your skills, tools, and more]() Original publisher: [Read original article]() Author: Kevin Hou; Haoyu Wang; Alan Blount Published: 2026-09-12T11:04:33.891311Z Content type: article Language: en Sources: [Google Developers Blog]() Topics: [Agent Skills](), [Model Context Protocol (MCP)](), [MCP Server](), [Google](), [amazon](), [Microsoft](), [OpenAI](), [Vercel]() Tags: [agent-skills](), [amazon](), [google](), [maintainers](), [manifest](), [mcp](), [mcp-server](), [microsoft](), [openai](), [plugin](), [portable](), [skills](), [vercel]() ### AI overview The article introduces Agent Plugins 1.0.0, a vendor-neutral specification for packaging Agent Skills and MCP servers into portable plugins. It standardizes the manifest and directory layout so developers can distribute one package across clients while preserving client-specific flexibility. Google is joining the Core Maintainers and beginning support in its products. ### Source excerpt Agent Plugins 1.0.0 is a new, vendor-neutral directory specification--backed by Google, Amazon, Microsoft, and others--for packaging Agent Skills and MCP servers into a single portable unit. By standardizing the manifest (plugin.json) and utilizing a fixed directory layout, it eliminates the need for developers to maintain separate wrappers or configurations to support different AI coding agents and IDEs. Google has officially joined as a Core Maintainer and already rolled out support in the Agents CLI and Data Agent Kit, allowing developers to start building and distributing interoperable plugins today. ## Why the AWS PACE Team Built Its Full-Stack Scaffolding as an Nx Plugin DevFeed: [Why the AWS PACE Team Built Its Full-Stack Scaffolding as an Nx Plugin]() Original publisher: [Read original article]() Author: Juri Strumpflohner Published: 2026-09-10T00:00:00Z Content type: article Language: en Sources: [Juri Strumpflohner]() Topics: [Amazon Web Services](), [coding](), [AI-assisted coding](), [Infrastructure as code](), [Template]() Tags: [ai](), [aws](), [blog](), [coding](), [coding-agents](), [devkit](), [generators](), [infrastructure-as-code](), [nx](), [plugin](), [tutorial](), [video]() ### AI overview The article explains why the AWS PACE team built full-stack scaffolding as an Nx plugin using Nx Devkit generators. It discusses predictable prototyping, generated code ownership, infrastructure and application components, and how coding agents affect plugin development. ### Source excerpt How the AWS PACE team built the Nx Plugin for AWS on the Nx Devkit, and why coding agents make building your own Nx plugin cheaper than ever. ## Standardizing Exception Message Style in Ruby DevFeed: [Standardizing Exception Message Style in Ruby]() Original publisher: [Read original article]() Author: Daniel Doubrovkine (dblock@dblock.org) Published: 2026-09-05T00:00:00Z Content type: article Language: en Sources: [Daniel Doubrovkine]() Topics: [Ruby](), [Exception](), [ci]() Tags: [ci](), [exception](), [exceptions](), [grape](), [lint](), [open-source](), [plugin](), [ruby](), [standard]() ### AI overview The article explains a convention for Ruby exception messages: they should generally begin with lowercase and omit trailing punctuation because they follow the exception class name and a colon. It describes fixing seven inconsistent sites in Grape, documenting the convention, and releasing the rubocop-exception_messages RuboCop plugin to enforce casing and punctuation, with additional checks for redundant class names and interpolation markers. ### Source excerpt While reviewing dozens of PRs from ericproulx optimizing Grape's internals recently, I noticed that the bare raise ArgumentError, "..." calls scattered across the codebase were inconsistent: some messages were capitalized, some ended in a period, most were not. Longtime readers know where this is going. Ruby's own core and standard library exceptions don't do this - TypeError: no implicit conversion from nil to integer, ArgumentError: wrong number of arguments, and so on all read lowercase and unpunctuated, because the message is meant to be read after the exception class name and a colon, not as a standalone sentence. Grape's own Grape::Exceptions::* classes already follow this convention. The bare raise ArgumentError, "..." calls in dsl/entity.rb, dsl/inside_route.rb, dsl/validations.rb, and validations/types/dry_type_coercer.rb didn't, so I fixed those seven sites and documented the convention in CONTRIBUTING.md, in #2909. To avoid regressions, I wrote rubocop-exception_messages, a RuboCop plugin gem with two cops: ExceptionMessages/Casing flags (and autocorrects) messages that don't start with a lowercase letter. ExceptionMessages/Punctuation flags (and autocorrects) messages with a trailing period, with an exception for a literal ellipsis ("still processing.."), which is stylistic rather than a sentence ending. Both cops recognize raise Class, "message" and raise Class.new("message") forms, and handle interpolated (dstr) messages by only checking the literal string segments (the first segment for casing, the last for punctuation), since interpolated values in the middle are out of the cop's control. # bad raise ArgumentError, 'Missing required option.' # good raise ArgumentError, 'missing required option' The gem ships as a modern RuboCop plugin (via lint_roller), so it's a one-line addition to a consuming project's .rubocop.yml: plugins: - rubocop-exception_messages rubocop-exception_messages 0.2.0 is out now, and I've added it back to Grape's own Gemfile and ## AMD FSR plugin updated for Unreal Engine 5.8 DevFeed: [AMD FSR plugin updated for Unreal Engine 5.8]() Original publisher: [Read original article]() Author: Joe Rozek; Alexander Blake-Davies Published: 2026-08-27T12:00:00Z Content type: release Language: en Sources: [AMD GPUOpen]() Topics: [Unreal Engine](), [releases](), [GPU](), [Machine learning](), [SDKs]() Tags: [amd-fsr-3](), [amd-fsr-4](), [amd-fsr-frame-generation](), [amd-fsr-framegeneration](), [amd-fsr-upscaling](), [announcement](), [antilag](), [fsr-3](), [fsr-4](), [game-development](), [generation](), [gpu](), [ml](), [news](), [performance](), [plugin](), [product-blogs](), [product-release](), [redstone](), [release](), [super-resolution](), [technical-articles](), [unreal](), [unreal-engine]() ### AI overview The AMD FSR Unreal Engine plugin has been updated for Unreal Engine 5.8. It adds FSR Redstone SDK 2.3 updates, FSR Upscaling 4.1.1 support for AMD Radeon RX 7000 Series GPUs, and FSR Frame Generation 4.0.1 improvements. ### Source excerpt The updated AMD FSR™ Unreal® Engine plugin brings ML-powered upscaling and frame generation to Unreal Engine 5.8, now extending FSR Upscaling support to AMD Radeon RX 7000 Series GPUs. ## Your alt text passes automated checks. That doesn't mean it's any good. DevFeed: [Your alt text passes automated checks. That doesn't mean it's any good.]() Original publisher: [Read original article]() Author: Taarik Ashenafi Published: 2026-08-24T20:56:32Z Content type: article Language: en Sources: [GitHub]() Topics: [Accessibility](), [alt text](), [GitHub](), [Tooling]() Tags: [accessibility](), [alt-text](), [automation](), [blog](), [engineering](), [false-positives](), [github](), [github-actions](), [plugin](), [scanner](), [user-experience]() ### AI overview This article explains a GitHub Accessibility Scanner plugin for evaluating alt text. It distinguishes deterministic checks that automated tools can prove from contextual quality judgments that may require a model and image context. ### Source excerpt We built a plugin for the GitHub Accessibility Scanner to make sure your alt text is actually accessible. Here's how it works. The post Your alt text passes automated checks. That doesn't mean it's any good. appeared first on The GitHub Blog. ## Online index migration and shard scaling in OpenSearch with the AOSC plugin DevFeed: [Online index migration and shard scaling in OpenSearch with the AOSC plugin]() Original publisher: [Read original article]() Author: Arpit Singla Published: 2026-08-18T21:56:28Z Content type: article Language: en Sources: [OpenSearch]() Topics: [Amazon OpenSearch Service](), [migration](), [Open Source](), [Routing (disambiguation)]() Tags: [blog](), [mapping](), [migration](), [open-source](), [opensearch](), [pipeline](), [plugin](), [production](), [reconciliation](), [routing](), [schema](), [technical](), [workflow]() ### AI overview This article introduces Automatic Online Schema Change (AOSC), an open-source OpenSearch plugin for migrating live indexes to pre-created targets with different mappings, settings, shard counts, or document shapes. It backfills existing documents, replays operations made during migration, and switches an alias after a short write block, while documenting its scaling behavior and limitations. ### Source excerpt Learn how the open-source AOSC plugin migrates live OpenSearch indexes--changing mappings, settings, or shard counts--without losing writes or requiring downtime. The post Online index migration and shard scaling in OpenSearch with the AOSC plugin appeared first on OpenSearch. ## WordPress AI Connectors: A Developer's Guide to the 7.0 AI Client DevFeed: [WordPress AI Connectors: A Developer's Guide to the 7.0 AI Client]() Original publisher: [Read original article]() Author: Team WPShout Published: 2026-08-13T10:53:25Z Content type: tutorial Language: en Sources: [Back-End Development - WPShout]() Topics: [WordPress](), [WordPress AI](), [API](), [Large Language Model](), [SDKs](), [PHP]() Tags: [anthropic](), [api](), [back-end-development](), [guide](), [llms](), [php](), [plugin](), [sdk](), [wordpress](), [wordpress-ai](), [wordpress-news]() ### AI overview A developer guide to WordPress 7.0's AI connectors and AI Client. It explains provider-agnostic LLM requests, API-key configuration, credential handling, provider plugins, and building a runnable example plugin. ### Source excerpt WordPress 7.0's AI connectors and wp_ai_client_prompt() give any plugin a provider-agnostic way to talk to LLMs. Learn the API and build a working plugin. ## Visual Studio Code 1.133 DevFeed: [Visual Studio Code 1.133]() Original publisher: [Read original article]() Author: Visual Studio Code Team Published: 2026-08-12T17:00:00Z Content type: release Language: en Sources: [Visual Studio Code - Code Editing. Redefined.]() Topics: [Visual Studio Code](), [GitHub Copilot CLI](), [GitHub Copilot app](), [MCP Server](), [SDKs](), [API keys](), [EJS]() Tags: [api](), [claude](), [copilot](), [github-copilot](), [html](), [manifest](), [mcp-server](), [plugin](), [plugins](), [release](), [sdk](), [visual-studio](), [vs-code]() ### AI overview Visual Studio Code 1.133 introduces more flexible Claude sessions, including provider switching between turns and API-key access when GitHub sign-in is unavailable. It also adds an agent host for sharing sessions across VS Code windows, support for the Agent Plugins standard, and automatic reloading for HTML previews. ### Source excerpt Learn what's new in Visual Studio Code 1.133 Read the full article ## Introducing Agent Plugins DevFeed: [Introducing Agent Plugins]() Original publisher: [Read original article]() Author: Jonathan Hefner Published: 2026-08-06T00:00:00Z Content type: article Language: en Sources: [Vercel News]() Topics: [Agent Skills](), [Model Context Protocol (MCP)](), [MCP Server](), [JSON](), [Artificial Intelligence](), [Extension]() Tags: [agent-skills](), [json](), [manifest](), [mcp](), [mcp-server](), [plugin](), [plugins](), [validation]() ### AI overview Agent Plugins 1.0.0 is an open, vendor-neutral standard for packaging Agent Skills and MCP servers into distributable plugins. It defines a directory structure with a plugin.json manifest and fixed component locations, while leaving installation, distribution, policy, user experience, and client-specific capabilities to individual clients. ### Source excerpt Today, Agent Plugins 1.0.0 is publicly available. Agent Plugins is an open, vendor-neutral standard for plugins that extend AI agents. Agent Skills provide reusable instructions and resources for AI agents. MCP servers connect agents to tools and services. Both can be reused across clients, but clients often package and discover them differently. Agent Plugins gives compatible clients a common format: a directory with a plugin.json manifest and fixed locations for its components. The format is intentionally small and easy to implement, and it leaves installation, distribution, policy, user experience, and client-specific capabilities to each client. One package for the portable parts Extension authors often adapt the same component to several client formats. Even though the underlying Skill or MCP server is identical, clients often expect different top-level metadata, discovery paths, or MCP configuration. Agent Plugins gives those shared components one predictable, structured home: A minimal JSON manifest (plugin.json) identifies the specification version and names the plugin: Those two fields are the minimum requirement for the manifest, and the rest of the contract is represented in the file structure of the directory itself. A reusable component should not need to be repackaged for every client, so the format specifies only what a client needs to discover and load what is inside. Every compatible client checks for plugin.json at the plugin root. Clients that support Skills discover them under skills/. Clients that support MCP servers read their configuration from mcp.json. A client can support either component type or both. After the client validates the manifest, components are validated independently, so one invalid component does not disable unrelated ones. For plugin authors, that means fewer client-specific conventions for the same component. For client implementers, the specification defines a small, deterministic contract for discovery, validation, and lo ## Product release notes - May 2026 DevFeed: [Product release notes - May 2026]() Original publisher: [Read original article]() Author: Etay Alony Published: 2026-07-30T10:06:41Z Content type: release Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [Release notes](), [event driven](), [Claude Code](), [configuration](), [Code]() Tags: [2026](), [agentic](), [claude-code](), [code](), [community](), [configuration](), [copilot](), [event-driven](), [model](), [plugin](), [product](), [product-release](), [release](), [ui](), [workflows]() ### AI overview Port's May 2026 release adds a public plugins repository, multiple workflow triggers and placement controls, Claude Code and Copilot integrations, organization-aware browser sessions, and an opt-in sidebar layout. ### Source excerpt May extends what teams can build on Port: a public plugins repo opens the ecosystem to community use and contribution, Workflows gain multiple triggers and richer placement controls, and two new integrations bring Claude Code and Copilot activity directly into Port. ## KotlinLLM is Going Open Source DevFeed: [KotlinLLM is Going Open Source]() Original publisher: [Read original article]() Author: Anastasia Birillo Published: 2026-07-28T07:50:41Z Content type: article Language: en Sources: [Kotlin : A concise multiplatform language developed by JetBrains | The JetBrains Blog]() Topics: [kotlinllm](), [Kotlin](), [Open Source](), [IntelliJ IDEA](), [Large Language Model](), [Code generation](), [AI-assisted coding](), [Software Engineering]() Tags: [code-completion](), [code-generation](), [engineering](), [intellij](), [intellij-idea](), [kotlin](), [kotlinllm](), [llm](), [llms](), [open-source](), [plugin](), [research](), [research-prototype](), [software](), [software-engineering]() ### AI overview KotlinLLM is an open-source research prototype and IntelliJ IDEA plugin for Kotlin/JVM projects. It introduces Smart macros whose generated Kotlin source evolves from runtime scenarios, allowing applications to delegate selected logic to an LLM without calling the model on every request or relying on a separate runtime agent. ### Source excerpt TL;DR KotlinLLM is now public. It's a research prototype for delegating runtime logic to an LLM from Kotlin code. Instead of calling an LLM on every request or running a separate agent, you can write an explicit Kotlin call. Its body is generated Kotlin source code, and that code is updated as your application hits [...] ## Handling Application States and Retries in Cypress End-to-End Tests DevFeed: [Handling Application States and Retries in Cypress End-to-End Tests]() Original publisher: [Read original article]() Author: Gleb Bahmutov Published: 2026-07-28T04:00:00Z Content type: tutorial Language: en Sources: [Gleb Bahmutov]() Topics: [Cypress](), [test](), [App]() Tags: [api](), [can](), [cypress](), [errors](), [flaky](), [plugin](), [products](), [retry](), [test](), [testing](), [tests]() ### AI overview This tutorial explains how to design Cypress end-to-end tests for loading, empty, and error states. It recommends detecting known error states immediately and using in-place retries with cypress-recurse when appropriate, instead of relying only on whole-test retries. ### Source excerpt Imagine a typical application that loads some data. The app starts in the initial state, starts loading, then one of 3 possible states ar ## Harness Cursor Plugin Comes to Cursor for iOS DevFeed: [Harness Cursor Plugin Comes to Cursor for iOS]() Original publisher: [Read original article]() Author: Aurora Chun Published: 2026-07-27T00:00:00Z Content type: release Language: en Sources: [Harness Blog]() Topics: [cursor](), [Deployment](), [Security](), [CI/CD]() Tags: [ci-cd](), [cursor](), [deployment](), [ios](), [plugin](), [security]() ### AI overview The Harness Cursor Plugin now works in Cursor for iOS, allowing developers to check pipeline status, deployment health, and security posture from a phone. Read access is available by default, while write actions require confirmation and the appropriate RBAC role. ### Source excerpt The Harness Cursor Plugin now works on Cursor for iOS. Check pipeline status, security posture, and deployment health from your phone, governed by RBAC. | Blog ## The forbidden index: Building privacy-preserving search with OpenSearch DevFeed: [The forbidden index: Building privacy-preserving search with OpenSearch]() Original publisher: [Read original article]() Author: Kylie Wagar-Dirks Published: 2026-07-24T15:00:22Z Content type: article Language: en Sources: [OpenSearch]() Topics: [Open Source](), [Access Control](), [pii](), [dashboards](), [tokenization](), [data](), [elasticsearch](), [Framework]() Tags: [analytics](), [analytics-stack](), [blog](), [compliance](), [dashboards](), [data](), [dynamic-data](), [open-source](), [opensearch](), [pii](), [plugin](), [privacy](), [search](), [tokenization]() ### AI overview The article describes a talk by Unnati Mishra and Akshat Khanna on building privacy-preserving search and analytics with OpenSearch. Their approach moves privacy controls into the ingest layer, using a custom plugin to redact PII at index time through tokenization and dynamic data masking. It also applies differential privacy to OpenSearch Dashboards by adding calibrated noise to aggregate query results. ### Source excerpt At OpenSearchCon Europe 2026, Unnati Mishra and Akshat Khanna (Angel One) argued that privacy in search must be handled during the ingest phase rather than retroactively through access controls. The post The forbidden index: Building privacy-preserving search with OpenSearch appeared first on OpenSearch. ## NetBox: How to Prevent Direct Changes to the Main Branch DevFeed: [NetBox: How to Prevent Direct Changes to the Main Branch]() Original publisher: [Read original article]() Author: Rick Donato Published: 2026-07-17T12:51:04Z Content type: tutorial Language: en Sources: [Packet Coders - Learn Network Automation]() Topics: [NetBox](), [configuration]() Tags: [configuration](), [example](), [how-to](), [netbox](), [plugin](), [tips]() ### AI overview This tutorial explains how to use the NetBox Changes plugin to prevent direct changes to the main branch. It describes enabling protect_main so changes use branches and an approval workflow, and provides a configuration example. ### Source excerpt NetBox Tip! Prevent direct changes to the main branch when using the NetBox Changes plugin. Enable protect_main to ensure all changes are made through branches and follow an approval workflow. Here's an example configuration: # ./configuration.py PLUGINS_CONFIG = { "netbox_changes": { "protect_main": True, ## Vercel Plugin now available in Kimi Code CLI DevFeed: [Vercel Plugin now available in Kimi Code CLI]() Original publisher: [Read original article]() Author: Melkey Moksyakov Published: 2026-07-17T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Command-line interface](), [SDKs](), [Next.js](), [vercel ai sdk]() Tags: [ai](), [apis](), [cli](), [documentation](), [next-js](), [plugin](), [upgrade](), [vercel]() ### AI overview The Vercel Plugin is now available in the Kimi Code CLI, providing on-demand Vercel platform knowledge and skills for Next.js, AI SDK, Vercel Functions, and other technologies. It also helps keep Kimi Code current with Vercel APIs and recommended patterns. ### Source excerpt The Vercel Plugin is now available in the Kimi Code CLI. Kimi Code can now draw on Vercel platform knowledge on demand, with skills for Next.js, AI SDK, Vercel Functions, and more. The Vercel Plugin also helps Kimi Code stay up to date with the latest Vercel APIs and recommended patterns. To install it, upgrade to the latest Kimi Code CLI and select the Vercel Plugin from the Third-party section of the /plugin menu. Learn more in the Vercel Plugin documentation. Read more ## Live coding with dir stepper DevFeed: [Live coding with dir stepper]() Original publisher: [Read original article]() Published: 2026-07-16T00:00:00Z Content type: article Language: en Sources: [Jake Wharton]() Topics: [intellij-platform](), [IntelliJ IDEA](), [Git](), [ide](), [Code](), [Documentation]() Tags: [code](), [coding](), [git](), [ide](), [intellij-idea](), [intellij-platform](), [kotlinconf](), [plugin](), [presentation](), [procedural](), [refactoring]() ### AI overview The article describes creating a workflow for live-coding presentations after finding that Git commits and interactive rebases were cumbersome for managing sequential coding steps. It explores using IntelliJ IDEA as an extensible platform for a tool that can move through steps, jump to completed states, refactor steps, and keep the process unobtrusive for the presenter and audience. ### Source excerpt Two months ago I gave my first ever live programming talk at KotlinConf. It was called "Talking to terminals (and how they talk back)", and you can watch it here. I've previously done slide-heavy talks which contained small demos or navigating through an existing codebase. Since this talk was starting from nothing, I decided to just write all the code from nothing. This meant spending the majority of the time in the IDE, but also figuring out how to remember what I was supposed to be writing at each step. Making the wrong choice The exceedingly obvious solution to having a series of steps in a live coding presentation is a git repo and a commit for each step. Unfortunately, this is a huge pain in the ass and really doesn't work at all (at least not for me). I started with commits, but by the 7th or 8th commit I was spending more than half my time doing interactive rebases over the entire history. Need a function in step 8 that should've been extracted between step 3 and 4? That's another 10 minutes rewriting history. Because it's a small set of files that are changing, every commit conflicts with any changes to history. It's also not clear how you actually move through the history. We want to start from nothing and move forward through history. Generally, git helps you jump backwards from the latest, not stepping forward from the oldest. It's not impossible, it's just clearly going against the grain. The problem, defined Now thoroughly enjoying this distraction from writing the actual talk, I distilled what I was trying to solve. Ability to manually write the changes required or to simply jump to the finished step. Some steps are important to watch unfold while others are procedural. This also can help with time management when I (inevitably) run low on time. Easily refactor steps as I go. Later steps often requiring refactoring previous ones to minimize the diff. As the talk evolves I want to add or merge steps. Nearly invisible to me and the viewer. I don't want t ## Making ServiceLoader usable: a provider factory DevFeed: [Making ServiceLoader usable: a provider factory]() Original publisher: [Read original article]() Author: Stefano Fago Published: 2026-07-12T00:00:00Z Content type: tutorial Language: en Sources: [Nicolas Fränkel]() Topics: [Java](), [Code](), [JSON Web Tokens](), [JSON]() Tags: [decoupling](), [design-patterns](), [java](), [json](), [jwt](), [plugin](), [plugins](), [serviceloader](), [spi]() ### AI overview This article presents a provider-factory pattern for Java ServiceLoader. Instead of loading a service implementation directly, ServiceLoader loads a small factory with a no-argument constructor; the factory then constructs the service and can support implementation selection and custom constructors. The pattern is illustrated with a mock payments system and is related to decoupling JSON and JWT capabilities from concrete libraries. ### Source excerpt I keep coming back to java.util.ServiceLoader. I have used it to put a JSON layer behind a contract, so the core code carries no direct dependency on any particular JSON library, and I can swap the implementation without touching callers. The same shape works for JWT handling, where the concrete library might be jose4j or another JOSE implementation, and you can easily find other decoupling use-cases. ## A Real IntelliJ IDEA Inside Docker: Integration Tests with X Server, Window Manager, and Live Video DevFeed: [A Real IntelliJ IDEA Inside Docker: Integration Tests with X Server, Window Manager, and Live Video]() Original publisher: [Read original article]() Author: Eugene Petrenko Published: 2026-07-05T00:00:00Z Content type: tutorial Language: en Sources: [Eugene Petrenko]() Topics: [IntelliJ IDEA](), [Docker](), [Testing](), [Docker Container](), [FFmpeg (Fast Forward Moving Picture Experts Group)](), [GUI](), [Node.js](), [MCP]() Tags: [ai-agents](), [ai-coding](), [browser](), [devrig](), [docker](), [docker-container](), [eugene-petrenko](), [ffmpeg](), [gui](), [intellij](), [intellij-idea](), [jonnyzzz](), [mcp](), [mcp-steroid](), [node-js](), [plugin](), [tag-41199d53f463](), [testing](), [tests]() ### AI overview This tutorial presents a reusable approach for running full IntelliJ IDEA integration tests inside Docker with a GUI. It covers the container image, X server, window management, IDE control, and streaming live video to a browser, with open-source code in the test-integration module. ### Source excerpt Evals that boot a full IntelliJ IDEA -- pixels, dialogs, indexing and all -- inside a Docker container. Xvfb provides the display, fluxbox keeps the windows in place, ffmpeg records everything, and a tiny Node.js server streams the live video straight into a browser tab on your machine. Here is the whole recipe, so you can build your own. ## Опенсорсим YaGS Plugin: открытый плагин для работы с 3DGS внутри Unreal Engine DevFeed: [Опенсорсим YaGS Plugin: открытый плагин для работы с 3DGS внутри Unreal Engine]() Original publisher: [Read original article]() Author: s\_eliseev (Яндекс) Published: 2026-07-02T07:02:10Z Content type: article Language: ru Sources: [Яндекс - Как мы делаем Яндекс / Статьи]() Topics: [3D](), [Unreal Engine]() Tags: [3d](), [3dgs](), [gaussian](), [gaussian-splatting](), [plugin](), [tag-831b63de9433](), [tag-9e9e5e80d07a](), [tag-e6d9cc1f0757](), [unreal-engine]() ### AI overview The article explains how Gaussian Splatting can create photorealistic 3D representations from photographs for film production, city digital twins, and autonomous-transport simulation. It introduces YaGS Plugin, an open-source plugin that integrates Gaussian Splatting scenes into Unreal Engine, and describes the underlying 3DGS representation and reconstruction process. ### Source excerpt Представьте, что вам нужна фотореалистичная 3D-копия реального объекта или сцены: например, лица актёра для крупного плана или целой городской улицы. Сегодня для этого есть два инструмента: классическое 3D-моделирование и фотограмметрия. Однако они съедают недели работы и ломаются там, где очень важны детали, -- волосы, хром, стекло, отражения превращаются в артефакты. А на то, чтобы снять реалистичную сцену или объект так, чтобы это масштабировалось на тысячи единиц, обычно уходит слишком много времени и денег. Выход из этого тупика для целого ряда задач мы нашли в Gaussian Splatting и прогнали технологию через несколько очень разных проектов: сканирование людей и локаций для кино (например, для "Кибердеревни"), создание цифровых двойников городских кварталов и симуляцию для автономного транспорта. Инструмент один -- задачи разные. И именно на этом контрасте и родилось самое интересное. Сегодня я расскажу, как риг из 15 камер заменяет установку за сотни тысяч долларов и зачем мы используем движущегося человека как калибровочную доску. Объясню, почему для беспилотного автомобиля фотореализм обязан рождаться из данных, а не из 3D-редактора. Ну и, конечно же, расскажу про YaGS Plugin -- наш опенсорс-плагин, который делает Gaussian Splatting полноценной частью сцены в Unreal Engine. Читать далее [Next page]()