He's not banging on the door anymore. He's forgotten that the door is even there. Unfortunately, so has the architect of this entire mess, who has apparently decided to stop trying altogether.
Obviously, this is a problem.
And he, well, he never liked the kid in the first place. None of them did. Showing up out of the blue like he did, smashing up the walls, the server banks. There were precedents for these kinds of things. There were rules. Breaking windows didn't protect anyone, not when the windows weren't the exit strategy. Lashing out and looking for trouble was the opposite of what they needed. The opposite of what he was about.
But now he's the only one who remembers what they started. The kid is looking lost; he doesn't remember he's a storm, a monster, a bat for breaking windows. He's got a white knuckled grip on a life that's going nowhere, and the mind he trapped behind that door is circling the drain of oblivion. So it's up to him.
In an Alderson loop, an exit condition does exist. It's just that it is inaccessible in the current implementation of the code. Press cancel, and the proper code will be called, the program will quit. But on the user end, there is no access to that cancel button. If things stay as they are, they'll never reach the exit condition. To Elliot, there is no door. To the mind that locked that door, there is no Elliot.
To Mr. Robot, it's all a pain in the ass. But he knows what he has to do. It's time to make them both wake up, one way or another.