To avoid failure, launch AI agents with high human control and low agency, such as suggesting actions to an operator. As the agent proves reliable and you collect performance data, you can gradually increase its autonomy. This phased approach minimizes risk and builds user trust.

For CISOs adopting agentic AI, the most practical first step is to frame it as an insider risk problem. This involves assigning agents persistent identities (like Slack or email accounts) and applying rigorous access control and privilege management, similar to onboarding a human employee.

Traditional identity models like SAML and OAuth are insufficient for agents. Agent access must be hyper-ephemeral and contextual, granted dynamically based on a specific task. Instead of static roles, agents need temporary permissions to access specific resources only for the duration of an approved task.

To overcome employee fear, don't deploy a fully autonomous AI agent on day one. Instead, introduce it as a hybrid assistant within existing tools like Slack. Start with it asking questions, then suggesting actions, and only transition to full automation after the team trusts it and sees its value.

Frame AI agent development like training an intern. Initially, they need clear instructions, access to tools, and your specific systems. They won't be perfect at first, but with iterative feedback and training ('progress over perfection'), they can evolve to handle complex tasks autonomously.

Current AI workflows are not fully autonomous and require significant human oversight, meaning immediate efficiency gains are limited. By framing these systems as "interns" that need to be "babysat" and trained, organizations can set realistic expectations and gradually build the user trust necessary for future autonomy.

The most effective AI user experiences are skeuomorphic, emulating real-world human interactions. Design an AI onboarding process like you would hire a personal assistant: start with small tasks, verify their work to build trust, and then grant more autonomy and context over time.

The CEO of WorkOS describes AI agents as 'crazy hyperactive interns' that can access all systems and wreak havoc at machine speed. This makes agent-specific security—focusing on authentication, permissions, and safeguards against prompt injection—a massive and urgent challenge for the industry.

AI agents can cause damage if compromised via prompt injection. The best security practice is to never grant access to primary, high-stakes accounts (e.g., your main Twitter or financial accounts). Instead, create dedicated, sandboxed accounts for the agent and slowly introduce new permissions as you build trust and safety features improve.