Update the status within the client could it be fine or is it horrible?

[albertcito]

const StartApp = () => {
  const { setUser, ...props } = useUser();
  const client = useRef(createClient({
    url: `${constants.urlServer}/graphql/public`,
    fetchOptions: () => {
      const token = localStorage.getItem('accessToken');
      return {
        headers: { authorization: token ? `Bearer ${token}` : '' },
        withCredentials: true,
      };
    },
    exchanges: [
      dedupExchange,
      cacheExchange,
      retryExchange({
        retryIf: (error) => {
          if (error.response.status === 403) { setUser(); }
          return false;
        },
      }),
      fetchExchange,
    ],
  })).current;
  return (
    <UserContext.Provider value={{ ...props, setUser }}>
      <Provider value={client}>
        <GlobalStatus />
      </Provider>
    </UserContext.Provider>
  );
};

[kitten]

Depending on how you're using the credentials this will be completely fine. This obviously can't quite be a complete example but there's some assymmetry between your authorisation management in useUser and the token being retrieved from local storage.

If you already have a singleton that manages the user or a context object, you could instead investigate using the authorisation exchange instead: https://formidable.com/open-source/urql/docs/advanced/authentication/