customable/claude-mem
1
0
Fork 0
Code Issues 1 Pull requests 5 Projects Releases 163 Packages 2 Wiki Activity Actions

feat(worker): implement agent provider registry pattern (#171) #222

Merged
jack merged 3 commits from feat/171-agent-registry into main 2026-01-24 19:20:37 +00:00
Conversation 0 Commits 3 Files changed 4 +180 -74
jack commented 2026-01-24 17:45:41 +00:00
Owner
Copy link

Summary

  • Add AgentProviderDefinition interface for provider metadata (name, displayName, envKey, priority)
  • Replace hardcoded switch statement with dynamic provider registry
  • Add registerProvider/unregisterProvider/getAvailableProviders functions
  • Support configurable fallback order via AI_PROVIDER_FALLBACK setting
  • Built-in providers registered with priority (mistral=20, anthropic=10)
  • Maintain backwards compatibility with registerAgent (deprecated)

New Settings

  • AI_PROVIDER_FALLBACK: Array of provider names for custom fallback order

Example Usage

// Register custom provider
registerProvider({
  name: 'ollama',
  displayName: 'Ollama Local',
  envKey: 'OLLAMA_BASE_URL',
  isAvailable: () => !!process.env.OLLAMA_BASE_URL,
  create: () => new OllamaAgent(),
  priority: 5,
});

// Get available providers sorted by priority
const providers = getAvailableProviders();

Test plan

  • Verify default agent selection works with priority-based fallback
  • Test custom AI_PROVIDER_FALLBACK setting
  • Verify registerProvider adds new provider to registry
  • Check backwards compatibility with registerAgent

Closes #171

🤖 Generated with Claude Code

## Summary - Add `AgentProviderDefinition` interface for provider metadata (name, displayName, envKey, priority) - Replace hardcoded switch statement with dynamic provider registry - Add `registerProvider`/`unregisterProvider`/`getAvailableProviders` functions - Support configurable fallback order via `AI_PROVIDER_FALLBACK` setting - Built-in providers registered with priority (mistral=20, anthropic=10) - Maintain backwards compatibility with `registerAgent` (deprecated) ## New Settings - `AI_PROVIDER_FALLBACK`: Array of provider names for custom fallback order ## Example Usage ```typescript // Register custom provider registerProvider({ name: 'ollama', displayName: 'Ollama Local', envKey: 'OLLAMA_BASE_URL', isAvailable: () => !!process.env.OLLAMA_BASE_URL, create: () => new OllamaAgent(), priority: 5, }); // Get available providers sorted by priority const providers = getAvailableProviders(); ``` ## Test plan - [ ] Verify default agent selection works with priority-based fallback - [ ] Test custom AI_PROVIDER_FALLBACK setting - [ ] Verify registerProvider adds new provider to registry - [ ] Check backwards compatibility with registerAgent Closes #171 🤖 Generated with [Claude Code](https://claude.com/claude-code)
feat(worker): implement agent provider registry pattern (#171)
All checks were successful
CI / build (pull_request) Successful in 46s
Details
3ede87ff69 
- Add AgentProviderDefinition interface for provider metadata
- Replace hardcoded switch with dynamic provider registry
- Add registerProvider/unregisterProvider/getAvailableProviders functions
- Support configurable fallback order via AI_PROVIDER_FALLBACK setting
- Built-in providers registered with priority (mistral=20, anthropic=10)
- Maintain backwards compatibility with registerAgent (deprecated)

New settings:
- AI_PROVIDER_FALLBACK: array of provider names for custom fallback order

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Merge branch 'main' into feat/171-agent-registry
All checks were successful
CI / build (pull_request) Successful in 42s
Details
2296bafdec 
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Merge branch 'main' into feat/171-agent-registry
All checks were successful
CI / build (pull_request) Successful in 40s
Details
94fadae3c5
jack merged commit 78a230c0d0 into main 2026-01-24 19:20:37 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
good first issue

Good for newcomers

  
has-pr

Issue has an associated pull request

  
help wanted

Community contributions welcome

  
idea

Idea or concept - not yet ready for implementation

  
priority
critical
Urgent issue requiring immediate attention

  
priority
high
High priority issue

  
priority
low
Low priority issue

  
priority
medium
Medium priority issue

  
status
blocked
Blocked by external dependency

  
status
in-progress
Currently being worked on

  
status
needs-review
Awaiting code review

  
status
ready
Ready to be worked on

  
type
bug
Something isn't working

  
type
docs
Documentation improvements

  
type
enhancement
Improvement to existing functionality

  
type
feature
New feature or request

  
type
refactor
Code refactoring without functional changes

No labels
good first issue
has-pr
help wanted
idea
priority
critical
priority
high
priority
low
priority
medium
status
blocked
status
in-progress
status
needs-review
status
ready
type
bug
type
docs
type
enhancement
type
feature
type
refactor
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
customable/claude-mem!222
No description provided.