Copia Actions is now available — a workflow engine built directly into Copia that lets you automate the repetitive tasks your team has been running by hand.

What's new

Copia Actions lets you define workflows that live alongside your code in Copia. Lightweight, self-hosted workflow runners execute those workflows based on triggers like commits, pull-requests, issues, or DeviceLink backup events. Results and artifacts can be stored directly in your repo for audit-worthy change tracking and management.

How it helps

If your team is manually running mirror scripts, rebuilding compliance reports from git logs, or doing drift audits by hand, Actions can help automate the cycles. You can standardize the operations and share as part of a repo template to make sure every repo you create in Copia inherits your quality.

Learn More

We're happy to announce that Copia now supports Siemens TIA Portal v21 for Source Control rendering. Support for DeviceLink automated backups is planned soon.

No user action is required in Copia to start version controlling Siemens TIA Portal v21 project files. See our documentation for more information on supported file types. 

At Copia, protecting the OT networks our customers rely on is a core responsibility. The DeviceLink Agent runs inside some of the most sensitive parts of your industrial infrastructure, and we hold that trust seriously. That's why we're announcing an important security improvement to how the DeviceLink Agent handles Script backup jobs.

What Changed

Previously, Script backup jobs could pull any script file stored in a Copia repository and execute it directly on the host running the DeviceLink Agent — without any additional controls on the agent side. While this required write access to Copia's web application to configure, it still meant that a script stored in Copia could run with the full privileges of the agent process on a machine sitting inside your OT network.

Starting today, every script that a backup job attempts to execute must be pre-approved in an allowlist file on the host running the agent. This allowlist can only be modified by an administrator account on the agent host. If a script's path is not in the allowlist, the backup job will fail immediately and the script will not run. This moves control of what can execute on your OT servers from the Copia web application to the server itself, where your IT and OT security teams have direct authority.

Who Needs to Take Action

If you are currently running Script backup jobs, in order to ensure operational continuity, we have automatically generated a script allowlist for you based on the scripts you have already configured in Copia. You should verify that the allowlist file exists on each host running the DeviceLink Agent and that it contains the paths of your authorized scripts.

If you are setting up new Script backup jobs, you will need to create the allowlist file manually before those jobs will execute successfully.

Our documentation contains detailed instructions on how to create and use the script allowlist.

Why This Matters for OT Security

The principle of "defense in depth" is foundational to OT cybersecurity: every additional step taken towards hardening your security is cumulative. By requiring scripts to be explicitly approved on the agent host, we ensure that no change to a Copia repository, whether accidental or malicious, can cause arbitrary code to execute on a machine inside your OT network without the explicit approval of the team managing that server.

We will continue to invest in security improvements like this one to protect your OT infrastructure. If you have questions about this change or need help with your existing script backups, please reach out to our support team.

We're excited to announce enhancements to our Advanced Merge Tool in Source Control, designed to give you even greater flexibility when merging Siemens TIA Portal projects.

What's New?

Available now, our latest update introduces deeper merge capabilities for Structured Text (SCL) routines in TIA Portal projects. Building on the DB and Tag Table merge support we released last year, the Advanced Merge Tool now provides line-level merge resolution for SCL files. This means you can resolve conflicts with greater precision, choosing specific lines within an SCL routine instead of being limited to accepting an entire file from one branch.

How This Helps:

• Reduced Rework: No more overwriting a colleague's changes just because you both modified the same SCL file. Pick and choose the exact lines you need.
• Improved Collaboration: Merge code changes from multiple contributors to the same Structured Text routines with confidence and ease.
• Enhanced Accuracy: Maintain code integrity and minimize the risk of errors during complex merges — especially for large SCL files where only a few lines have actually changed.
• Increased Speed: Spend less time manually reconciling changes outside of Copia, and more time shipping code.

This enhancement is part of our ongoing commitment to provide you with the most powerful and user-friendly Industrial DevOps platform. We continuously strive to meet the evolving needs of our customers and improve your experience.

Learn More:

For detailed information and examples of SCL Line-Level Merge in action, please visit our updated documentation.

AI models are advancing quickly, and those advances let us reason over far larger amounts of context. We want to pass those capabilities directly to you so Copia Copilot can work with whole projects and long-form engineering artifacts the way humans do, without repeatedly chopping things into pieces.

That’s why we’re excited to announce that Copia Copilot now supports a 1,000,000-token context window for customers — up from 140,000 tokens, a more than sevenfold increase.

What this means for your workflows

With a 1M token window, Copia Copilot can hold far more of your project context in a single session. That unlocks practical gains across many common industrial and automation workflows:

• Analyze larger projects: A larger context window means larger projects can be analyzed in their entirety, rather than in subsections, allowing for richer code analysis.
• Attach specification documents: Conversations can include documents such as a User Requirements Specification (URS) document or a device specification document, allowing for contextually relevant code generation that adheres to specific requirements, styles, or device types.
• Compare multiple files: Attach multiple project files to compare code between projects or between different revisions of the same project.

Practical benefits

• Fewer workarounds: Less time spent splitting files, pasting snippets, or stitching context together manually.
• Faster root-cause and change analysis: Copilot can propose changes that take the entire project into account.
• Richer conversations with Copilot: Ask higher-level, cross-document questions and get answers that reflect the whole system.

Try it now

This expanded token window is available now to customers of Copia Copilot. We’re eager to see how you use it, whether that’s analyzing larger projects, running end-to-end project analyses, or surfacing insights from long-form documentation. If you run into edge cases or have feedback about large-file workflows, please reach out to your Copia contact or contact@copia.io.

Thanks for building with Copia — we’ll keep pushing model advances into the product so you can work at the scale your projects require.

Copia now supports Omron Sysmac Studio projects in Source Control.

This release enables users to manage Sysmac Studio PLC projects in their Copia repositories, now with graphical rendering, diffing, and code commenting support. Omron projects can now live alongside the rest of your automation code in a single source of truth.

This initial release includes Source Control support only. DeviceLink backup support for Omron Sysmac Studio is planned for the near future and will enable automated backups directly from Omron PLCs into Copia.

For setup details and supported project information, please see our Documentation.

We're happy to announce that Copia now supports the newest version of Rockwell's Studio 5000 Logix Designer, V38, for both Source Control rendering and DeviceLink automated backup! No user action is required within Copia to start version-controlling or automatically backing up V38 projects. See our Documentation for more info on our Rockwell/Allen-Bradley support.

We’re excited to announce support for FactoryTalk Linx as the communication software for your DeviceLink Studio 5000 devices running FW >=V31, enabled by the Logix Designer SDK. This update expands DeviceLink’s reliability and flexibility for Studio 5000 users by addressing several common backup challenges.

What’s New

FactoryTalk Linx Support
You can now use FactoryTalk Linx on your Agent machine instead of being limited to RSLinx. This eliminates the need to recreate devices and network paths in RSLinx just to run backups.

Improved Networking
Backups now support nested communication paths. No more rewiring networks just to make DeviceLink work.

More Reliable Backups
RSLinx re-browsing issues often caused failed backups. With the Logix SDK integration, we've significantly reduced the need to manually re-browse devices.

Broader Device Coverage
Additional Rockwell controllers, such as PlantPAX devices, are now recognized and supported for backups.

For important information about the capabilities and limitations of this new feature, please visit our documentation using the button below.

View Docs

You can now connect Copia with Azure DevOps Boards and Work Items! With this integration, any commit message or Pull Request comment in Copia that references a Work Item will automatically add a comment to the corresponding Azure Work Item, including a direct link back to Copia as seen in the image below.

If your company uses Azure DevOps Work Items for project management and ticket tracking, this feature now makes it easier to track changes, navigate between tools, and keep your development workflow connected.

Learn how to set it up →