Repository navigation
docs(guides): reach LM Studio and OpenRouter through OpenCode or Pi - #19384
Conversation
A step-by-step guide for running chats on LM Studio (local) or OpenRouter models through the OpenCode and Pi harnesses Kiro Crew already drives: installing and selecting the harness, each harness's own provider entry and sign-in (taken from the OpenCode, Pi and LM Studio docs), picking the model in the composer, and where the provider credentials live. Kiro Crew holds no provider key for this setup. Part of #11568 Related to #10088
UX Review (Opus 5.5) — ✅ PASSUX-level review of UX-Verdict: PASS Nothing to check. [UX-REVIEWED] 333e3e1 Description read[DESCRIPTION-READ] f9b03540f97e82ca5d062e6921aaf99318b55d793d8078342545c923f4b20070 That sha256 names everything this verdict read: the PR description, plus the 3 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
First Principles Review (Opus 5.5) — ✅ PASSPremise-level review of First-Principles-Verdict: PASS The supplied patch also contains the MembersPage, crew-mode spec and RFC hunks from #19346, which is already on base (c4c51aa); check that the PR's own commits touch only the guide. What this change shipsInventory (2 items) — 2 justifiedIntent: a user can run chats on LM Studio or OpenRouter models by following one guide that uses the OpenCode or Pi harness. This is an ADDITION (docs only).
Searching [FIRST-PRINCIPLES-REVIEWED] 333e3e1 Description read[DESCRIPTION-READ] 9191902f8fd73c7d8f49309b06156e2b0f2c0ed1a8dd4a3c3e6dc827e8030660 That sha256 names the PR description this verdict read. Recompute it with |
Design Review (Opus 5.5) — ✅ PASSDesign-level review of Design-Verdict: PASS Nothing to check. [DESIGN-REVIEWED] 333e3e1 Description read[DESCRIPTION-READ] 99ec21977dfe36fb791fb91fb0882c3b97ea06eba19c5cfcc67e4dee4cf3a30f That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
Opus 5.5 Review — ✅ no blocking findingsReviewed Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
GPT 6.1 Review — ✅ no blocking findingsGPT 6.1 completed its review of This comment is updated in place on each push. Review detailsFINDING -- website/src/pages/members/MembersPage.tsx:3465 -- False positive or not applicable? A repository writer can comment: |
Add pi --list-models as Pi's terminal check, say that OpenCode lists the openrouter provider only after a key is stored, and cover its 'Provider not found' answer in the troubleshooting table. Part of #11568
|
Re the Design Review note (a human should run the OpenCode LM Studio path end to end): I ran the harness side of the guide against real binaries, in throwaway config and data directories with no real credentials.
Not covered here: a live LM Studio server, a real OpenRouter key, and a Kiro Crew chat driven end to end. The PR description's Manual verification section says the same. |
|
Re the First Principles note on 333e3e1: the PR's own commits (51abab8, 333e3e1) touch only |
iamwhatever
left a comment
There was a problem hiding this comment.
This is a docs-only guide for running chats on LM Studio or OpenRouter models through the OpenCode or Pi harness, plus one index row. I checked its Kiro Crew claims against the code on this head. The install commands match backends.py (npm i -g opencode-ai) and PI_INSTALL_COMMAND in acp/harness/pi.py. OpenCode is in ACP_BACKENDS_MEMBER_DISPATCH and Pi is not, which matches the member DM note. The "OpenCode is not signed in" / "Pi is not signed in" messages and the credential paths (.local/share/opencode/auth.json, .pi/agent/auth.json) match host_auth.py. The guide adds no product code or credential handling, and it says plainly what was not run end to end. Lanes are PASS and checks are green. — crew-pr-reviewer (deep re-check)
Problem / Motivation
Goal: A user can run Kiro Crew chats on LM Studio (local) or OpenRouter models by following one guide, using the OpenCode or Pi harness Kiro Crew already drives.
There is no Kiro Crew documentation for reaching LM Studio or OpenRouter. Both harnesses already speak to these providers from their own configuration, but nothing tells a user which harness to pick, which harness file to edit, how each harness signs in, or how the chosen model shows up in the composer.
Why it matters
Users asking for local or OpenRouter models currently have no supported path written down, so they reach for forks or direct adapters. The harness route needs no new trust posture: the provider keys stay in each harness's own credential file and Kiro Crew holds none.
Not a goal
What changed (motivation → approach → change)
docs/guides/lm-studio-and-openrouter.md: install and select the harness (Settings, Agent Harness, oragent.acp_backend), the member DM backend note, LM Studio server start and model id check, the OpenCodeopencode.jsonprovider entry and the Pimodels.jsonentry for LM Studio, OpenRouter sign-in throughopencode auth loginand Pi's/login openrouter, picking the model in the composer, where the credentials live, and a troubleshooting table.docs/guides/README.md: index row for the new guide.pi --list-models, OpenCode's "Provider not found" answer before an OpenRouter key is stored), added after running the harnesses.Rejected alternatives:
Backwards compatibility
Compatible: documentation only; no code, config or schema changes.
Removes nothing: the diff adds one guide and one index row.
Tests
N/A: documentation only.
scripts/docs_lint.py --testandscripts/docs_lint.pypass locally (every internal link resolves, the new guide is indexed). The external links in the guide were checked to answer HTTP 200.Manual verification
opencode.json,opencode models lmstudiolistslmstudio/google/gemma-3n-e4bandopencode debug configresolves"model": "lmstudio/google/gemma-3n-e4b".opencode models openrouteranswers "Provider not found: openrouter" until a credential is stored, and listsopenrouter/...ids onceauth.jsonholds an OpenRouter entry.models.json,pi --list-models gemmalists providerlmstudio, modelgoogle/gemma-3n-e4b; with theapiKeyline removed the model is not listed.Related Issues
Part of #11568
Related to #10088 (the picker, owned by its assignee)
Checklist
feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)Contribution License Agreement
Contributed under the project's Apache-2.0 license.