Profile, Auth, and Backend Runtime Selection

Profile, Auth, and Backend Runtime Selection A workflow diagram generated by Archify. 01 / Authentication source 02 / Backend preference 03 / Web graph EX / Android graph Construct Resolve Install and open Build Client · constructor · Backend preference › Construct Build Client constructor Load Stored Auth · path · env · profile · Authentication source › Resolve Load Stored Auth path · env · profile Select Backend · arg · env · Web · Backend preference › Resolve Select Backend arg · env · Web Web Graph · WebRuntime · WebRawAPI · Web graph › Install and open · default Web Graph WebRuntime · WebRawAPI default Android Graph · runtime · raw APIs · Android graph › Install and open · opt-in Android Graph runtime · raw APIs opt-in web cookie jar android Legend Agent logic Policy External system

Authentication precedence

  • • Path > NOTEBOOKLM_AUTH_JSON > active profile
  • • Web owns cookie I/O; Android assembles ProfileStore, MintService, and bearer state

Backend-selected graph

  • • Explicit backend > NOTEBOOKLM_BACKEND > Web
  • • client.raw follows the backend; Android account lookup returns self._auth.account_email without I/O

Android boundary

  • • Android construction performs no credential I/O; BearerProvider first reads at open
  • • Root _client_compat.py pre-registers LazyWebSidecar; deprecated rpc_call materializes it on demand