AI Engineer World's Fair 2025

Beyond Conversation: Why Documents Transform Natural Language into Code

Filip Kozera· Founder and CEO, Wordware10:57

Loading slides…

Read the talk

Beyond Conversation: Why Documents Transform Natural Language into Code

Repeatable work needs more than a conversation: it needs a clear assignment, a trigger, and a way for people to review results without supervising every step.

From a talk by Filip Kozera

When one precise edit becomes another conversation

You have been working in Claude or an OpenAI chat, copying material into projects and assembling a workflow by hand. Now you want to change one sentence in an artifact. The conversation keeps growing, but the instructions that matter are increasingly mixed with abandoned ideas and irrelevant exchanges. This is the opening problem Filip Kozera, co-founder and CEO of Wordware, identifies: the conversation is ephemeral, while the work needs a stable specification.

The difficulty is not just remembering what was said. It is deciding what should still count. A long conversation accumulates context without providing a clean way to revise the current assignment. Kozera also wants the system to force clarity: ChatGPT may ask what a deep research request should investigate, yet ordinary interaction does not reliably surface the uncertainties that need an answer before work proceeds.

Several other limitations follow from using the conversation as the working document:

  • Version control and reuse: A useful workflow is hard to preserve, compare, and run again when it lives across exchanges and copied text.
  • Response quality: Kozera reports getting worse responses as his context grows, describing the behavior as model laziness.
  • Organization: Chat offers little support for logical grouping or nesting of an assignment.
  • Abstraction: The interface gives the user one interaction layer, rather than an explicit choice between specifying every small detail and setting a task at a higher level.

Together, these problems make structured iteration difficult even when individual responses are useful.

Slide beside the speaker lists context pollution, lack of structured iteration, no forced clarity, poor version control, limited reusability, model laziness, no hierarchical organization, and a single abstraction level.Open full source frame
Eight limitations of chat-based systems.
0:000:19
Suggest correction

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

0:00 · section reference included

A document makes the assignment explicit

Documents already serve a familiar purpose: explaining a complex system to someone who does not know how to build it. Kozera jokes that Noah’s Ark had the first product requirements document roughly 3,500 years ago, immediately adding, “don't check me on that one.” The useful comparison is the act of specifying a system for another party, not the historical dating.

A document turns an evolving conversation into an explicit assignment. Writing it requires the author to decide what the system should do and communicate that coherently. That is the forced clarity missing from a stream of conversational revisions: another person—or an agent—must be able to understand the intended system from the specification.

2:082:25
Suggest correction

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

2:08 · section reference included

The next limit is the user’s attention

Even a clear conversation can keep the user sitting at the interface. Kozera calls this interaction pattern concurrency of one: work advances through the conversation the person is currently attending to. He points to Manus and deep research as early departures from that pattern, with work continuing after the user steps away. The appeal is that something useful is happening without another prompt.

Computers have, of course, done background work for years. The change is how much judgment a workflow can exercise. Kozera moves from handcrafted automation, exemplified by Zapier, to specialized agents whose contribution might initially resemble a fuzzy if/else making one or two decisions.

ApproachHow work is directedPlace in Kozera’s comparison
Handcrafted workflowExplicitly arranged stepsFrequent, important tasks
Specialized agentA few judgment-based decisionsBounded decision-making
General agentBroader discretionEmerging use, with limits on important work

His task diagram places occurrence on the vertical axis and importance on the horizontal axis. When both are high, organizations have reason to invest in handcrafted workflows. General agents are beginning to make decisions, but Kozera observes that users remain reluctant to admit them into higher-importance work.

TASKS diagram plots occurrence vertically and importance horizontally, with regions labeled specialized, general, and hand-crafted, plus opposing diagonal arrows labeled VALUE and MARKET SIZE.Open full source frame
Tasks mapped by occurrence and importance.
2:523:13
Suggest correction

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

2:52 · section reference included

Let the agent prepare work, then review it

A human in the loop gives an agent room to work without handing it unrestricted control over the outcome. The reviewer can approve or reject the work, change the output, or repair the logic that produced it. Those are different interventions: editing one result resolves the immediate problem, while changing the logic addresses how subsequent work will be done.

The agent can start from explicit or implicit user intent. Sending an email, sending a Slack message, or attending a meeting can provide the activating event. Kozera’s concrete example is a meeting with investors: recognizing the kind of meeting could prompt an update to the CRM. The event supplies the occasion for work; interpreting its meaning supplies the proposed task. A meeting having occurred does not, by itself, establish that a CRM update has been executed.

4:204:42
Suggest correction

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

4:20 · section reference included

From a personal assistant to an organizational network

Multiple ambient agents create a communication problem. People need to control their agents and inspect their outputs, while agents need to exchange information about available data. One agent might ask a more general agent what is in Notion rather than independently acquiring all of that context. Protocols become the means of coordinating those relationships.

The same pattern can expand from an individual’s agents to an organization’s internal and external agents. Even the apparently dramatic idea of agents managing humans has a mundane example: an agent creates Jira tickets for engineers. It is assigning work through an existing organizational interface. These relationships form what Kozera calls the enterprise’s future graph.

His adoption forecast starts with prosumers delegating tasks such as email management to recover time. Enterprise adoption then follows more slowly, because tools must be verified and agents must have the right authority and permissions. The personal convenience of background work becomes an organizational question about who may use which tools, on whose behalf, and with what consequences.

5:075:31
Suggest correction

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

5:07 · section reference included

Accept uncertainty while bounding its consequences

Delegating to probabilistic systems requires a different attitude toward uncertainty. Kozera asks whether business value can justify using a system whose behavior is not fully understood. In Kozera’s hypothetical client-closing example, a system delivers business value 99.9% of the time; the remaining 0.1% must not have catastrophic consequences. The percentages illustrate a risk argument, not measured Wordware reliability: useful outcomes do not remove the need to limit the damage of failures.

Humans remain responsible for their agents’ actions. Managing several agents therefore includes expressing taste, intent, and personal brand in their assignments. An agent acting on someone’s behalf needs more than a task description; its behavior should reflect how that person wants the work done.

Kozera identifies the Model Context Protocol (MCP) as an initial step, while asking for richer communication of agent constraints, delegated authority, and approval requirements. The historical distinction matters: the March 2025 specification already included optional transport authorization, and its tools specification recommended human confirmation and the ability to deny invocations. His broader concern is how to represent and enforce an agent’s organizational mandate, beyond access to a tool connection.

6:436:57
Suggest correction

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

6:43 · section reference included

Coding makes the management skill visible

Coding provides Kozera’s early example of humans managing agents. He sees particular benefit for engineers who combine strong individual-contributor skills with the ability to manage a team of interns. They can both understand the work and direct someone else through it.

An excellent individual contributor may still find AI-generated code disappointing. Kozera suggests that expectations about quality and optimization can make delegation unattractive to someone who would prefer to do the work directly. Extracting organizational benefit from a swarm of agents demands a separate skill: setting assignments, judging results, and managing the work rather than personally producing every detail.

7:598:21
Suggest correction

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

7:59 · section reference included

Put a trusted, repeatable process into the background

Chat still has a role: brainstorming. The transition comes when the exploratory conversation has produced a process worth repeating. Documenting and triggering an agent is for repeatable work, not a requirement for every exchange. Kozera’s progression is straightforward:

  1. Use the conversation to explore what the work should involve.
  2. Write a document explaining the agent’s assignment.
  3. Establish that the process is useful and trustworthy enough to repeat.
  4. Connect it to a trigger so it can start without another conversation.

The trigger might be a cron job, a Gmail event, or an implicit signal of user intent.

For the investor-meeting example, a compact assignment could make the intended work and review boundary explicit:

markdown

# Investor meeting follow-up

When a completed meeting is identified as an investor meeting,
prepare a proposed CRM update from the meeting information.

Keep the proposal concise and factual.
Ask for clarification when the information is insufficient.
Request human approval before applying the update.

The document specifies recurring behavior; the trigger determines when to invoke it. Background execution also changes the interaction budget: latency matters somewhat less when the user is not waiting at the chat window. The agent should surface an issue when it struggles or needs approval.

The person’s work shifts toward writing assignments that express their taste and reviewing the resulting work. As confidence grows, that review becomes the main interaction with a collection of background agents. Kozera’s memorable analogy is Tinder-style swiping left or right: approving, rejecting, or editing results rather than continuously prompting each agent through its task.

8:589:11
Suggest correction

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

8:58 · section reference included

Where enterprise value may accumulate

Kozera closes with a forecast: wider prosumer adoption will precede a gradual move into enterprises, where organizations build tools that the newest models can use. In that future, the durable advantage belongs to the enterprise’s tools—its capacity to let agents perform valuable work—even as the models improve.

He predicts that enterprise tools will be “the moat,” before qualifying the forecast with “Let's see if it's true.” He positions Wordware as enabling these background agents. The proposed destination is a working relationship in which documents define assignments, agents perform recurring work, and people retain responsibility for deciding which results should become actions.

10:1710:40
Suggest correction

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

10:17 · section reference included

Resources

From the talk

Updates since the talk

Transcript download
Full transcript

Loading transcript…