Read more of this story at Slashdot.
Read more of this story at Slashdot.
This is a maintenance release that adds a Romanian translation, fixes some important bugs, and updates the bundled FileType plugins.
There are two releases of Paint.NET:
Settings -> Updates -> Check Now.
Changes since 5.1.9:
We’re thrilled to announce that Surveys Agent - your intelligent assistant for managing surveys end-to-end - is now generally available to all commercial customers worldwide with a Microsoft 365 Copilot license.
Previously available through the Frontier preview program, Surveys Agent has helped early adopters streamline data collection and actionable insights for use cases like training sessions, employee engagement, and customer research. Now, it’s ready for everyone.
Surveys Agent simplifies the entire survey lifecycle through a conversational experience. Whether you're starting from scratch or refining an existing survey, it helps you:
No more juggling multiple tools or chasing down responses. Surveys Agent brings everything together in one place, making survey creation as easy as chatting with an expert colleague.
From drafting to distribution, Surveys Agent works seamlessly inside your Copilot experience. It suggests optimal launch plans, prepares outreach messages, and keeps you updated with response tracking. You can revisit the conversation anytime to check status, ask follow-up questions, or export results to Excel for deeper analysis.
With this broader release, Surveys Agent is now accessible to all commercial Microsoft 365 Copilot users. You can find it in the Agent Store under Built by Microsoft, ready to help you build, run, and analyze surveys with less effort.
With general availability, we’ve also introduced several key enhancements to make Surveys Agent even more powerful and intuitive:
Surveys Agent is available to business users with a Microsoft 365 Copilot license. Ready to get started? Install Surveys Agent and pin it to your Microsoft 365 Copilot sidebar for quick access. We’re excited to see how you use it—and we’re listening. Share feedback directly in the chat by rating responses with a thumbs up or thumbs down and adding your comments to help us shape what’s next.
Looking forward to seeing how Surveys Agent can support your workflow and continue to bring you from idea to insights with less effort!
three things MCP can do, and an infinite number of things it can’t do (all of which make it great)
AI agents can interact with the world using tools. Those tools can be generic or specific.
Run a bash command
Operate a web browser
Execute a SQL query
See my Google Calendar events
List my tasks in Asana
Send an email
The most general ones, like “run a bash command” and “read and write files” are built into the agent. More specific ones are provided through Model Control Protocol (MCP) servers.
Every tool provided to the agent comes with instructions sent as part of the context. Each MCP server the user configures clogs up the context with instructions and tool definitions, whether the agent needs them for this conversation or not.
If the agent can run a bash command, it can write a curl command or a script to call an API. Why use an MCP server instead?
If you want to teach your agent to do something that doesn’t require authentication–like read a web site–then by all means, let it use the tools it already knows. It can get a long way with `curl` and `jq`. Why dilute its world with more instructions when it already knows so much?
Call known APIs with simple auth
Dig around in a SQL database
Operate a web page with a playwright script
Read Figma designs and get just what it needs
Read and update your Google Calendar
Look at graphs and traces in ASCII
While “run a bash command” covers most things you want it to do, it also covers everything you don’t want an agent to do. The agent can screw with your configuration, write private data out to a public repository, and use your credentials to publish infected versions of your libraries. There is (relative) safety in specific tools. For instance, the agent’s filesystem tools reject writes to files outside of the current project. (The agent then asks my permission to do that update in bash. I say no.)
Well-designed MCPs offer the operations that make sense. They’re limited by your authorization as a user, and you can further limit their authorization when you connect or in your agent’s configuration. We can be smarter about it.
Currently, if I configure an MCP, it’s available all the time to all agent threads. Most of the time, that’s a waste of my context. I want to configure which subagents know about which MCP, so my “look at production” agent can see my observability platform, my UI-updating agent can see Figma, and my status update agent can see Asana. I also want agents to load MCP context incrementally, so that it doesn’t get every tool definition until it asks to see them.
When MCPs don’t hog context, they still won’t often beat using the innate knowledge of the model. But when you are ready to curate the access that agents have to your SaaS or data, MCPs are fantastic.
Cory House (Pluralsight/DomeTrain author and principal at ReactJS Consulting) shares the story of going “all-in” on JavaScript/React and how that focus grew into a successful independent consulting and training career. We dig into the tradeoffs of deep specialization vs breadth, how to spot real opportunities, and the “two-way door” idea for tech career moves. Cory also walks through his current pivot: using AI as a developer accelerator (how teams use it, where it helps most, what to watch out for) and how experimentation today — while tooling is cheap and rapidly evolving — is valuable. Along the way we surface mindset lessons (Cal Newport, Carol Dweck), how to balance giving away content vs paid courses, and practical tips for auditors/consultants trying to scale their impact.
Guest: Cory House — https://www.bitnative.com/
· Consulting & training: https://www.reactjsconsulting.com/
· Courses: Dometrain (TypeScript: Getting Started / Deep Dive) · YouTube: https://www.youtube.com/@housecor
· X: https://x.com/housecor
· GitHub: https://github.com/coryhouse
· DevOpsDays Des Moines (speaker): https://devopsdays.org/events/2025-des-moines/welcome/
· Podcast: https://eitl.ai/podcast/
· Books: So Good They Can’t Ignore You (Cal Newport), Mindset (Carol Dweck)