A remote's own expired token hides a good stored login issue #155 closed: completed andymccall opened this 7 days ago · 0 comments

Found 2026-10-28 overnight: every checkout's remote.earth.token (Andy's personal tokens) expired, so oxy push earth and oxy pull earth answer 401: this token has expired, although the agent home's stored login for the same hub (credentials.toml, oxy auth status: valid) would be accepted. Repo::remote_options takes the remote's own token first and fill_credentials keeps fallbacks only from enclosing checkouts (issue #112), never from the credential store, so an expired remote token cannot be got past without editing the checkout's config.

Worked around by pushing from a fresh clone with no stored token (/mnt/development/wox, oxygen c04f9f51).

Expected: when the remote's own token is refused as unknown or expired, try the stored login for that hub (and enclosing checkouts' tokens) before failing, and say which token was refused and which one worked, suggesting oxy config --unset remote.NAME.token to drop the stale one.