This repository was archived by the owner on Jun 11, 2026. It is now read-only.
Make credential resolution explicit and testable#91
Merged
patosullivan merged 3 commits intoMay 26, 2026
Merged
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f743124ed9
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
arthyn
approved these changes
May 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR extracts credential/config resolution into explicit, injectable resolver and credential-flag layers, then updates
ensureClient()to honor resolver-owned auth/cache policy instead of implicitly falling back to cached cookies.The goal is to make auth behavior deterministic and testable without touching a developer's real env, home directory, cache, OpenClaw config, or a live ship.
What Changed
scripts/credential-resolver.tswith explicit resolution metadata:--shipplusTLON_SKILL_DIRscripts/credential-flags.tsfor top-level credential flag parsing and validation.scripts/api-client.tssoensureClient()consumes resolver metadata before reading/writing auth cache..yamlresolution/docs behavior.scripts/main.ts,README.md, andSKILL.mdto document the implemented credential forms, resolution order, and cache-write policy.Policy Decisions
--config <file>--url <url> --cookie <cookie>with optional--shipand optional fallback--code--url <url> --ship <ship> --code <code>--ship <ship>forTLON_SKILL_DIRor targeted cache lookup~/.clawdbot/moltbot.json~/.moltbot/moltbot.jsonTests
Validated locally: