[go: up one dir, main page]

Skip to main content

Are AI "Autonomous Coworkers" Ready for Payroll?

Rotem Cohen
Seemplicity

As discussions around AI "autonomous coworkers" accelerate, many industry projections assume that agents will soon operate alongside human staff in making decisions, taking actions, and managing tasks with minimal oversight. But a growing number of critics (including some of the developers building these systems) argue that the industry still has a long way to go to be able to treat AI agents like fully trusted teammates. There is an absence of trust that organizations must have before allowing any system, human or machine, to handle sensitive, high-stakes work.

AI agents still struggle to consistently explain their reasoning, flag uncertainty, or guarantee compliance, making it difficult for leaders to hand over control of tasks that demand both precision and judgment. Until AI can meet these deeper trust requirements, "autonomous coworkers" will remain more aspirational than operational.

The Access-Control Blind Spot

AI agents are not inherently dangerous, but organizations still have limited visibility into what these "coworkers" can actually access or do once deployed, which is where the fear is coming from. Most enterprise systems were never designed with autonomous agents in mind; they were built for human users with predictable roles and clearly scoped permissions.

As a result, when companies plug an AI agent into these environments, they often rely on assumptions rather than certainty about what data the agent can reach, what actions it can initiate, or how broadly its permissions propagate across interconnected platforms. Even the human teams implementing them don't always have a full grasp of the permission layers behind their own systems, creating blind spots that make comprehensive oversight difficult.

Because current agents lack the built-in guardrails and explainability needed to surface actions in real time, they often don't know what to watch for in the first place. For example, they may not realize they shouldn't touch a particular folder simply because they technically have access to it. As a result, organizations may not realize something has gone wrong until the damage is already done. This disconnect between organizational assumptions and actual agent behavior turns access control into a hidden, but critical, obstacle to safe adoption.

Managing AI Hallucinations

Another barrier to treating agents as reliable collaborators is the lack of contextual understanding. Today's models can hallucinate or operate on incomplete data, and unlike human coworkers, they don't recognize when they're out of their depth.

AI systems excel at generating confident answers, even when the underlying information is missing, ambiguous, or wrong. That confidence can mask uncertainty in ways that are difficult for human users to detect, making hallucinations less of a glitch and more of an inherent byproduct of how generative models process patterns and probabilities.

For that reason, hallucinations are better understood as a chronic condition to be managed rather than a flaw that can be engineered away. No amount of fine-tuning can fully eliminate a model's tendency to fill gaps or infer details that aren't there; that's a structural feature of how they generate language and actions.

The practical path forward is building systems, guardrails, and human workflows that assume hallucinations will happen and minimize their impact when they do. Treating hallucinations as a permanent characteristic rather than a temporary bug shifts the conversation from "when will this be fixed?" to "how do we operate safely, knowing this is part of the landscape?"

The Path to Responsible Autonomy

If autonomous agents are ever to operate safely alongside humans, organizations will need to embrace a secure-by-design approach that rethinks how these systems are built, deployed, and governed. That means designing agents with least-privilege access from day one, embedding real-time auditability, enforcing reversible actions, and ensuring every autonomous decision is both explainable and overridable.

This also means aligning technical safeguards with human workflows so agents amplify accountability. The companies that take this path now will set the standard for responsible autonomy, proving that AI coworkers can be powerful collaborators when they're properly engineered with security, transparency, and human trust at their core.

Rotem Cohen Gadol is CTO at Seemplicity

The Latest

Outages aren't new. What's new is how quickly they spread across systems, vendors, regions and customer workflows. The moment that performance degrades, expectations escalate fast. In today's always-on environment, an outage isn't just a technical event. It's a trust event ...

Most organizations approach OpenTelemetry as a collection of individual tools they need to assemble from scratch. This view misses the bigger picture. OpenTelemetry is a complete telemetry framework with composable components that address specific problems at different stages of organizational maturity. You start with what you need today and adopt additional pieces as your observability practices evolve ...

One of the earliest lessons I learned from architecting throughput-heavy services is that simplicity wins repeatedly: fewer moving parts, loosely coupled execution (fewer synchronous calls), and precise timing metering. You want data and decisions to travel the shortest possible path. The goal is to build a system where every strategy and each line of code (contention is the key metric) complements the decision trees ...

As discussions around AI "autonomous coworkers" accelerate, many industry projections assume that agents will soon operate alongside human staff in making decisions, taking actions, and managing tasks with minimal oversight. But a growing number of critics (including some of the developers building these systems) argue that the industry still has a long way to go to be able to treat AI agents like fully trusted teammates ...

Enterprise AI has entered a transformational phase where, according to Digitate's recently released survey, Agentic AI and the Future of Enterprise IT, companies are moving beyond traditional automation toward Agentic AI systems designed to reason, adapt, and collaborate alongside human teams ...

The numbers back this urgency up. A recent Zapier survey shows that 92% of enterprises now treat AI as a top priority. Leaders want it, and teams are clamoring for it. But if you look closer at the operations of these companies, you see a different picture. The rollout is slow. The results are often delayed. There's a disconnect between what leaders want and what their technical infrastructure can handle ...

Kyndryl's 2025 Readiness Report revealed that 61% of global business and technology leaders report increasing pressure from boards and regulators to prove AI's ROI. As the technology evolves and expectations continue to rise, leaders are compelled to generate and prove impact before scaling further. This will lead to a decisive turning point in 2026 ...

Cloudflare's disruption illustrates how quickly a single provider's issue cascades into widespread exposure. Many organizations don't fully realize how tightly their systems are coupled to thirdparty services, or how quickly availability and security concerns align when those services falter ... You can't avoid these dependencies, but you can understand them ...

If you work with AI, you know this story. A model performs during testing, looks great in early reviews, works perfectly in production and then slowly loses relevance after operating for a while. Everything on the surface looks perfect — pipelines are running, predictions or recommendations are error-free, data quality checks show green; yet outcomes don't meet the ground reality. This pattern often repeats across enterprise AI programs. Take for example, a mid-sized retail banking and wealth-management firm with heavy investments in AI-powered risk analytics, fraud detection and personalized credit-decisioning systems. The model worked well for a while, but transactions increased, so did false positives by 18% ...

Basic uptime is no longer the gold standard. By 2026, network monitoring must do more than report status, it must explain performance in a hybrid-first world. Networks are no longer just static support systems; they are agile, distributed architectures that sit at the very heart of the customer experience and the business outcomes ... The following five trends represent the new standard for network health, providing a blueprint for teams to move from reactive troubleshooting to a proactive, integrated future ...

Are AI "Autonomous Coworkers" Ready for Payroll?

Rotem Cohen
Seemplicity

As discussions around AI "autonomous coworkers" accelerate, many industry projections assume that agents will soon operate alongside human staff in making decisions, taking actions, and managing tasks with minimal oversight. But a growing number of critics (including some of the developers building these systems) argue that the industry still has a long way to go to be able to treat AI agents like fully trusted teammates. There is an absence of trust that organizations must have before allowing any system, human or machine, to handle sensitive, high-stakes work.

AI agents still struggle to consistently explain their reasoning, flag uncertainty, or guarantee compliance, making it difficult for leaders to hand over control of tasks that demand both precision and judgment. Until AI can meet these deeper trust requirements, "autonomous coworkers" will remain more aspirational than operational.

The Access-Control Blind Spot

AI agents are not inherently dangerous, but organizations still have limited visibility into what these "coworkers" can actually access or do once deployed, which is where the fear is coming from. Most enterprise systems were never designed with autonomous agents in mind; they were built for human users with predictable roles and clearly scoped permissions.

As a result, when companies plug an AI agent into these environments, they often rely on assumptions rather than certainty about what data the agent can reach, what actions it can initiate, or how broadly its permissions propagate across interconnected platforms. Even the human teams implementing them don't always have a full grasp of the permission layers behind their own systems, creating blind spots that make comprehensive oversight difficult.

Because current agents lack the built-in guardrails and explainability needed to surface actions in real time, they often don't know what to watch for in the first place. For example, they may not realize they shouldn't touch a particular folder simply because they technically have access to it. As a result, organizations may not realize something has gone wrong until the damage is already done. This disconnect between organizational assumptions and actual agent behavior turns access control into a hidden, but critical, obstacle to safe adoption.

Managing AI Hallucinations

Another barrier to treating agents as reliable collaborators is the lack of contextual understanding. Today's models can hallucinate or operate on incomplete data, and unlike human coworkers, they don't recognize when they're out of their depth.

AI systems excel at generating confident answers, even when the underlying information is missing, ambiguous, or wrong. That confidence can mask uncertainty in ways that are difficult for human users to detect, making hallucinations less of a glitch and more of an inherent byproduct of how generative models process patterns and probabilities.

