fix: restore login-once auth flow via leadbay_login tool#2
Merged
Conversation
The OpenClaw plugin API adaptation (5e94ab5) silently removed the username/password login flow and replaced it with manual API token configuration — a concept that doesn't exist in Leadbay. Restore the login flow by registering a leadbay_login tool that accepts email + password, authenticates via POST /auth/login, and stores the bearer token in-memory. No credentials are persisted. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
leadbay_logintool that accepts email + password, authenticates viaPOST /auth/login, and stores the bearer token in-memory — no credentials persistedTest plan
npm run buildcompiles cleanlyleadbay_loginwith credentials → subsequent API calls work🤖 Generated with Claude Code