AI Engineer Europe 2026

Your agent is blindfolded

Johan Lajili· Member of Engineering, Full-Stack, Poolside9:58

Loading slides…

Read the talk

Your agent is blindfolded

Coding agents need a way to see failures, operate the application, and verify repairs. Johan Lajili shows how application-specific tooling makes that feedback loop possible.

From a talk by Johan Lajili

Why does AI coding work for one developer and fail for another?

How can one developer stop touching code while another gets unusable changes in a production application? Johan Lajili, an engineer at Poolside, opens with this split in experience. Poolside builds its own foundation models and coding agents, but the problem is familiar across tools: one developer celebrates having AI do everything; another asks whether those successes amount to little more than to-do apps.

It is easy to dismiss the enthusiast as selling AI or the skeptic as someone who never really tried it. A more useful explanation distinguishes greenfield projects from brownfield applications: starting fresh seems easier than changing a system with years of accumulated decisions. Yet Lajili has used AI successfully in legacy applications. The age of the codebase alone does not explain the difference.

Two stacked Reddit posts contrast letting Cursor and Claude do the coding with reports of hallucinated imports and broken services.Open full source frame
Two contrasting accounts of using AI coding tools.
0:160:31
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

0:16 · section reference included

Plausible code needs feedback

In a new application, an agent's expectations often fit the environment it is creating. Put a component here, add a service there, and the resulting structure may work as expected. An existing application contains surprises: a promising code path may no longer be used, or behavior may depend on another part of the repository the agent has not inspected.

EnvironmentWhat the agent can miss
GreenfieldWhether its newly created structure actually behaves as expected
BrownfieldDead code, hidden dependencies, and existing behavior outside its inspection

The distinction makes the feedback loop decisive. Intuition can suggest an implementation, but observations must establish whether that implementation works in this application.

When an agent announces that a new workflow works perfectly, its confidence is bounded by the capabilities and information it received. It may have verified the result; it may only have produced something that looks correct. A user who discovers a failure can supply logs and ask for another attempt, keeping the loop moving. Another user may conclude that the tool cannot be trusted and stop. The engineering opportunity is to let the agent obtain that corrective evidence itself.

1:542:12
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

1:54 · section reference included

Give the agent access to the application

At Poolside, Lajili built an internal CLI called Spoolside to let agents test the application. Its inspection capabilities include screenshots and snapshots: compact representations of what is on a page that an agent can consume without the full page content. He compares these capabilities with gstack.

Poolside's application is a VS Code extension, so ordinary webpage access is not enough. Spoolside supplies the additional access machinery that lets the agent interact with the extension much as it would with a webpage. It then extends that access across the running system:

  • Service evidence: Extract logs from frontend and backend services.
  • Service control: Restart services when needed.
  • Navigation: Open a particular menu or go to a particular page.
  • Conversation workflows: Send a message, wait for the agent's reply, send a follow-up, and upload an image.

These higher-level operations can be composed into a workflow. The agent gets both a way to act and a way to observe what happened.

Slide titled “Our CLI at Poolside: Spoolside” lists snapshots, screenshots, component interaction, DOM tracing, service restarts, logs, and high-level commands.Open full source frame
Spoolside’s CLI tools for inspecting and operating the application.
3:443:59
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

3:44 · section reference included

Reproduce the failure before proposing the fix

Application access changes where debugging starts. An eager agent may immediately suggest adding a margin or inserting some code. Lajili wants it to reproduce the bug before editing. That establishes that the agent can reach the failing state and recognize the problem it is trying to solve.

An intuitive fix might still be right. But if the agent cannot inspect the result, a human must verify it. That burden limits how much work can be delegated and makes unattended overnight runs difficult to trust. Reproduction is a first step toward that trust, not evidence that overnight autonomy has already been achieved. Spoolside itself is not offered as a reusable GitHub project; the recommendation is to build equivalent access for your own application.

4:575:10
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

4:57 · section reference included

Make verification part of the working environment

This shifts some engineering effort from directly building the product to making the product easier for an agent to work on. Better tools are one part of that investment. A more navigable codebase and better knowledge bases also help the agent understand what to change and how to check it. The interface can be a CLI, a skill, or an MCP integration. Lajili chose a CLI for simplicity; the appropriate form depends on the application and the problem.

More output is useful only if errors do not compound with it. Lajili contrasts the product engineer of 2025 with a proposed role he calls the AIX engineer: someone who makes it possible for AI to build the product reliably. That includes making verification easy and presenting the agent's work so a human can review it.

An arrow connects a 2025 Product Engineer box to a 2026 aiX Engineer box, above a line about building the product and making sure AI can build it.Open full source frame
From 2025 Product Engineer to 2026 aiX Engineer.

His analogy is the airline oxygen-mask instruction: equip the AI to help itself before asking it to work on more features. Building that capability may slow immediate feature delivery, but he expects the investment to pay off as more agents use the environment over longer periods.

5:486:02
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

5:48 · section reference included

Where do exploratory checks meet committed tests?

The audience asks where mechanical primitives such as screenshots and logs end and checked-in unit or integration tests begin. Should these checks be temporary, or should they become tests that always run?

Lajili describes his checks as fairly ephemeral and explicitly treats that as a personal preference. He sometimes finds automated tests too rigid and difficult to maintain, and favors tooling that lets the agent explore an application as a human tester would.

Consider a button that is visibly too far to the left. The immediate temptation is to tell the agent exactly what is wrong. Instead, Lajili steps back and asks what would let the agent discover the misplacement itself. The missing capability may be more consequential than the individual correction: once the agent can observe this class of problem, it needs less human intervention on subsequent tasks.

7:397:48
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

7:39 · section reference included

Find missing commands in the agent's logs

After several rounds of work, inspect the interaction history. Lajili suggests asking an AI to review past logs for recurring issues and repeated actions. Repeated sleep(50) calls are a useful signal: the agent may be compensating for a missing command that waits for a particular condition. Repeatedly starting Storybook can similarly reveal a workflow worth packaging into a reusable operation.

The useful abstraction is a named readiness condition with a bounded wait. For example, this TypeScript helper lets an application-specific probe decide when an operation can continue:

typescript

async function waitFor(
  description: string,
  isReady: () => Promise<boolean>,
  timeoutMs = 10_000,
): Promise<void> {
  const deadline = Date.now() + timeoutMs;

  while (Date.now() < deadline) {
    if (await isReady()) return;
    await new Promise<void>((resolve) => setTimeout(resolve, 100));
  }

  throw new Error(`Timed out waiting for ${description}`);
}

The short polling delay controls how often the probe runs; it does not decide whether the application is ready. A reply-wait command, for example, should proceed when the reply is available rather than after an arbitrary pause. This illustrates the missing-command pattern, without assuming a particular Spoolside API.

8:539:03
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

8:53 · section reference included

Choose an interface that fits the product

The right observation surface depends on what you are building. For a Unity game, Lajili proposes considering an ASCII representation of the 3D world: a representation the agent can inspect as it reasons about the environment. For an application with extensive permissions, it may need easy access to different logins so it can experience the product under different roles.

Those choices remain an engineering responsibility. A screenshot, a world representation, and a role-specific session expose different kinds of evidence. Build the access that lets the agent discover the failures your product can actually have.

9:169:30
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

9:16 · section reference included

Resources

From the talk

Transcript download
Full transcript

Loading transcript…