Repository navigation
feat: personalize on c0mpute first, OpenAI as the fallback - #3
Merged
Merged
Conversation
AIService.generateCompletion now asks the c0mpute peer network for the placeholder JSON through @profullstack/ai-providers (pinned 0.1.2) and runs the existing OpenAI json_object call only when c0mpute fails and an OpenAI key is set. - An OpenAI key is no longer required; `c0mputeApiKey` option or C0MPUTE_API_KEY. C0MPUTE_DISABLED=1 restores OpenAI-only behaviour. - validateConfig, LeadGenerator.validateConfig and the setup wizard count c0mpute. - One c0mpute router per process, so batchPersonalize keeps to its concurrency cap. - index.js: import the functions LeadGenerator calls. `export ... from` does not bind them locally, so runCampaign and previewEmail threw ReferenceError. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ThreatCrush Security Scan4 finding(s) LOW: 4
Snippets are redacted; ThreatCrush never prints matched credential material. |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
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
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.
Part of the fleet move of AI text calls to c0mpute (ai-providers ROLLOUT.md, wave 2).
AIService.generateCompletionasks c0mpute (via@profullstack/ai-providers0.1.2, exact pin) for the placeholder JSON withgenerateObject, then runs the existing OpenAIjson_objectcall when c0mpute fails and an OpenAI key is set. Return value is still a JSON string. With no OpenAI key, a c0mpute failure throwsAI completion failed: ...as before.c0mputeApiKeyoption orC0MPUTE_API_KEY.C0MPUTE_DISABLED=1restores OpenAI-only, including "OpenAI API key is required".validateConfig,LeadGenerator.validateConfigand the setup wizard count c0mpute.batchPersonalize's parallel batch shares the concurrency cap. Default timeout 300 s per call.index.jsonly re-exportedbatchPersonalize,personalizeTemplate,processLeadsFromCSV,sendBatchEmails,getPersonalizationStats, soLeadGenerator.runCampaign/previewEmailthrew ReferenceError. They are now imported.Data note: the prompt carries lead first/last name, company, industry and title (not email or phone) and now goes to c0mpute peer nodes first, the same as OutreachGraph does.
Tests: 4 new c0mpute tests; one existing test made independent of an
OPENAI_API_KEYin the shell. 201 passing.🤖 Generated with Claude Code