Reported issues for kiaaccess-mcp

Pod holds 9 of 9 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to kiaaccess-mcp.

Most discussed

Auto-review follow-ups for PR #40: feat(session): accept a bootstrapped rmtoken via KIA_RMTOKEN

Tracking auto-review follow-ups for #40 (verdict: warn).

🟡 Nits

• forgetSession() sets cachedRmToken=null while loadRmToken() only re-reads KIA_RMTOKEN/session store when the cache is undefined, so kia_forget_session permanently hides a still-valid KIA_RMTOKEN env var until process restart (src/client.ts:437)

When addressing the review on #40, resolve each item and add Closes #<this issue> to the PR once everything is genuinely fixed; defe

Read the thread · 2026-08-10 · closed · external user · 0 comments

Auto-review follow-ups for PR #23: fix(client): recover a rotated vinkey and accept a quoted temperature

Tracking auto-review follow-ups for #23 (verdict: fail).

🔴 Important

• src/client.ts:558 — KiaClient.dispatch applies the cached vinkey remap to the header only, so cmm/gvi's body keeps the dead key on every call after the first recovery in a session; apply opts.bodyForVinKey on the initial send when currentVinKey changed the key

🟡 Nits

• tests/commands.test.ts:334 — the 'advertises the string form' schema assertions (toContain('string')

Read the thread · 2026-07-28 · closed · external user · 1 comment

Auto-review follow-ups for PR #21: fix(connector): keep the code box revealed when OTP verification fails

Tracking auto-review follow-ups for #21 (verdict: warn).

🔴 Important

• src/kia-auth.ts ~L358-363: err instanceof Error ? err : new Error(String(err)) and if (!failure.revealFields) in the new outer catch block appear unreachable given current call sites (every throw in that try already produces an Error without revealFields set), and are not exercised by any test — risks failing the vitest.config.ts-enforced 100% branch-coverage threshold unl

Read the thread · 2026-07-28 · closed · external user · 1 comment

Auto-review follow-ups for PR #17: feat(connector): hide the code box until Kia has actually sent a code

Tracking auto-review follow-ups for #17 (verdict: warn).

🟡 Nits

• docs/DEPLOY-CONNECTOR.md still describes the Texted code field as visible-but-empty on first load; now stale since the field is hidden/disabled until step 1's rejection reveals it

When addressing the review on #17, resolve each item and add Closes #<this issue> to the PR once everything is genuinely fixed; deferred items stay open here. See the auto-review follow-up conventi

Read the thread · 2026-07-28 · closed · external user · 0 comments

Auto-review follow-ups for PR #10: feat(connector): complete Kia's MFA in the login page, not by hand

Tracking auto-review follow-ups for #10 (verdict: warn).

🟡 Nits

• src/kia-auth.ts module header (lines 4-13), KiaProps.rmtoken (line 47), and hostedDeviceId's note (lines 66-70) still describe the removed paste flow (local stdio bootstrap, kia_export_refresh_token, "trusting the paste") and contradict the updated login() docblock and docs/DEPLOY-CONNECTOR.md
• tests/worker.test.ts:93 asserts expect(html).toMatch(/code/i), which would pass e

Read the thread · 2026-07-28 · closed · external user · 0 comments

Auto-review follow-ups for PR #8: chore(main): release 0.2.0

Tracking auto-review follow-ups for #8 (verdict: fail).

🔴 Important

• CHANGELOG.md references non-reachable commits 0fff3c8 and 8956e6d for two features that aren't in the v0.1.0..HEAD history; only the kiaaccess-curl skill commit (8c62dd0) is actually included in this release

When addressing the review on #8, resolve each item and add Closes #<this issue> to the PR once everything is genuinely fixed; deferred items stay open here. See the

Read the thread · 2026-07-28 · closed · external user · 1 comment

Auto-review follow-ups for PR #5: feat(charging): verify evc commands against a real vehicle

Tracking auto-review follow-ups for #5 (verdict: warn).

🟡 Nits

• tests/index.test.ts:62 comment still calls the charging commands "(unverified)", stale after this PR verified them

When addressing the review on #5, resolve each item and add Closes #<this issue> to the PR once everything is genuinely fixed; deferred items stay open here. See the auto-review follow-up convention in CLAUDE.md.

Read the thread · 2026-07-28 · closed · external user · 0 comments

Auto-review follow-ups for PR #2: feat(skills): add kiaaccess-curl shell-out skill

Tracking auto-review follow-ups for #2 (verdict: fail).

🔴 Important

• evc/* verification-status claim in skills/kiaaccess-curl/SKILL.md and references/requests.md contradicts docs/KIA-API.md, which is still not updated and lists evc/charge, evc/cancel, evc/sts as unverified

When addressing the review on #2, resolve each item and add Closes #<this issue> to the PR once everything is genuinely fixed; deferred items stay open here. See the aut

Read the thread · 2026-07-28 · closed · external user · 1 comment

Most recent

Auto-review follow-ups for PR #34: refactor(connector): retire the standalone Cloudflare Worker connector

Tracking auto-review follow-ups for #34 (verdict: warn).

🟡 Nits

• src/tools/session.ts:107-108 still explains the registerSessionStatusTool split as existing "because the hosted Cloudflare connector registers THIS" while lines 3/30/306/332 of the same file were genericised — the only remaining caller is line 153 in that same file
• src/client.ts:11 and :346-348 still justify the pure-constructor rule with "the module singleton is built in Wor

Read the thread · 2026-08-06 · closed · external user · 0 comments

The remaining reports are on the project's issue tracker.