docs: add Poolside provider page

[amypoolside]

Issue

No linked issue — this is a standalone documentation contribution adding Poolside provider guidance.

Context

Kilo Code supports Poolside models through Kilo Gateway, Poolside Platform, and OpenRouter, but the provider documentation did not explain these access paths.

This adds setup instructions for VS Code and the CLI, including authentication, model selection, direct Poolside Platform configuration, and reasoning variants.

Implementation

The page is organized by access path so readers can choose based on authentication and billing before following client-specific steps.

The Poolside Platform example sets the published context window so Kilo can manage conversation compaction. It omits limit.output because Poolside does not publish a maximum output length and Kilo applies its documented fallback.

Screenshots / Video

N/A — documentation-only change.

How to Test

Manual/local verification

• npx --yes prettier@3.6.2 --check packages/kilo-docs/lib/nav/ai-providers.ts packages/kilo-docs/pages/ai-providers/index.md packages/kilo-docs/pages/ai-providers/poolside.md
  • Passed.
• git diff --check
  • Passed.
• Confirmed all Markdoc tab tags are balanced.
• Parsed both JSONC examples successfully.
• Confirmed internal routes resolve and all referenced external URLs return HTTP 200.
• Verified current Poolside model availability on Kilo Gateway and OpenRouter.

Reviewer test steps

1. Run bun run --filter @kilocode/kilo-docs dev.
2. Open http://localhost:3002/docs/ai-providers/poolside.
3. Confirm the Kilo Gateway, Poolside Platform, and OpenRouter sections render correctly.
4. Switch between the VS Code and CLI tabs in each section.
5. Confirm the configuration examples and links render correctly.

Blocked checks and substitute verification

• bun run --filter @kilocode/kilo-docs test could not run because Bun is not installed locally.
• bun run --filter @kilocode/kilo-docs build could not run for the same reason.
• Substitute verification consisted of pinned Prettier, whitespace, Markdoc structure, JSONC parsing, route, external-link, source-code, and source-document checks.

Checklist

• Issue linked above, or exception explained
• Tests/verification described
• Screenshots/video included for visual changes, or marked N/A
• Changeset considered; not needed for a docs-only change
• I personally reviewed the diff and can explain the changes, including any AI-assisted work.

[vercel]

@amypoolside is attempting to deploy a commit to the Kilo Code Team on Vercel.

A member of the Team first needs to authorize it.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Incremental review of commit 0b9ffe39 (rebase onto current main plus a meta-description update). The only PR-owned change since the last review is the poolside.md meta description, which adopts the previously suggested wording and now sits within the 120–160 character guideline. The xAI → SpaceXAI and tencent/hy3:free edits in models-and-providers.md came from main via the rebase, not from this PR, and are out of review scope.

Previous findings are resolved: the Gateway free-model-ID warning was confirmed by the author against the live api.kilo.ai/api/gateway/models response (laguna-s-2.1:free and laguna-xs-2.1:free are current; the older IDs are no longer served), and the meta-description suggestion was applied verbatim. No images or code were introduced, so the image-format and memory-leak checks are not applicable.

Files Reviewed (2 files)

• packages/kilo-docs/pages/ai-providers/poolside.md
• packages/kilo-docs/pages/gateway/models-and-providers.md

Previous Review Summaries (2 snapshots, latest commit 0aaa5cc)

Current summary above is authoritative. Previous snapshots are kept for context only.

Previous review (commit 0aaa5cc)

Status: 2 Issues Found | Recommendation: Address before merge

Incremental review of commit 0aaa5cc0cf (docs rewrite of the Poolside page to the built-in provider + /connect flow, and updated free-model list). The previous reviewer request to use /connect in the CLI tab is addressed by the new commit. Verified against the codebase: the auth.json credential store, the Show more providers entry point in the VS Code Providers tab (same pattern as the xAI provider page), and all internal links (/docs/gateway, /docs/gateway/authentication, /docs/getting-started/setup-authentication). One correctness concern on the Gateway free-model IDs, one minor SEO nit on the meta description. No images or code introduced, so the image-format and memory-leak checks are not applicable.

Overview

Severity	Count
CRITICAL	0
WARNING	1
SUGGESTION	1

Issue Details (click to expand)

WARNING

File	Line	Issue
packages/kilo-docs/pages/gateway/models-and-providers.md	64	New free model IDs (laguna-s-2.1:free, laguna-xs-2.1:free) don't match the in-repo Gateway catalog snapshot (laguna-m.1:free, laguna-xs.2:free); confirm against the live Gateway

SUGGESTION

File	Line	Issue
packages/kilo-docs/pages/ai-providers/poolside.md	3	Meta description ~113 chars, below the 120–160 guideline

Files Reviewed (2 files)

• packages/kilo-docs/pages/ai-providers/poolside.md - 1 issue
• packages/kilo-docs/pages/gateway/models-and-providers.md - 1 issue

Fix these issues in Kilo Cloud

Previous review (commit c38f350)

Status: No Issues Found | Recommendation: Merge

Docs-only PR adding a Poolside provider page. Verified the technical claims against the codebase: Ctrl+T variant cycling, May train label, /connect and /models commands, VS Code custom provider dialog field labels (Provider ID / Display name / Provider API / Base URL / Submit), the ThinkingSelector next to the model picker, kilo.jsonc naming, the settings#managing-settings anchor, and the provider/model ID format with a slash-containing model key (parseModel joins the remainder, so poolside-platform/poolside/laguna-s-2.1 resolves correctly). The sitemap is auto-generated from lib/nav, so the nav addition covers indexing. No images introduced, so the image-format rule is not applicable. No code changes, so the memory-leak check is not applicable.

Files Reviewed (3 files)

• packages/kilo-docs/lib/nav/ai-providers.ts
• packages/kilo-docs/pages/ai-providers/index.md
• packages/kilo-docs/pages/ai-providers/poolside.md

---

_{Reviewed by kimi-k3 · Input: 176.1K · Output: 4.2K · Cached: 224.3K}

_{Review guidance: REVIEW.md from base branch main}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs (docs-staging)	Ready	Preview	Aug 6, 2026 2:54pm

[lambertjosh]

Hi - can you please recommend using /connect, which follows a similar workflow to what is shown in VSCode? That is much nicer than the manual config method.

[amypoolside]

Updated - the CLI tab now uses /connect to select Poolside and enter the API key, matching the VS Code flow. Removed the manual config. Pushed in 0aaa5cc.

[lambertjosh]

Thanks, merging!