Open
Conversation
…resolve conflicts Made-with: Cursor
17 tasks
- Correct chutes-fast alias to point to a valid model (GLM-4.7-FP8) - Align setChutesApiKey signature with other providers (accept SecretInput) - Use maybeSetResolvedApiKey in non-interactive Chutes onboarding - Fix test mock data to match ChutesModelEntry API shape Made-with: Cursor
…t detections) - Fix Feishu media download/upload type errors by removing redundant timeout parameter (handled by client) - Add 'pragma: allowlist secret' to false-positive test tokens and translations Made-with: Cursor
…/chutesai/openclaw into feat/chutes-provider-integration
Replace complex state-mutation helper with direct applyChutesConfig call after OAuth success, matching the pattern used by the API key flow. This reliably sets the Chutes default model so the model picker shows a Chutes model as current instead of falling back to the previous anthropic default. Made-with: Cursor
The timeout parameter was removed from the source code in a previous commit because it was causing type errors with the SDK, but the tests were not updated. This brings the tests in sync with the source. Made-with: Cursor
Conflict resolutions: - src/secrets/target-registry-pattern.ts: adopt upstream's named-variable style for sibling_ref check; preserve pragma allowlist comment - extensions/feishu/src/media.test.ts: keep upstream's expectMediaTimeoutClientConfigured() and add PR's imageCreateMock assertion for image_type: "message" verification - src/agents/models-config.providers.ts: adopt upstream's refactored provider-loader pattern (SIMPLE/PROFILE_IMPLICIT_PROVIDER_LOADERS); wire Chutes into both API-key (withApiKey) and OAuth profile (withProfilePresence) loader slots using buildChutesProvider from models-config.providers.discovery.ts Supporting changes to integrate Chutes into the new architecture: - src/agents/models-config.providers.discovery.ts: add buildChutesProvider (dynamic model discovery via discoverChutesModels with access token) - src/agents/model-auth-markers.ts: add CHUTES_OAUTH_MARKER and register it in isNonSecretApiKeyMarker Made-with: Cursor
Veightor
force-pushed
the
feat/chutes-provider-integration
branch
from
46b18de to
106db9b
Compare
Made-with: Cursor
…tings) Made-with: Cursor
…/chutesai/openclaw into feat/chutes-provider-integration
…es to new extension system Made-with: Cursor
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
2 participants
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
Describe the problem and fix in 2–5 bullets:
Change Type (select all)
Scope (select all touched areas)
Linked Issue/PR
User-visible / Behavior Changes
List user-visible changes (including defaults/config).
If none, write
None.Security Impact (required)
Yes/No)Yes/No)Yes/No)Yes/No)Yes/No)Yes, explain risk + mitigation:Repro + Verification
Environment
Steps
Expected
Actual
Evidence
Attach at least one:
Human Verification (required)
What you personally verified (not just CI), and how:
Compatibility / Migration
Yes/No)Yes/No)Yes/No)Failure Recovery (if this breaks)
Risks and Mitigations
List only real risks for this PR. Add/remove entries as needed. If none, write
None.