Join Dana Lawson, CTO at Netlify, as she explores how to design systems for a true agent experience (AX). Learn how AI agents interact directly with APIs, leverage runtime metadata, and use real-time observability to test, debug, and remediate in production while keeping humans fully informed.
Discover how feedback loops and Zero-UI architecture can transform how agents work with your systems.
Don’t miss out, book your free spot now
How can organizations best balance the desire for increased AI agent autonomy with the critical need for human control and oversight, (especially in scenarios involving high-stakes decisions or potential risks)?
As agents start testing and fixing issues in production, how can QA help define the right balance between automated remediation and human sign-off?
Do you think Zero-UI systems will ever fully replace traditional interfaces, or will both always coexist?
How AI can help to identify hidden bugs in UI which even QA can’t find?
What are the most significant challenges in evolving existing monolithic or legacy architectures into a more modular, agent-centric ecosystem?
How would you design an AI-driven exploratory testing framework that not only discovers unknown defects dynamically but also learns from previous sessions to continuously improve test coverage and risk detection?
How do you test and validate agent workflows before deploying them to production in a Zero-UI setup?
What’s a good strategy to get my risk averse company that is slow to share its code base to transition to bots ?
What new metrics (beyond response time and accuracy) are required to measure user trust in Zero-UI systems?
How can Zero UI principles (voice, gesture, sensors) be architected into applications to deliver seamless user experiences without relying on traditional screens?
How do you validate fairness, bias, and explainability in an agent-driven experience where the reasoning process is hidden?
How can AI-driven testing incorporate business context, such as critical workflows or compliance requirements?
How do you handle security and authorization when agents access APIs directly in a Zero-UI architecture?
How does it relate to the MCPs like Playwright, which focus on UI and less on API?
What unique security risks could ever emerge in zero-UI environments?
In a world without UIs, do you see humans designing for agents instead of agents designing for humans?
Do we need a new testing paradigm (beyond functional, performance, and security) specifically for agent-based experiences?
How does the AX work around the SSO ?
Will there come a time when it’s almost impossible for new QAs to get hired since companies mainly look for experienced testers?
