Baseten Integration

Baseten-backed fan-out and HogCode routes

PorkiCoder keeps managed Baseten-backed Kimi and GLM paths for independent worktree fan-out and the bundled HogCode assistant. As of 2.17.1, these models are not in the main Chat, Agent, or OpenCode picker. The former Baseten-backed Consult MCP tools remain retired.

Download PorkiCoder Read model docs

Quick Start

The remaining Baseten-backed paths are already wired into PorkiCoder's managed workflows. Use worktree fan-out when you want isolated Kimi or GLM candidates, or run the read-only HogCode assistant for its managed Kimi K2.7 Code route.

1
Install PorkiCoder
Download PorkiCoder, sign in, and open a project.
2
Choose a workflow
Start a managed worktree fan-out, or launch the bundled HogCode assistant.
3
Choose a model
Choose Kimi K2.7 Code or GLM-5.2 for fan-out. HogCode uses its managed Kimi K2.7 Code route.
4
Review the answer
Compare isolated fan-out candidates or review HogCode's read-only answer in the same workflow.

Baseten-Backed Models

PorkiCoder uses these Baseten-backed models in bounded, separate workflows rather than the main IDE model picker.

Model path Transport Typical use
Kimi K2.7 Code PorkiCoder-managed Baseten route for independent fan-out workers and the bundled HogCode assistant. Isolated implementation or review candidates; read-only project assistance in HogCode.
Kimi K2.6 Legacy native Kimi worker path outside the main Chat, Agent, and OpenCode catalog. Fast model work where a separate managed worker explicitly selects the legacy Kimi key.
GLM-5.2 PorkiCoder-managed Baseten route for independent fan-out workers and judges. GLM reasoning uses Baseten's top-level reasoning_effort field. Large-context candidate reviews, architecture tradeoffs, and fan-out judging.

How PorkiCoder Uses Baseten

  • Independent fan-out workers can still select Kimi and GLM native model keys; the default rotation includes GLM-5.2 and Kimi K2.7 Code.
  • The bundled read-only HogCode assistant uses PorkiCoder's managed Kimi K2.7 Code route.
  • PorkiCoder records usage, applies quota checks on server-backed paths, retries transient Baseten failures, and staggers Baseten-backed fan-out workers to avoid synchronized rate-limit retries.
  • The main Chat, Agent, and OpenCode picker does not expose Kimi or GLM in 2.17.1. Baseten credentials and routes are not injected into or used by the bundled porkicoder-consult MCP server.
Baseten is separate from Consult MCP
PorkiCoder 2.17.0 retired consult_kimi, consult_kimi27, consult_kimi27_fast, and consult_glm52. Consult MCP now provides local subscription workers and separate Kimi K3, Gemini, and GPT API tools. Worktree fan-out remains a different MCP operation with explicit current-conversation paid-model consent.

Example Prompts

These plain-English requests illustrate the remaining Baseten-backed workflows:

  • Run a fan-out with Kimi and GLM candidates, then compare the diffs.
  • Use GLM-5.2 as the fan-out judge and explain the architectural risks in the winning diff.
  • Run HogCode and explain this project using its read-only tools.

Suggested Baseten Listing

If Baseten adds PorkiCoder to its integrations page, this short listing matches the current implementation:

PorkiCoder

Use Baseten-backed Kimi and GLM models in PorkiCoder's independent worktree fan-out and read-only HogCode workflows. PorkiCoder handles authenticated routing, streaming, retries, quota checks, and usage tracking while keeping the main IDE and Consult MCP on separate model paths.

Docs: https://porkicoder.com/integrations/baseten.html

FAQ

Do users need a Baseten account?
Not for the supported PorkiCoder-managed fan-out and HogCode routes. PorkiCoder applies its normal sign-in, consent, quota, and credit checks.
Is this limited to one agent?
No. Multiple isolated fan-out candidates can use Kimi and GLM routes, and HogCode keeps its separate read-only Kimi route. They are not exposed in the main Chat, Agent, OpenCode picker, or Consult MCP catalog.
Where can I read the general docs?
See the worktree fan-out section, the HogCode section, and the separate Consult MCP section for the current consult tool catalog.