feat(connectors): implement push logic for syncing connectors

[Paveltarno]

Note

Description

This PR implements the push synchronization logic for OAuth connectors in the Base44 CLI, enabling the base44 connectors push command. The implementation handles creating/updating connectors, removing upstream-only connectors, and managing OAuth authorization flows with browser redirect and polling. It includes comprehensive error handling for conflict scenarios like different-user connections.

Related Issue

None

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)
• Other (please describe):

Changes Made

Core Logic:

• Added push.ts module with pushConnectors() function that syncs local connector configs to the API
• Implemented sync logic that compares local connectors with upstream and performs create/update/delete operations
• Added oauth.ts module with runOAuthFlow() function for handling browser-based OAuth authorization with polling
• Created ConnectorSyncResult interface to track sync outcomes (synced, removed, needs_oauth, error)

API Updates:

• Renamed syncConnector() to setConnector() and updated endpoint from POST to PUT
• Updated response schema from SyncConnectorResponse to SetConnectorResponse
• Enhanced error handling for different_user conflicts
• Added OAuth status polling via getOAuthStatus()

CLI Command:

• Created new connectors push command under src/cli/commands/connectors/
• Interactive OAuth flow with user confirmation prompt (skips in CI environments)
• Comprehensive summary display showing synced, added, removed, and failed connectors
• Graceful error handling for individual connector operations

Project Integration:

• Updated ProjectData interface to include connectors: ConnectorResource[]
• Added connectorsDir field to project config schema (defaults to "connectors")
• Integrated connector reading into readProjectConfig() function
• Removed filename validation logic (no longer requires filename to match type)

Testing:

• Added comprehensive CLI tests (connectors_push.spec.ts) covering success cases, errors, OAuth flows, and conflict detection
• Added core unit tests (connectors.spec.ts) for pushConnectors() and runOAuthFlow() functions
• Added API mock methods in testkit for connector endpoints (list, set, remove, OAuth status)
• Removed obsolete connector-type-mismatch fixture

Testing

• I have tested these changes locally
• I have added/updated tests as needed
• All tests pass (npm test)

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (if applicable)
• My changes generate no new warnings
• I have updated AGENTS.md if I made architectural changes

Additional Notes

The implementation follows the Resource pattern established for entities, functions, and agents. The push logic handles three main scenarios: syncing local connectors to the API, removing upstream connectors not present locally, and managing OAuth authorization flows when needed. Error handling ensures graceful degradation when individual operations fail.

Key implementation details:

• OAuth flow automatically opens browser and polls for authorization completion
• In CI environments (detected via process.env.CI), OAuth prompt is skipped
• Removed the strict filename-to-type validation that was previously enforced
• Changed API endpoint from POST /external-auth/sync to PUT /external-auth/integrations/{type}

---

_{🤖 Generated by Claude | 2026-02-08 06:21 UTC}

[github-actions]

🚀 Package Preview Available!

---

Install this PR's preview build with npm:

npm i @base44-preview/cli@0.0.28-pr.191.545b03a

Prefer not to change any import paths? Install using npm alias so your code still imports base44:

npm i "base44@npm:@base44-preview/cli@0.0.28-pr.191.545b03a"

Or add it to your package.json dependencies:

{
  "dependencies": {
    "base44": "npm:@base44-preview/cli@0.0.28-pr.191.545b03a"
  }
}

• 📦 Preview Package: @base44-preview/cli@0.0.28-pr.191.545b03a
• 🔗 View this commit on GitHub

---

_{Preview published to npm registry — try new features instantly!}

[claude]

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

[Paveltarno]

@claude rebase with pavelta-connectors-1 branch

[claude]

Claude finished @Paveltarno's task in 23s —— View job

---

Task: Rebase with pavelta-connectors-1 branch

• Analyze request
• Execute git operations

Analysis

I understand you want to rebase the pavelta-connectors-push-logic branch with pavelta-connectors-1. However, I need to clarify a limitation:

I cannot perform interactive rebase operations due to the complexity and potential need for conflict resolution that requires human decision-making.

Alternative Approaches

I can offer two alternatives:

1. Merge approach: I can merge the latest changes from pavelta-connectors-1 into this branch

   • Command: git merge origin/pavelta-connectors-1
   • Creates a merge commit
   • Safer and automated

2. Manual rebase instructions: I can provide you with the exact commands to rebase manually

   git fetch origin
   git rebase origin/pavelta-connectors-1
   # Resolve any conflicts if they occur
   git push --force-with-lease origin pavelta-connectors-push-logic

Would you like me to:

• A) Proceed with merging pavelta-connectors-1 into this branch (automated)
• B) Provide detailed manual rebase instructions

Please let me know which approach you prefer, or if you'd like me to attempt something else.

---

[Paveltarno]

@claude rebase against branch pavelta-connectors-1

[claude]

Claude finished @Paveltarno's task in 37s —— View job

---

Task: Rebase against branch pavelta-connectors-1

• Analyze request and check capabilities
• Execute rebase operation

Analysis

I understand you want to rebase pavelta-connectors-push-logic against pavelta-connectors-1. However, I've encountered a limitation:

I cannot perform interactive git operations like rebase. According to my capabilities, I can only create and push commits, but cannot perform branch operations such as rebase or merge.

Additionally, I noticed that the pavelta-connectors-1 branch is not currently available in my local checkout. I would need to fetch it first, but even if I could fetch it, I cannot execute the rebase operation.

How to Rebase Manually

Here are the exact commands you can run to perform this rebase:

# Ensure you're on the correct branch
git checkout pavelta-connectors-push-logic

# Fetch the latest changes from the base branch
git fetch origin pavelta-connectors-1

# Rebase your branch onto pavelta-connectors-1
git rebase origin/pavelta-connectors-1

# If there are conflicts, resolve them, then:
# git add <resolved-files>
# git rebase --continue

# Once rebase is complete, force push (with lease for safety)
git push --force-with-lease origin pavelta-connectors-push-logic

Alternative: Merge Instead

If you'd prefer to avoid rebasing, I could perform a merge operation by creating a merge commit. This would:

• Preserve the exact history of both branches
• Not require force pushing
• Be a simpler operation that I can perform

Would you like me to merge pavelta-connectors-1 into this branch instead?

---