Rangle

EventsWebinar

The New Part of the Developer's Job: Designing the Moment an Agent Asks for Permission

Personal agents stop and ask a person before they send, pay, sign or delete. Rangle Solutions Architect Abdella Ali on designing that moment: which decisions still need a person, and what to show them.

  • Tuesday, December 15, 2026
  • 12:30–1:30 PM ET
  • Virtual · Live

Save your seat

Reserve your spot for the live session.

What you'll get

  • The full one-hour session, live, with time for your questions.
  • The complete session recording, sent to every registrant.
  • A calendar hold with your join link.

Can't join live? Register anyway. Everyone who signs up gets the recording.

NikeStripeGoogleSanofiStaplesThe North FaceKenvueHims & HersInvescoEndy

Personal agents stop and ask before they send, pay, sign or delete. Someone has to design that moment.

Your doctor, your bank, your clients' customers: everyone else is getting agents too. For now, that approval step is where the person sits. It will move too.

Someone has to design that moment: which decisions still need a person, and what they need to see to make them well. Abdella's view is that we design the loops other people live in, including where a person stays in them on purpose. The same question shows up inside your own delivery loop, where review has become the slowest step.

Abdella Ali is a Solutions Architect with more than a decade at Rangle. This year he has been building agent pipelines for real client delivery work. He first gave this talk at FITC Web Unleashed in Toronto on October 27.

Designing the Moment an Agent Asks for Permission. Rangle webinar with Abdella Ali, Tuesday, December 15, 12:30 to 1:30pm ET

What you'll leave with

  • A clear read on the trend lines. How long agents can work alone today, how fast that's changing, and what it suggests for 2027, clearly labelled as extrapolation.
  • A way to see where your loop waits on people. Checking step by step, task by task, or by outcome, and why review has become the bottleneck.
  • Loops that report to people. Designing architecture reviews, debt audits and security checks that tell the right person exactly what they need to decide.
  • Hard questions for your codebase and Figma file. What replaces the pull request? How do you build a design system agents can't break? What happens to your homepage when the visitor is an agent?

What we'll walk through

  1. Where we've always sat, and how each layer of tooling made each loop do more
  2. Why the loop is tightening, with the data
  3. A real loop: an agent-driven site migration of about 100 pages
  4. Where the loop hits a person
  5. Everyone else gets agents too, and the four actions where they still stop and ask: send, pay, sign, delete
  6. What we bring, one layer up: knowing when it's wrong, deciding where people sit, and keeping the loop tight

Then Q&A.

This session is for you if…

  • You're a developer working out where your own judgement matters most as agents take on more of the building.
  • You're an engineering manager, tech lead or architect whose team already hands real work to agents.
  • You lead design or front-end work and you're wondering what a design system looks like when agents assemble the screens.
  • You feel review becoming the slowest part of delivery and want a better way to decide where people stay in the loop.

Bring your team.