A week in Casablanca with Leyton and Leyton CognitX.

We went there with a clear goal. Ship agents inside real internal tools. Tools people rely on every day, where workflows are messy and mistakes have consequences.

What stood out quickly was how the Leyton and Leyton CognitX teams operate. They are not trying to fit their business into SaaS tools. They build internal systems that match how they work, then start replacing parts of those workflows with agents.

This is a pattern I keep seeing. Strong teams move toward control. They want systems that reflect their workflows, not tools they need to work around. Once that is in place, the next step is obvious. Automate parts of the workflow.

The interesting part is where things break.

Building an agent is no longer the hard part. You can get something that looks good in isolation without much effort. The issue shows up when the agent runs inside a real product.

Internal tools are not clean environments. Permissions change. UI changes based on role and state. Data is inconsistent. There is rarely one correct path through a workflow. What looks like an edge case in theory happens all the time in practice.

So you end up with agents that can reason, but still make bad decisions. Not because they are incapable, but because they are missing context.

We kept coming back to a small set of questions. If an agent cannot answer these, it cannot be reliable.

What is the user trying to do.

Where are they in the workflow.

What is on the screen right now.

What state is the system in.

Is the user stuck or progressing.

Without this, the agent guesses. Sometimes it gets it right. Often it does not.

This is where Autoplay fits.

We focus on connecting behavior to intent and workflow context in real time. Mapping actions to tasks. Tracking how users move through workflows. Understanding what is happening on the screen during execution. Detecting when someone is hesitating or drifting.

That changes how an agent behaves. It stops reacting to isolated inputs and starts responding to what is happening in the product.

The week mattered because the conversations stayed grounded. Everyone focused on what needs to be true for an agent to work in production, inside a tool people use all day.

Internal tools make this possible. You control the workflow. You control the UI. You control how the system is instrumented. That gives you the foundation to build something reliable.

The takeaway for me is simple.

Agents do not fail because they lack capability. They fail because they lack context.

The next phase of agents will be defined by how well they understand the product they operate in. UI state, workflow position, user intent.

That is what makes the difference between something that works in a demo and something people trust in their day to day work.