# Plugins Published articles for Plugins. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Mir/Wayland-Powered Miracle-WM 0.11 Released With New Overview Mode, Window Urgency DevFeed: [Mir/Wayland-Powered Miracle-WM 0.11 Released With New Overview Mode, Window Urgency]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-17T00:58:42Z Content type: release Language: en Sources: [Phoronix]() Topics: [Wayland](), [Library](), [canonical]() Tags: [commands](), [data](), [desktop-linux](), [events](), [github](), [image](), [input](), [ipc](), [library](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [open-source-graphics](), [overview](), [phoronix](), [phoronix-test-suite](), [plugins](), [release](), [ubuntu-benchmarks](), [ubuntu-hardware](), [update](), [wayland](), [window](), [windows]() ### AI overview Miracle-WM 0.11, a Wayland compositor built on the Mir library, adds an overview mode, window urgency support, plugin IPC events and commands, and support for newer Mir protocols. The release is built on Mir 2.29. ### Source excerpt Canonical engineer Matthew Kosarek rolled out Miracle-WM 0.11 today as an end-of-summer update to this Wayland compositor built atop the Mir library... ## Dropbox Evolves Riviera Content Processing Platform to Support AI Workloads DevFeed: [Dropbox Evolves Riviera Content Processing Platform to Support AI Workloads]() Original publisher: [Read original article]() Author: Leela Kumili Published: 2026-09-16T14:42:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [dropbox](), [Artificial Intelligence](), [API](), [Orchestration](), [Retrieval Augmented Generation (RAG)]() Tags: [ai](), [ai-ml-data-engineering](), [apache](), [apis](), [architecture](), [architecture-design](), [asynchronous-architecture](), [backend](), [caching](), [data-pipelines](), [development](), [distributed-systems](), [dropbox](), [dropbox-riviera-ai-platform](), [embeddings](), [enterprise-content-management](), [large-language-models](), [ml-data-engineering](), [model-context-protocol-mcp](), [news](), [orchestration](), [platform-engineering](), [plugins](), [rag](), [tika]() ### AI overview Dropbox has expanded Riviera from an internal file-preview service into a content-processing platform supporting more than 300 file formats and over 100 transformation capabilities. The platform supports Dropbox products including Search, Replay, Sign, and Dash, and provides APIs for asynchronous document conversion, media transcription, and structured metadata extraction for AI and RAG workflows. ### Source excerpt Dropbox has evolved Riviera from a file preview service into a universal content processing platform supporting more than 300 file formats and over 100 transformation capabilities. Processing hundreds of thousands of transformations per second, Riviera now supports Search, Replay, Sign, and Dash, while its APIs enable asynchronous content extraction for AI and RAG workflows. By Leela Kumili ## 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 [...] ## WordPress.com Education launches free classroom plans for teachers and students DevFeed: [WordPress.com Education launches free classroom plans for teachers and students]() Original publisher: [Read original article]() Author: L. Jeffrey Zeldman Published: 2026-08-17T15:12:09Z Content type: release Language: en Sources: [Jeffrey Zeldman]() Topics: [WordPress](), [Website]() Tags: [automattic](), [blogs-and-blogging](), [career](), [community](), [courseware](), [creativity](), [education](), [free](), [free-software](), [launches](), [learning](), [open-source](), [platforms](), [plugins](), [publishing](), [sftp](), [software](), [ssh](), [students](), [teaching](), [websites](), [wordpress]() ### AI overview Automattic has launched WordPress.com Education, a free classroom product that gives students WordPress.com domains, optional .blog or .art domain names, and plugin support. Teachers can provide access free for the first year without entering payment details. ### Source excerpt Meet WordPress.com Education, a new, free product for teachers and students. The post For students who make websites appeared first on Jeffrey Zeldman Presents. ## 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 ## ChatGPT education plugins: What changes for developers DevFeed: [ChatGPT education plugins: What changes for developers]() Original publisher: [Read original article]() Author: Atharva Deosthale Published: 2026-08-06T00:00:00Z Content type: article Language: en Sources: [Appwrite Blog]() Topics: [ChatGPT](), [Artificial Intelligence](), [OpenAI](), [Claude](), [Back end]() Tags: [agentic](), [agentic-ai](), [ai](), [apps](), [backend](), [chatgpt](), [claude](), [developers](), [education](), [integration](), [openai](), [plugins](), [workflows]() ### AI overview OpenAI's three ChatGPT education plugins for ChatGPT Work and Codex bundle apps, skills, instructions, and workflows for K-12 educators, college educators, and college students. The article explains access through ChatGPT Edu and ChatGPT for Teachers, and argues that plugins and grounding layers such as Learning Commons may become important distribution and infrastructure for EdTech developers. ### Source excerpt OpenAI's ChatGPT education plugins bring agentic AI to K-12 and college workflows. See what shipped, who gets access, and what EdTech developers should build. ## 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 ## Introducing Agent Plugins 1.0.0 DevFeed: [Introducing Agent Plugins 1.0.0]() Original publisher: [Read original article]() Author: Jonathan Hefner Published: 2026-08-06T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Agent Skills](), [Model Context Protocol](), [client](), [JSON](), [ChatGPT](), [codex](), [cursor](), [GitHub](), [Kiro](), [vs-code]() Tags: [agent](), [agent-skills](), [announcement](), [chatgpt](), [codex](), [cursor](), [distribution](), [github](), [github-copilot](), [guide](), [kiro](), [manifest](), [mcp](), [plugins](), [policy](), [portable](), [skills](), [user-experience](), [vs-code]() ### AI overview Agent Plugins 1.0.0 is an open, vendor-neutral standard for packaging Agent Skills and MCP servers into portable plugins. It defines a common root manifest and fixed component locations while allowing each compatible client to control installation, distribution, policy, user experience, and client-specific capabilities. ### Source excerpt Agent Plugins 1.0.0 is now available. It is an open, vendor-neutral standard for packaging Agent Skills and MCP servers into portable plugins. Compatible agent clients can discover and load them. Agent Plugins defines a common format: a root plugin.json manifest, plus fixed locations for portable components. Each client keeps control of installation, distribution, policy, user experience, and client-specific capabilities. At launch, Agent Plugins is supported across the following clients: ChatGPT and Codex Cursor GitHub Copilot Kiro VS Code Read the specification and implementation guides, learn more in the announcement post, and follow our guide to build a plugin on the new standard. Read more ## wasmCloud 2.6: Trigger services, host component plugins, and warm instance pooling DevFeed: [wasmCloud 2.6: Trigger services, host component plugins, and warm instance pooling]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2026-08-03T00:00:00Z Content type: release Language: en Sources: [wasmCloud Blog]() Topics: [WebAssembly](), [Messaging](), [Latency]() Tags: [components](), [dns](), [latency](), [plugins](), [services](), [stateful](), [streaming](), [wasmcloud](), [webassembly]() ### AI overview wasmCloud 2.6.0 and patch 2.6.1 introduce trigger services, host component plugins, warm-instance pooling, default NATS consumer groups for replicas, per-component DNS allowlists, Wasmtime 47 updates, and direct WASI 0.3 component builds. ### Source excerpt wasmCloud 2.6 ships trigger services, host component plugins (WebAssembly components that extend the host), warm-instance pooling, consumer groups by default for NATS messaging, and per-component DNS allowlists. ## What is the ROI of Spotify's Backstage internal developer portal? DevFeed: [What is the ROI of Spotify's Backstage internal developer portal?]() Original publisher: [Read original article]() Author: Sooraj Shah Published: 2026-07-30T11:28:26Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [Backstage](), [internal developer portal](), [Platform Engineering](), [Open Source](), [Back end](), [Front end]() Tags: [backend](), [backstage](), [cost](), [developer-portal](), [financial](), [frontend](), [internal-developer-portal](), [open-source](), [platform-engineering](), [plugins]() ### AI overview The article examines the return on investment of using Spotify's Backstage to build an internal developer portal. It argues that Backstage's open-source flexibility can obscure substantial development, staffing, customization, plugin, time, and financial costs, and that teams may underestimate the effort required to operate it. ### Source excerpt Implementing Backstage comes with hidden development and financial costs -- learn whether they're worth it in this post. ## Khronos Sponsors Open-Source glTF Importer/Exporter for Autodesk 3ds Max DevFeed: [Khronos Sponsors Open-Source glTF Importer/Exporter for Autodesk 3ds Max]() Original publisher: [Read original article]() Author: jphilips (jeff@khronosgroup.org) Published: 2026-07-14T13:00:00Z Content type: release Language: en Sources: [Blogs Khronos Blog]() Topics: [Open Source](), [3D](), [Tool](), [Documentation]() Tags: [3d](), [animation](), [apache](), [api](), [blog-glt](), [cameras](), [compression](), [documentation](), [gltf](), [lighting](), [mesh](), [open-source](), [plugin-development](), [plugins](), [render](), [standards]() ### AI overview The Khronos Group sponsored and released open-source glTF 2.0 importer and exporter plugins for Autodesk 3ds Max under the Apache 2.0 license. The plugins support round-trip glTF workflows, including scene content, materials, textures, compression, animation, lighting, and instancing. ### Source excerpt The Khronos Group has sponsored the glTF 2.0 Importer/Exporter for Autodesk 3ds Max open-source project under the Apache 2.0 license, and today has released the resulting glTF importer and exporter plugins, built to professional standards in collaboration with the community, and free for all to use. ## 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. ## PM Skills 2.0: Red-Team Your Roadmap, Then Check the Code Before You Ship DevFeed: [PM Skills 2.0: Red-Team Your Roadmap, Then Check the Code Before You Ship]() Original publisher: [Read original article]() Author: Paweł Huryn Published: 2026-06-05T17:55:04Z Content type: release Language: en Sources: [The Product Compass]() Topics: [Claude](), [Artificial Intelligence](), [GitHub](), [test](), [execution]() Tags: [ai](), [claude](), [command](), [env-file-security](), [github](), [plugins](), [release](), [review]() ### AI overview PM Skills 2.0 is a free, MIT-licensed Claude marketplace release with 68 skills, 42 commands, and 9 plugins. It adds the /red-team-prd command and an AI Shipping Kit for documenting, auditing, and shipping AI-built applications with human sign-off. ### Source excerpt 68 free Claude skills, 42 commands, 9 plugins. This release adds a new /red-team-prd command and the AI Shipping Kit: a way to document, audit, and ship AI-built apps with human sign-off. ## Build a Repository Harness for Claude Code Coding Agents DevFeed: [Build a Repository Harness for Claude Code Coding Agents]() Original publisher: [Read original article]() Author: Engin Diri Published: 2026-05-26T00:00:00Z Content type: opinion Language: en Sources: [Pulumi]() Topics: [Claude Code](), [AI-assisted coding](), [Tooling](), [Code](), [Command-line interface](), [MCP]() Tags: [ai](), [ai-agents](), [claude](), [claude-code](), [coding-agents](), [devops](), [extension](), [hooks](), [ls](), [mcp](), [perspectives](), [plugins](), [skills](), [tooling]() ### AI overview The article argues that, in real codebases, the context and tooling surrounding Claude Code can matter more to performance than the underlying model version. It presents a repository-level AI harness built from seven components, including CLAUDE.md, hooks, skills, plugins, LSP, MCP, and subagents, and discusses agentic navigation without a separately maintained codebase index. ### Source excerpt Anthropic shipped a piece earlier this month called How Claude Code Works in Large Codebases. I have not read anything more useful about coding agents this year. The core claim, in their words: "the ecosystem built around the model--the harness--determines how Claude Code performs more than the model alone." In my phrasing: in a real codebase, the model is the smaller variable. The layer of context and tooling you wire around the agent matters more than which version of Sonnet or Opus is behind it. The post stays high-level, which is the right move for a launch piece. What I want to do here is land it. Same seven pieces, but with the wiring you would actually put in a repo, in the order I would put it. How Claude Code navigates without an index Anthropic's writeup says Claude Code works from the live codebase and does not require a codebase index to be built, maintained, or uploaded. The agent navigates the way an engineer would, with grep, find, ls, file reads, and reference-following. Anthropic calls this agentic search, and the upside is obvious: no separate index exists for you to keep fresh. The downside is also obvious. An engineer who has never seen your repo and only has shell tools will flounder if you drop them in the root with no map. That is your agent on day one. Everything that follows is about giving it the map. The AI layer in seven pieces Every codebase used to have two artifacts engineers cared about: the code and the tests. A third exists now. Call it the AI layer, or the harness, or whatever you want. This layer is the set of context and tools you give your coding agent to operate in this specific repo. Anthropic breaks it into seven pieces, and each one solves a different scaling problem. Anthropic gives each piece a role: CLAUDE.md is the foundation, hooks do self-improvement, skills are progressive disclosure, plugins handle distribution, LSP gives navigation, MCP is extension, subagents split exploration from editing. They are not equal in usag ## Backstage in Amsterdam: Highlights from BackstageCon and KubeCon + CloudNativeCon Europe 2026 DevFeed: [Backstage in Amsterdam: Highlights from BackstageCon and KubeCon + CloudNativeCon Europe 2026]() Original publisher: [Read original article]() Author: André Wanlin, Emma Indal & Ruxandra Stanciu, Spotify Published: 2026-04-20T00:00:00Z Content type: article Language: en Sources: [Backstage Software Catalog and Developer Platform Blog]() Topics: [Backstage](), [Developer experience](), [internal developer portal](), [Tooling](), [Command-line interface](), [Maintainers](), [pull-requests]() Tags: [2026](), [backstage](), [catalog](), [cli](), [community](), [contributors](), [developer-experience](), [developer-portal](), [ecosystem](), [engineering](), [europe](), [explore](), [idp](), [internal-developer-platform](), [keynote](), [kubecon](), [maintainers](), [open-source](), [platform-engineering](), [plugin](), [plugins](), [pull-requests](), [q-a](), [red-hat](), [software-catalog](), [software-templates](), [techdocs]() ### AI overview A recap of BackstageCon and KubeCon + CloudNativeCon Europe 2026 in Amsterdam highlights community talks, maintainer discussions, a documentary premiere, a live keynote demonstration, and ContribFest. It also covers Backstage deployment governance, unified developer experience, catalog workflows, platform CLI usage, and the plugin ecosystem. ### Source excerpt Backstage in Amsterdam: Highlights from BackstageCon and KubeCon + CloudNativeCon Europe 2026 ## How to Sell WordPress Plugins and Themes: The Complete 2026 Guide DevFeed: [How to Sell WordPress Plugins and Themes: The Complete 2026 Guide]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-04-06T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [WordPress themes and plugins](), [WordPress Plugins](), [WordPress](), [Support]() Tags: [2026](), [digital-products](), [guide](), [how-to](), [marketplaces](), [monetization](), [payment](), [payment-processing](), [plugins](), [pricing](), [product](), [themes](), [wordpress]() ### AI overview A practical 2026 guide to selling WordPress plugins and themes. It covers licensing, pricing, updates, support, payment processing, and the trade-offs between marketplaces and direct sales, including WordPress.org and Envato Market. ### Source excerpt Learn how to sell WordPress plugins and themes online with the right licensing, pricing, delivery, and payment setup - without marketplace commissions. ## How to Monetize Figma Plugins in 2026 DevFeed: [How to Monetize Figma Plugins in 2026]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-03-29T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Figma plugins](), [Figma plugin](), [Figma Community](), [Development]() Tags: [2026](), [developers](), [figma](), [figma-plugins](), [how-to](), [license-keys](), [merchant-of-record](), [monetization](), [payment](), [payments](), [plugins](), [product-development](), [revenue](), [scale](), [validation](), [visibility]() ### AI overview A guide to monetizing Figma plugins through a freemium model, external payment infrastructure, Merchant of Record services, and secure license key management. ### Source excerpt Learn how to build a sustainable revenue stream from your Figma plugins using a freemium model and secure license key management. ## session-bridge: I Made Two Claude Code Sessions Talk to Each Other DevFeed: [session-bridge: I Made Two Claude Code Sessions Talk to Each Other]() Original publisher: [Read original article]() Author: Shreyas Patil Published: 2026-03-20T13:09:22Z Content type: opinion Language: en Sources: [Shreyas Patil's Blog]() Topics: [Claude Code](), [Code]() Tags: [agent](), [agentic-ai](), [agentic-ai-development](), [building](), [claude-code](), [claude-plugin](), [claudeai](), [context](), [plugin](), [plugins]() ### AI overview A developer describes building session-bridge, a Claude Code plugin that lets separate sessions for a library and its consumer application communicate and share context across repositories. The article covers the motivation, architecture, design decisions, failures, and shipped result. ### Source excerpt Building 'session-bridge': A Claude Code plugin that allows separate AI sessions to communicate and share context across different repositories. ## Here's my list of reasons for using Opencode DevFeed: [Here's my list of reasons for using Opencode]() Original publisher: [Read original article]() Author: Kaushik Gopal Published: 2026-03-17T20:00:00Z Content type: opinion Language: en Sources: [Kaushik Gopal's Site]() Topics: [User experience (UX)](), [client](), [servers](), [context]() Tags: [agentic](), [architecture](), [bugs](), [external](), [features](), [mcps](), [models](), [opencode](), [plugins](), [switching](), [tailscale](), [ux]() ### AI overview The author gives five personal reasons for using OpenCode: switching between models, its client-server architecture, subagent and mode features, opinionated user experience, and plugin customization. The article also notes that OpenCode has bugs and missing features, which the author says have not stopped them from using it exclusively for two months. ### Source excerpt Here's my list of reasons for using Opencode. 1. Switch between models on the fly ## I'm often experimenting with the bleeding edge models as they come out. I actively switch between models for tasks and I use them all enough where I can tell the difference. Opencode lets me switch between models mid-task or mid-conversation. Fluidly. 2. client-server architecture (a.k.a built-in remote control) ## I wrote about this and agentic fluidity in more detail but tldr: Opencode has the client/server architecture baked in. So I can just start an opencode server on one machine, expose it through tailscale serve and start using it on my phone or other machines. 3. Subagent + mode features ## I talked about this on my podcast in some detail but Opencode has the best implementation of subagents and modes. You can switch to a subagent definition as your primary mode, then operate other subagents from there. It makes orchestrator-type tasks super easy. 4. Opinionated UX ## I love that OpenCode is opinionated about their UX. They don't try to be Claude Code or Codex. In the process they have some really nice UX patterns like a sidebar with ongoing file changes, context/cost, MCPs connected etc. It's the first time I've not needed to worry about a custom statusline.sh or building one. 5. "Highly" customizable via plugins ## The plugin ecosystem is highly customizable. To the point where you can add new features, integrate with external services or even modify OpenCode's default behavior. The wonderful Jesse Vincent mentioned this to me when I was stupidly contemplating a fork. What's missing # It's not all rainbows and sunshine. Anomaly -- the team behind OpenCode -- is small. Which sometimes shows, because there's definitely bugs and some features missing. But I will say... none that's deterred me from using it for the last two months, exclusively. Go give it a shot. Many of the serious AI coders I know are really liking it and switching. ## Newsletter: Improved Python Support, Merging Plugins into Core, and more DevFeed: [Newsletter: Improved Python Support, Merging Plugins into Core, and more]() Original publisher: [Read original article]() Author: Serverless Team Published: 2025-11-18T00:00:00Z Content type: news Language: en Sources: [Serverless Blog]() Topics: [serverless framework](), [Python](), [configuration](), [IAM](), [OpenTelemetry]() Tags: [aws](), [aws-lambda](), [cloud-computing](), [configuration](), [faas](), [function-as-a-service](), [how-to](), [iam](), [infrastructure-as-code](), [news](), [opentelemetry](), [plugins](), [python](), [serverless](), [serverless-architecture](), [serverless-framework](), [updates]() ### AI overview A Serverless Framework newsletter recaps built-in Python support, plugin consolidation into core, reliability improvements during upstream outages, IAM changes, and planned OpenTelemetry configuration and expanded variable resolution. It also mentions a limited-time discount and hiring for the Framework team. ### Source excerpt Serverless Framework is closing out the year with major updates--new Python support built in, improved reliability during upstream outages, key IAM changes, and upcoming features like OpenTelemetry configuration and expanded variable resolution--while also offering a limited-time 20% end-of-year discount and actively hiring for the Framework team. This post recaps what's new, what's coming next, and how to get involved. ## Three new features to help build brand momentum with Figma Buzz DevFeed: [Three new features to help build brand momentum with Figma Buzz]() Original publisher: [Read original article]() Author: Jasmine Stoy Published: 2025-10-23T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [Template](), [Code]() Tags: [ads](), [animation](), [asset-management](), [customization](), [design](), [design-systems](), [event](), [features](), [figma](), [linkedin](), [marketing](), [plugins](), [product-development](), [promotion](), [social-media](), [tools](), [video]() ### AI overview Figma Buzz introduces three features for creating branded marketing assets: configurable templates connected to design systems, plugins for tasks such as digital asset management and translation, and direct video trimming. ### Source excerpt With marketing templates that are now connected to your design system, plugins that pull in your favorite apps, and video trimming in Figma Buzz, we're giving designers and marketers new tools to create branded assets that speak volumes. ## Moving on from Nix DevFeed: [Moving on from Nix]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2025-06-17T00:00:00Z Content type: opinion Language: en Sources: [Carlos Becker]() Topics: [Nix](), [dotfiles](), [configuration](), [Homebrew]() Tags: [configuration](), [homebrew](), [nix](), [packages](), [plugins]() ### AI overview A developer explains why, after using Nix in dotfiles for more than two years, they are moving away from it. They cite Nix's broad control over files and tools, outdated packages, instability, and slow application of configuration changes, while continuing to use Homebrew for some desktop applications. ### Source excerpt After using nix in my dotfiles for over 2 years, I'm now moving away from it. Here's why. ## Introducing multi-language dynamic plugins for Redpanda Connect DevFeed: [Introducing multi-language dynamic plugins for Redpanda Connect]() Original publisher: [Read original article]() Author: James Kinley Published: 2025-06-17T00:00:00Z Content type: release Language: en Sources: [Redpanda]() Topics: [gRPC](), [SDKs](), [Go Language](), [Python](), [Processes](), [streaming-data-processing](), [Unix]() Tags: [ai-ml-capabilities-in-streaming-data](), [architecture](), [configuration](), [creating-plugins-in-golang-and-python](), [dynamic-vs-compiled-plugins](), [framework](), [go](), [grpc-plugin-system](), [integration](), [interfaces](), [ipc](), [language-agnostic-plugin-system](), [multi-language-plugin-development](), [pipelines](), [plugin-development](), [plugins](), [process](), [processes](), [product](), [protocol](), [python](), [python-sdk-for-streaming-data](), [redpanda-connect](), [redpanda-connect-dynamic-plugins](), [redpanda-streaming-infrastructure](), [runtime-loaded-plugins-grpc](), [sdk](), [sdks](), [stream-processing](), [streaming-data-pipeline-plugins]() ### AI overview Redpanda Connect introduces Apache 2.0-licensed dynamic plugins in Beta with version 4.56.0. Plugins can be loaded at runtime as external executables that communicate with the main process through gRPC over Unix sockets, enabling plugin development in Go and Python. Official SDKs support both languages, while native Go plugins remain the preferred option for performance-critical workloads. ### Source excerpt Redpanda Connect dynamic plugins framework allows you to create and load plugins at runtime, opening up a world of new integration possibilities beyond Go. ## Ctrl-alt-elite: How our engineers move so fast DevFeed: [Ctrl-alt-elite: How our engineers move so fast]() Original publisher: [Read original article]() Author: Shlok Shah Published: 2025-05-12T10:43:33Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [Terminal](), [Raycast extension](), [Claude](), [Prompt Engineering](), [Visual Studio Code](), [incident](), [Go Language](), [React]() Tags: [building](), [claude](), [code](), [debug](), [design](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [outage](), [plugins](), [post-mortem](), [slack-incident](), [terminal](), [tools](), [vscode](), [workflow]() ### AI overview An incident.io intern describes the deliberate laptop setup, shortcuts, Raycast plugins, terminal use, and Claude practices that help the company's engineers work quickly and collaboratively. ### Source excerpt Moving fast does not happen by accident. Here is some of the intentional things our engineers do to move so quickly! [Next page]()