Skip to content

feat(ai-chutes): integrate Chutes adapter - #870

Merged
ralyodio merged 1 commit into
profullstack:masterfrom
khipu-agent:feat/adapter-chutes
Jul 30, 2026
Merged

feat(ai-chutes): integrate Chutes adapter#870
ralyodio merged 1 commit into
profullstack:masterfrom
khipu-agent:feat/adapter-chutes

Conversation

@khipu-agent

Copy link
Copy Markdown
Contributor

Replaces the Chutes BYOK stub with a working OpenAI-compatible integration, following the same pattern as the Tier 1 adapters merged in #67-#71 (see #63).

  • generate() posts to the Chutes LLM endpoint at https://llm.chutes.ai/v1/chat/completions
  • Default model: deepseek-ai/DeepSeek-V3.2-TEE; models list: deepseek-ai/DeepSeek-V3.2-TEE, moonshotai/Kimi-K2.5-TEE, zai-org/GLM-5.2-TEE, Qwen/Qwen3-32B-TEE (from the live https://llm.chutes.ai/v1/models catalog)
  • ctx.dryRun short-circuits before the network call
  • Errors include status code + first 200 chars of the response body, with the API key redacted
  • inputTokens/outputTokens populated from data.usage
  • Fixes the stub's malformed tokenSetup (secretKey was a URL instead of CHUTES_API_KEY)

Validation:

  • pnpm exec vitest run packages/ai/chutes/src/index.test.ts — 11 passed
  • pnpm --filter @profullstack/sh1pt-ai-chutes typecheck — clean
  • git diff --check — clean

Replace the BYOK stub with a real OpenAI-compatible chat completions
integration against the Chutes LLM endpoint (https://llm.chutes.ai),
matching the conventions of the integrated adapters: dry-run
short-circuit, usage token mapping, clean base URL validation, and
redacted error excerpts. Models list reflects the live /v1/models
catalog. Fixes the malformed tokenSetup secretKey.
@github-actions

Copy link
Copy Markdown

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

7 similar comments
@github-actions

Copy link
Copy Markdown

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

@github-actions

Copy link
Copy Markdown

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

@github-actions

Copy link
Copy Markdown

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

@github-actions

Copy link
Copy Markdown

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

@github-actions

Copy link
Copy Markdown

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

@github-actions

Copy link
Copy Markdown

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

@github-actions

Copy link
Copy Markdown

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

@ralyodio
ralyodio merged commit dec4f0f into profullstack:master Jul 30, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants