no. The issue is the way Sahi itself works (you run some JS in the browser). Not even SahiClient.

we could make it easier to handle error by having the Sahi Client request the accessor when creating it, but this would mean making SahiDriver twice slower but doing twice more calls to Sahi. Given that it is already slow as hell, it is not an option IMO.