For that reason, hallucinations are better understood as a chronic condition to be managed rather than a flaw that can be engineered away. No amount of fine-tuning can fully eliminate a model's tendency to fill gaps or infer details that aren't there; that's a structural feature of how they generate language and actions.

The practical path forward is building systems, guardrails, and human workflows that assume hallucinations will happen and minimize their impact when they do. Treating hallucinations as a permanent characteristic rather than a temporary bug shifts the conversation from "when will this be fixed?" to "how do we operate safely, knowing this is part of the landscape?"

The Path to Responsible Autonomy

If autonomous agents are ever to operate safely alongside humans, organizations will need to embrace a secure-by-design approach that rethinks how these systems are built, deployed, and governed. That means designing agents with least-privilege access from day one, embedding real-time auditability, enforcing reversible actions, and ensuring every autonomous decision is both explainable and overridable.

This also means aligning technical safeguards with human workflows so agents amplify accountability. The companies that take this path now will set the standard for responsible autonomy, proving that AI coworkers can be powerful collaborators when they're properly engineered with security, transparency, and human trust at their core.

Rotem Cohen Gadol is CTO at Seemplicity

The Latest

Outages aren't new. What's new is how quickly they spread across systems, vendors, regions and customer workflows. The moment that performance degrades, expectations escalate fast. In today's always-on environment, an outage isn't just a technical event. It's a trust event ...

Most organizations approach OpenTelemetry as a collection of individual tools they need to assemble from scratch. This view misses the bigger picture. OpenTelemetry is a complete telemetry framework with composable components that address specific problems at different stages of organizational maturity. You start with what you need today and adopt additional pieces as your observability practices evolve ...

One of the earliest lessons I learned from architecting throughput-heavy services is that simplicity wins repeatedly: fewer moving parts, loosely coupled execution (fewer synchronous calls), and precise timing metering. You want data and decisions to travel the shortest possible path. The goal is to build a system where every strategy and each line of code (contention is the key metric) complements the decision trees ...

As discussions around AI "autonomous coworkers" accelerate, many industry projections assume that agents will soon operate alongside human staff in making decisions, taking actions, and managing tasks with minimal oversight. But a growing number of critics (including some of the developers building these systems) argue that the industry still has a long way to go to be able to treat AI agents like fully trusted teammates ...

Enterprise AI has entered a transformational phase where, according to Digitate's recently released survey, Agentic AI and the Future of Enterprise IT, companies are moving beyond traditional automation toward Agentic AI systems designed to reason, adapt, and collaborate alongside human teams ...

The numbers back this urgency up. A recent Zapier survey shows that 92% of enterprises now treat AI as a top priority. Leaders want it, and teams are clamoring for it. But if you look closer at the operations of these companies, you see a different picture. The rollout is slow. The results are often delayed. There's a disconnect between what leaders want and what their technical infrastructure can handle ...

Kyndryl's 2025 Readiness Report revealed that 61% of global business and technology leaders report increasing pressure from boards and regulators to prove AI's ROI. As the technology evolves and expectations continue to rise, leaders are compelled to generate and prove impact before scaling further. This will lead to a decisive turning point in 2026 ...

Cloudflare's disruption illustrates how quickly a single provider's issue cascades into widespread exposure. Many organizations don't fully realize how tightly their systems are coupled to thirdparty services, or how quickly availability and security concerns align when those services falter ... You can't avoid these dependencies, but you can understand them ...

If you work with AI, you know this story. A model performs during testing, looks great in early reviews, works perfectly in production and then slowly loses relevance after operating for a while. Everything on the surface looks perfect — pipelines are running, predictions or recommendations are error-free, data quality checks show green; yet outcomes don't meet the ground reality. This pattern often repeats across enterprise AI programs. Take for example, a mid-sized retail banking and wealth-management firm with heavy investments in AI-powered risk analytics, fraud detection and personalized credit-decisioning systems. The model worked well for a while, but transactions increased, so did false positives by 18% ...

Basic uptime is no longer the gold standard. By 2026, network monitoring must do more than report status, it must explain performance in a hybrid-first world. Networks are no longer just static support systems; they are agile, distributed architectures that sit at the very heart of the customer experience and the business outcomes ... The following five trends represent the new standard for network health, providing a blueprint for teams to move from reactive troubleshooting to a proactive, integrated future ...