fix(activator): add Klavis service triggers to lobe-creds activation rules#14134
Merged
ONLY-yours merged 1 commit intoApr 27, 2026
Merged
Conversation
…rules When users mention Klavis-managed services (Notion, Slack, Google Drive, Airtable, Jira, Figma, etc.), the activator now recognizes these as credential/connection intents and activates lobe-creds automatically. This enables the full Klavis OAuth flow to be triggered inline without requiring the user to manually navigate to settings. Related to lobehub#14090
|
@ONLY-yours is attempting to deploy a commit to the LobeHub OSS Team on Vercel. A member of the Team first needs to authorize it. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## canary #14134 +/- ##
=========================================
Coverage 67.28% 67.28%
=========================================
Files 2157 2157
Lines 185062 185062
Branches 22662 19095 -3567
=========================================
Hits 124522 124522
Misses 60415 60415
Partials 125 125
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
sxueck
pushed a commit
to sxueck/lobehub
that referenced
this pull request
May 27, 2026
…rules (lobehub#14134) When users mention Klavis-managed services (Notion, Slack, Google Drive, Airtable, Jira, Figma, etc.), the activator now recognizes these as credential/connection intents and activates lobe-creds automatically. This enables the full Klavis OAuth flow to be triggered inline without requiring the user to manually navigate to settings. Related to lobehub#14090
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.
Problem
When a user says "help me use Notion" or "connect my Slack", the Agent needs to recognize this as a Klavis service connection intent and activate
lobe-credsto initiate the OAuth flow.Currently, the
<credentials_management>section inlobe-activator/src/systemRole.tsonly lists generic triggers (GitHub, Linear, Twitter, Microsoft) — Klavis-managed services are not mentioned, so the Agent never activateslobe-credsfor them.Change
Added Klavis-managed service names to the trigger conditions and decision flow in
lobe-activator/src/systemRole.ts, so the Agent automatically activateslobe-credswhen users mention services like Notion, Slack, Google Drive, Airtable, Jira, etc.Related
Follows up on #14090 which added the
connectKlavisServiceAPI and Klavis status injection into lobe-creds.