# dev-tools Developer tools are software and services used to build, test, maintain, and operate software. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## GitHub Copilot app for Beginners: Using the diff, terminal, and browser DevFeed: [GitHub Copilot app for Beginners: Using the diff, terminal, and browser]() Original publisher: [Read original article]() Author: Kayla Cinnamon Published: 2026-09-10T21:31:19Z Content type: tutorial Language: en Sources: [GitHub Engineering]() Topics: [GitHub Copilot](), [AI-assisted coding](), [dev-tools](), [web applications]() Tags: [ai-coding](), [ai-ml](), [github-copilot](), [github-copilot-app](), [github-copilot-app-for-beginners](), [pull-request](), [review](), [web-browser]() ### AI overview A beginner-oriented guide to using the GitHub Copilot app's diff, terminal, and browser panels to review agent-made code changes, run a project, preview a web feature, iterate, and create a pull request. ### Source excerpt Checking agent-generated code usually means hopping between tabs. Learn how to view diffs, run terminal commands, and preview web apps side by side in the GitHub Copilot app. The post GitHub Copilot app for Beginners: Using the diff, terminal, and browser appeared first on The GitHub Blog. ## Workflow lab: Moving between design and code with agents DevFeed: [Workflow lab: Moving between design and code with agents]() Original publisher: [Read original article]() Author: Riccardo Erra Published: 2026-08-26T22:00:00Z Content type: tutorial Language: en Sources: [Figma Blog]() Topics: [Figma](), [AI-assisted coding](), [dev-tools](), [Code](), [Pull Request]() Tags: [agents](), [ai](), [code](), [coding](), [design-systems](), [dev-tools](), [developers](), [figma](), [ui](), [workflow]() ### AI overview This workflow lab shows how designers and developers can use Figma, Figma dev tools, and coding agents to keep design and code aligned. It follows a feature from wireframes through implementation and review, emphasizing approved components, design tokens, and richer context to improve generated code and reduce rework. ### Source excerpt Coding agents are reshaping how developers build, but they're only as good as the input they're given. This workflow explores how context keeps code and canvas in sync. ## The Best WordPress Hosting in 2026 DevFeed: [The Best WordPress Hosting in 2026]() Original publisher: [Read original article]() Author: Paul Andrew Published: 2026-08-26T09:25:27Z Content type: comparison Language: en Sources: [Speckyboy Design Magazine]() Topics: [WordPress](), [WordPress Hosting](), [hosting](), [Caching](), [Security](), [dev-tools](), [ssh](), [SSL]() Tags: [caching](), [comparison](), [developer-tools](), [hosting](), [performance](), [pricing](), [security](), [ssh](), [ssl](), [support](), [tools](), [web-hosting](), [wordpress](), [wordpress-hosting]() ### AI overview A comparison of six WordPress hosting providers--WordPress.com, Bluehost, Pressable, Cloudways, Kinsta, and SiteGround--covering performance, traffic handling, uptime, pricing, support, management, security, backups, staging, caching, CDN access, and developer tools. It explains that different site types have different hosting needs and provides recommendations for common WordPress projects. ### Source excerpt Compare the best WordPress hosting providers for 2026, including pricing, performance, tools, support, and options for different types of sites. The post The Best WordPress Hosting in 2026 appeared first on Speckyboy Design Magazine. ## Agent Night demo recap: Evil Martians on making your docs discoverable to agents DevFeed: [Agent Night demo recap: Evil Martians on making your docs discoverable to agents]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-17T19:04:06Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [GitHub](), [dev-tools](), [Large Language Model](), [Search engine optimization (SEO)]() Tags: [agent](), [agents](), [developer-tools](), [docs](), [github](), [llm](), [model-training](), [retrieval]() ### AI overview Irina Nazarova's Agent Night demo recap explains how developer-tool documentation can be discovered by agents through websites and GitHub repositories. It distinguishes retrieval, which depends on access to documentation at request time, from training, which depends on whether content enters model corpora, and emphasizes repository descriptions, topics, licensing, and Markdown access. ### Source excerpt Irina Nazarova's Agent Night lightning demo: why GitHub, not your docs site, is the path into model training sets, and how Evil Martians measured all of it. ## Internal Developer Portal: How Do I Get Started? DevFeed: [Internal Developer Portal: How Do I Get Started?]() Original publisher: [Read original article]() Author: Sooraj Shah Published: 2026-07-30T10:23:42Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [internal developer portal](), [Developer experience](), [Platform Engineering](), [dev-tools](), [Microservice](), [Cloud Native Ecosystem](), [.NET MAUI]() Tags: [catalog](), [cloud-native](), [dev-tools](), [developer-experience](), [developer-portal](), [internal-developer-portal](), [jobs](), [microservices](), [onboarding](), [platform](), [platform-engineering](), [user-stories]() ### AI overview This article explains how platform engineering teams can start an internal developer portal by building a focused minimum viable product. It recommends reducing developer complexity, grounding the portal in real use cases and user stories, gathering stakeholder feedback, and improving the portal iteratively. ### Source excerpt You're using more dev tools that solve different problems, and now your breaking the developer experience. Learn the first steps to get started. ## Add API visualizations in Port with Swagger UI | Port DevFeed: [Add API visualizations in Port with Swagger UI | Port]() Original publisher: [Read original article]() Author: Dudi Elhadad Published: 2026-07-30T10:09:05Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [internal developer portal](), [OpenAPI Specification](), [Markdown](), [Microservice](), [dev-tools]() Tags: [api](), [developer-portal](), [documentation](), [integration](), [markdown](), [openapi-specification](), [software-catalog](), [visualization]() ### AI overview Port adds visualization features to its software catalog and developer portal, including Markdown documentation, OpenAPI specifications rendered with Swagger UI, and embedded URLs. These features centralize documentation, API discovery, monitoring dashboards, and other developer tools in context, reducing search and context switching. ### Source excerpt Here are the visualization features we just added: Markdown documentation visualization, Open API - swagger and embedded URLs. ## The future of the Keycloak Discourse forum DevFeed: [The future of the Keycloak Discourse forum]() Original publisher: [Read original article]() Author: GR Patil, Niko Köbler Published: 2026-07-20T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [ai-coding](), [dev-tools](), [maintenance](), [Security]() Tags: [ai](), [ai-coding](), [developer-tools](), [idm](), [kerberos](), [keycloak](), [ldap](), [maintenance](), [openid-connect](), [saml](), [security](), [sso]() ### AI overview The Keycloak project announces that it will wind down its Discourse forum. The article explains the forum's historical role, increased use of AI coding assistants and search-like developer tools, reduced forum activity, and the maintenance effort required to keep it open. ### Source excerpt The Keycloak project has always relied on open, searchable, community-owned discussion. Over the years, the Keycloak Discourse forum has been an important part of that: a place where users could ask configuration questions, share migration experiences, debug integrations, and find answers from people who had solved similar problems before. After a lot of consideration, we have decided to wind down the Keycloak Discourse forum. This is not a decision we are taking lightly. The forum contains many years of useful community knowledge, and we recognize the role it has played for Keycloak users. We also recognize that previous changes to the forum caused disruption. For that reason, we want to explain why we are making this change, how it will happen, when it will happen, and where the community should go next. Why we are making this change In June 2023, the Keycloak maintainers decided to sunset Discourse as one of the project's communication channels. That decision was met with strong feedback from the community. Many users explained that Discourse filled an important role that was not fully covered by mailing lists, GitHub Discussions, or chat. After listening to that feedback, we reactivated Discourse in October 2023. In the years since, the way developers seek help has changed. More and more Keycloak users now turn first to AI coding assistants and search-like developer tools when they need help configuring Keycloak, troubleshooting integrations, or understanding errors. Those tools have almost certainly learned from many of the public sources the community has created over the years, including the Discourse forum, GitHub Discussions, mailing lists, documentation, blog posts, and issue trackers. That shift has changed the role of a community forum. The old model depended on a steady flow of new questions, answers, corrections, and follow-up discussion. Without that activity, the forum risks becoming a stale support archive rather than a healthy community space. Keep ## OpenAI Eng & Dev Tools Founder: How Software Engineering Is Changing | Charlie Marsh DevFeed: [OpenAI Eng & Dev Tools Founder: How Software Engineering Is Changing | Charlie Marsh]() Original publisher: [Read original article]() Author: Ryan Peterman Published: 2026-06-22T09:45:53Z Content type: article Language: en Sources: [The Developing Dev]() Topics: [dev-tools](), [Development](), [Python](), [Software Engineering](), [engineering-culture]() Tags: [dev](), [dev-tools](), [engineering](), [go](), [javascript](), [linter](), [openai](), [python](), [rust](), [software-engineering](), [tooling](), [tools]() ### AI overview An interview with Charlie Marsh, founder of Astral, examines how software engineering and developer tooling are changing. Marsh discusses his experience building Python systems, limitations in Python tooling, and the influence of performance-focused native tools in the JavaScript ecosystem. ### Source excerpt Charlie Marsh is the founder of Astral, the Python devtool startup that was acquired by OpenAI. ## Google joins the Eclipse Foundation as a strategic member to accelerate AI-integrated developer tools DevFeed: [Google joins the Eclipse Foundation as a strategic member to accelerate AI-integrated developer tools]() Original publisher: [Read original article]() Author: Google Open Source (noreply@blogger.com) Published: 2026-06-10T18:30:00Z Content type: news Language: en Sources: [Google Open Source Blog]() Topics: [Google](), [Open Source](), [Artificial Intelligence](), [dev-tools](), [google-antigravity](), [Extension](), [Critical Infrastructure]() Tags: [ai](), [ai-integrated](), [antigravity](), [critical-infrastructure](), [developer-tools](), [eclipse-foundation](), [google](), [google-ospo](), [open-source](), [open-source-security]() ### AI overview Google joined the Eclipse Foundation as a Strategic Member in April 2026. It will sponsor Open VSX, participate in the foundation's governance, and support open infrastructure for AI-integrated developer platforms, along with open source security and regulatory compliance initiatives. ### Source excerpt by amanda casari & Mike Bufano, Google Open Source Collaboration with the Eclipse Foundation will support open infrastructure for AI-integrated developer platforms like Google Antigravity, while advancing broader open source security and regulatory compliance initiatives As of April 2026, Google has joined the Eclipse Foundation as a Strategic Member, reflecting the company's continued investment in open source technologies and modern developer infrastructure. As part of this collaboration, Google will additionally sponsor Open VSX and is among the first adopters of the recently announced Open VSX Managed Registry service. Open VSX is the open source, vendor-neutral extension registry for tools built on the VS Code™ extension API. It powers a rapidly growing ecosystem of AI-integrated IDEs, cloud development environments, and developer platforms, including Google Antigravity, AWS's Kiro, Cursor, and, Windsurf among many others. As a Strategic Member, Google will participate in the Eclipse Foundation's Board of Directors and Technical Advisory Council, helping guide the technical and strategic direction of one of the world's leading open source software foundations. "The industry is feeling the massive turning point as AI continues to change how developers write, deploy, and maintain software," said amanda casari of Google's Open Source Programs Office and new Eclipse Board member. "Joining The Eclipse Foundation as a Strategic Member ensures that the next generation of AI-integrated developer experiences--including platforms like Google Antigravity--are built in partnership with transparent, vendor-neutral foundations. Open registries, like Open VSX, are critical infrastructure which keep the global developer ecosystem open to everyone." Google and the Eclipse Foundation share a deep history, having collaborated across numerous initiatives since 2006. This Strategic Membership elevates the relationship and support critical to modern initiatives like Open VSX, Open Reg ## I Slop Forked Neon. You Should Too. DevFeed: [I Slop Forked Neon. You Should Too.]() Original publisher: [Read original article]() Author: Andre Landgraf Published: 2026-06-03T12:00:00Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [dev-tools](), [AI Bots](), [cursor](), [dashboards]() Tags: [agents](), [apis](), [cursor](), [dashboards](), [mcp](), [openapi](), [product]() ### AI overview The article argues that developer platforms should expose functionality through APIs, CLIs, MCP servers, and SDKs so coding agents can operate tools autonomously. It demonstrates the idea by describing an agent-built fork of the Neon console powered by Neon APIs. ### Source excerpt Agents are much better at using APIs, CLIs, and MCP servers than clicking through dashboards. That's why APIs matter even more in the age of agents. At Neon, we aim to expose all platform functionality through our open API -- if you see an action in our console, the associated endpoint should be open too. To illustrate this, I slop forked the Neon console. ## Kent Beck and Michael Grinich Discuss AI Adoption and the Future of Software Engineering DevFeed: [Kent Beck and Michael Grinich Discuss AI Adoption and the Future of Software Engineering]() Original publisher: [Read original article]() Author: Kent Beck Published: 2026-05-20T14:15:38Z Content type: opinion Language: en Sources: [Software Design: Tidy First?]() Topics: [Artificial Intelligence](), [future of software](), [Software Engineering](), [engineering-culture](), [dev-tools]() Tags: [ai](), [developer-tools](), [discussion](), [engineering-leadership](), [future-of-software](), [leadership](), [software-engineering]() ### AI overview Kent Beck and Michael Grinich discuss how AI adoption is affecting the broader technology ecosystem, software costs, competition, and engineering leadership. They also discuss enterprise developer tools and the motivation to build software. ### Source excerpt Michael Grinich & Kent Beck on AI adoption, the future of software engineering, and what enterprise developer tools reveal about where tech is headed. ## AI builders can now easily access 1Password secrets management and developer tools DevFeed: [AI builders can now easily access 1Password secrets management and developer tools]() Original publisher: [Read original article]() Author: info@1password.com (Sanjay Ramnath) Published: 2026-05-18T00:00:00Z Content type: opinion Language: en Sources: [Blog on 1Password Blog]() Topics: [dev-tools](), [SDKs]() Tags: [ai](), [ai-coding](), [api](), [api-keys](), [cybersecurity](), [developer](), [developer-tools](), [developers](), [sdks](), [secrets](), [security](), [vibe-coding]() ### AI overview The article argues that people building applications with AI coding tools need secrets management to avoid plaintext credentials and credential sprawl. It presents 1Password's developer security tools, including an SSH Agent, CLI, and SDKs. ### Source excerpt AI coding tools have changed who builds software. The barrier to entry has dropped to the point where a designer, an analyst, or a first-time founder can turn an idea into a working app in an afternoon. That shift is real, and it's accelerating. But every app needs to talk to something. Every API call, database connection, and automated workflow runs on secrets: API keys, tokens, SSH keys, service account credentials. And those secrets have to live somewhere. For most people building with AI tools today, secrets end up in a .env file, a chat message, a script, or a note that will "definitely get cleaned up later." AI coding tools are good at helping you get something working fast, but they tend to suggest the fastest path to a functioning prototype, not the most secure one. The result is real credentials stored in plain text, scattered across machines and codebases, hard to track and easy for threat actors to find when a machine is compromised. This is how credential sprawl starts. Not with a dramatic failure, but one unknowing shortcut at a time. Developers rely on secrets management tools: Now AI builders need them too Until recently, managing developer credentials was mostly a concern for engineering teams with the time and expertise to configure dedicated tooling. The people who generate secrets have historically been developers trained in secure coding. Today, that's changed. Designers are prototyping internal dashboards. Operations teams are automating repetitive tasks. Data analysts are connecting pipelines to interactive graphics. Founders are shipping their first apps without engineering teams. None of them signed up to become cybersecurity experts, but they're now handling some of the most sensitive credentials and secrets in their organizations, often without a clear path to doing it safely. The new wave of AI builders are frequently seeing directions from their vibe coding tool to either put plaintext credentials into a .env file on the computer desktop ## What's new in Svelte: May 2026 DevFeed: [What's new in Svelte: May 2026]() Original publisher: [Read original article]() Author: Dani Sandoval Published: 2026-05-01T00:00:00Z Content type: release Language: en Sources: [Svelte blog]() Topics: [Svelte](), [TypeScript](), [Command-line interface](), [releases](), [Caching](), [Forms](), [dev-tools]() Tags: [caching](), [cli](), [dev-tools](), [forms](), [release](), [svelte](), [typescript]() ### AI overview A May 2026 roundup of Svelte and SvelteKit updates, including TypeScript 6.0 support, remote function and form improvements, caching changes, experimental Svelte CLI community add-ons, and selected community projects. ### Source excerpt This month we got a ton of improvements to SvelteKit's remote functions, TypeScript 6.0 support and the experimental release of community plugins in the Svelte CLI. Svelte was also featured in ThoughtWorks Technology Radar! Big month, bigger showcase... so let's dive in! What's new in SvelteKit SvelteKit now supports TypeScript 6.0 (2.56.0, Docs, #15595) form fields can now specify a default value using field.as(type, value), reducing boilerplate for pre-populated forms (2.56.0, Docs, #15577) Remote function transport now uses hydratable, enabling richer data types in query results (2.56.0, #15533) Form submit now returns a boolean to indicate submission validity for enhanced form remote functions (2.57.0, Docs, #15530) Remote Function Breaking Changes (2.56.0) Client-requested query refreshes must obtain permission from the server (#15562) Stabilize remote function caching by sorting object keys (#15570) Add run() method to queries, disallow awaiting queries outside render (#15533) Isolate command-triggered query refresh failures per-query (#15562) requested now requires limit and yields { arg, query } entries rather than validated args (#15739) Looking for more details on the many bug fixes and performance optimizations from this month? Check out the SvelteKit / Adapter CHANGELOGs. What's new in Svelte and Svelte Dev Tools Community add-ons are now available in sv as an experimental feature (sv@0.1.0, Docs, #1020) The sv and sv-utils packages are now separate in the CLI package - leading to a more explicit public API and a deprecation pass for old features (sv@0.2.0, Docs, #1046) sv will now more reliably detect if Vitest v3 is installed when configuring projects (sv@0.15.2, #1073) Types for TweenOptions, SpringOptions, SpringUpdateOptions and Updater are now available as exports from svelte/motion (svelte@5.55.0, Docs, #17967) For a full list of changes - including all the important bugfixes that went into the releases this month - check out the Svelte compiler's ## 2026 Vercel AI Accelerator recap DevFeed: [2026 Vercel AI Accelerator recap]() Original publisher: [Read original article]() Author: Madison McIlwain Published: 2026-04-28T04:00:00Z Content type: article Language: en Sources: [Vercel News]() Topics: [Vercel](), [AI Development](), [dev-tools](), [Deployment](), [anthropic](), [Amazon Web Services](), [OpenAI](), [Auth0](), [OpenClaw](), [Notion](), [Supabase]() Tags: [2026](), [agents](), [ai](), [ai-accelerator](), [anthropic](), [aws](), [deployment](), [developer-tools](), [event](), [infrastructure](), [openai](), [openclaw](), [startup](), [vercel](), [workshops]() ### AI overview Vercel recaps its 2026 AI Accelerator, a six-week program in which 39 teams built AI applications, agents, developer tools, consumer apps, and vertical AI products. The program included technical workshops, expert discussions, partner support, infrastructure credits, and a Demo Day where teams presented to investors and industry leaders. ### Source excerpt On April 16th, 39 teams took the stage to pitch investors at Demo Day. During the prior six weeks, founders worked shoulder-to-shoulder with the Vercel team, our partners, and industry leaders to shape their ideas into the next generation of AI applications. Six weeks with the 2026 cohort Teams from around the world joined the 2026 cohort, building agents, developer tools, consumer apps, and vertical AI for finance, security, healthcare, and robotics. Each week, the cohort joined two sessions: a hands-on technical workshop and a fireside chat with an external speaker. The workshops covered the technical side of building AI products, from agents and models to deployment and scale. The fireside chats brought in industry leaders, Vercel experts, and investors. Speakers included Peter Steinberger (OpenAI/OpenClaw) and the Windsurf team, with topics ranging from the state of AI to pricing, legal, sales, marketing, and fundraising. Builder day Halfway through the program, the cohort came together with the broader Vercel startup ecosystem for Builder Day at Vercel's office. The day combined technical workshops, hands-on office hours with engineers from accelerator partners like AWS and Anthropic, open time to build and connect, and a special fireside chat between Malte Ubl (Vercel CTO) and Stephen Haney (Paper CEO). $8M in infrastructure and credits Beyond the programming, every team got over $200K to build with on Vercel and across the AI stack: Vercel AI stack: AI Gateway, Sandbox, Workflows, Fluid Compute, v0, and more Partners: AWS, Anthropic, OpenAI, Browserbase, ElevenLabs, Auth0, WorkOS, Notion, Modal, Neon, Supabase, and more Demo Day After six weeks of building, the cohort showed their work at Demo Day. Auth0 hosted the event at their offices, and each team had a few minutes to present to a room of VCs, AI leaders, and partners, with a panel of judges from across the AI ecosystem selecting the winners. Winners On Demo Day, judges scored teams on problem validity, ## How Cursor Handles Billing: A Complete Breakdown DevFeed: [How Cursor Handles Billing: A Complete Breakdown]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-04-08T00:00:00Z Content type: article Language: en Sources: [Dodo Payments Blog]() Topics: [cursor](), [Artificial Intelligence](), [Large Language Model](), [dev-tools]() Tags: [ai](), [billing](), [cursor](), [deep-dive](), [developer-tools](), [how-to](), [pricing](), [token]() ### AI overview This article explains Cursor's hybrid billing model, which combines a monthly subscription with a dollar-denominated pool of token-based AI usage. It covers pricing tiers, model-dependent costs, overage billing, and the abstraction layer that combines multiple model providers into one subscription experience. ### Source excerpt A deep dive into Cursor's pricing tiers, token-based usage pools, model-weighted costs, and how to build the same hybrid billing model for your own AI product. ## Polar.sh Review: 2026 Tiered Pricing, Fees, and Features for SaaS Developers DevFeed: [Polar.sh Review: 2026 Tiered Pricing, Fees, and Features for SaaS Developers]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-04-04T00:00:00Z Content type: comparison Language: en Sources: [Dodo Payments Blog]() Topics: [Software as a service](), [GitHub](), [Open Source](), [dev-tools]() Tags: [2026](), [alternatives](), [developer-tools](), [fees](), [github](), [open-source](), [payment-processing](), [pricing](), [review](), [saas]() ### AI overview This review examines Polar.sh's 2026 tiered Merchant of Record pricing, including the 5% + 50c Starter rate, paid plans, international card surcharges, chargeback fees, and payout-fee policies. It also describes Polar.sh's open-source billing features for SaaS and developer tools and compares the platform with Dodo Payments. ### Source excerpt Honest Polar.sh review for 2026 covering their new Starter/Pro/Growth/Scale plans, the 5% + 50c base rate, international surcharges, dispute and payout fees, and how it all compares to Dodo Payments' flat 4% + 40c. ## February in Servo: faster layout, pause and resume scripts, and more! DevFeed: [February in Servo: faster layout, pause and resume scripts, and more!]() Original publisher: [Read original article]() Author: The Servo Project Developers Published: 2026-03-31T00:00:00Z Content type: article Language: en Sources: [Servo Blog]() Topics: [servo](), [Web platform](), [Document Object Model (DOM)](), [dev-tools](), [Accessibility](), [API]() Tags: [accessibility](), [api](), [developer-tools](), [rust](), [servo](), [servo-engine](), [servo-rendering-engine](), [web](), [web-browser](), [web-browser-engine](), [web-engine](), [web-platform](), [web-rendering-engine]() ### AI overview This February update for Servo 0.0.6 highlights faster layout, script pause and resume work, new web platform features, expanded DOM APIs, developer tools, accessibility progress, embedding improvements, performance and stability work, and bug fixes. ### Source excerpt Servo 0.0.6 includes some exciting new features: