Muse Spark 1.3 and 1.3-contributor are discoverable via the Provider API
but Pi showed "Current model does not support thinking" because the
generated catalog had no reasoning flag or selectable efforts.
Reuse the existing Muse Spark manual override mechanism:
- add reasoning flags and image modalities for both ids to the generated
catalog (CLI 1.40.1 snapshot follows the same pattern as 1.1/1.2)
- add a manual effort override of [minimal, low, medium, high, xhigh]
in src/commandcode-catalog-overrides.ts, merged over the generated
catalog at load time (same set as 1.1/1.2/1.2-contributor, no max)
Pi selected thinking levels now map to reasoning_effort via the
existing generic thinkingMetadataForModel / mappedReasoningEffort path;
no model-specific transport logic is needed.
Tests: typecheck, test-models (override merge + thinking metadata),
test-model-metadata-check, test-pure-functions, test-pricing, test-cost,
test-stream (reasoning_effort mapping), test-runtime, test-transport all pass.
No live Command Code API test was performed.
Co-authored-by: heie54 <14918606+heie54@user.noreply.gitee.com>
Co-authored-by: Patrick Wozniak <email@patwoz.de>
Oh My Pi kept the unresolved $COMMAND_CODE_API_KEY placeholder as a literal config API key that shadowed its /login credential store and was sent as the Bearer token (401). The placeholder is now registered only on pi, where it keeps the API-key auth method and --api-key working next to OAuth; on OMP the provider omits apiKey unless a real key is configured. Host-supplied placeholders are resolved or stripped on every stream path, and the legacy generate transport uses the same rule.
Stored /login OAuth and API-key credentials, --api-key, and env keys are now covered end to end on both pi and Oh My Pi, and CI runs the pi suite against a real binary.
Co-authored-by: ebreen <ebreen@users.noreply.github.com>
PR #69 added efforts for meta/muse-spark-* directly to the generated
catalog, which the drift check flags and the daily sync job reverts.
Keep src/commandcode-catalog.ts byte-identical to upstream and merge a
separate src/commandcode-catalog-overrides.ts over it at load time. A
test fails as soon as upstream publishes efforts for an overridden model
so the override gets removed instead of shadowing the CLI catalog.
Verified against the live endpoint: pi --thinking xhigh sends
reasoning_effort="xhigh" for meta/muse-spark-1.2-contributor and the
request succeeds; --thinking off sends none.
Closes#69
Every host start awaited a full catalog request before the provider
registered, costing one HTTPS round-trip (up to the discovery timeout on a
hanging connection) even when a cache written seconds earlier was on disk.
Register the cached catalog immediately and run the live refresh in the
background; the live result re-registers the provider when it arrives. A
first start without a cache still awaits the live catalog. The background
refresh is aborted on session_shutdown so print mode does not wait for it.
Closes#63
(cherry picked from commit 142191f9420fe90460cdc3cbae70e26d0c000860)
Verify display pricing against the official pricing page and the live
provider model list:
- add claude-fable-5-1 and deepseek/deepseek-v4-flash-fast
- remove minimax/minimax-m3-free and minimax/minimax-m2.7-free, which the
provider no longer lists
- end the claude-sonnet-5 introductory window; the listed rate is unchanged
- google/gemini-3.7-flash returns to list price after the promotion ended
Add claude-fable-5-1, deepseek/deepseek-v4-flash-fast, and
tencent/hy4-preview with their reasoning efforts, add moonshotai/Kimi-K3
efforts, and drop minimax/minimax-m3-free, which the CLI no longer lists.
Maps the three Muse Spark models to [minimal, low, medium, high, xhigh]
so pi-ai can surface graded thinking levels instead of off-only.
These ids are already MODEL_REASONING=true; without MODEL_EFFORTS,
thinkingMetadataForModel() returns an empty map and the footer stays
:off with no cycle via /thinking or Shift+Tab.
Upstream command-code@1.32.2 lists these models as Efforts: — (none);
this commit intentionally adds a pi-side policy mapping aligned with
the opencode/opencode-go provider catalogs (which ship
muse-spark@ minimal..xhigh). The catalog header notes it is normally
generated by sync:commandcode-catalog — happy to move this to a
separate override layer if maintainers prefer.
Add the free minimax/minimax-m3-free and minimax/minimax-m2.7-free
promotional variants (free through September 5, 2026) and
tencent/hy4-preview, drop the retired stealth/ox-alpha, and refresh the
model-id and pricing snapshots to the current 62-model catalog verified
on 2026-08-28.
Qwen/Qwen3.8-Flash lists $0.16 input, $0.47 output, and $0.016 cache read
per million tokens, and z-ai/glm-5.3-flash lists $0.15, $0.50, and $0.03;
the official pricing page documents no cache-write rate for either model.
Synchronize the static model catalog with command-code@1.36.0, which adds
Qwen/Qwen3.8-Flash (reasoning efforts low, medium, xhigh) and
z-ai/glm-5.3-flash (low, high, max), the free minimax/minimax-m3-free
model, and the glm-5.3-flash output limit, and drops the retired
stealth/ox-alpha.
Align the developer-message fix with the Provider API transport router.
The fix stays scoped to the legacy /alpha/generate converter, and the
OMP advisory compat test now forces the upgrade_required fallback so the
advisory is asserted on the generate request body.
deepseek/deepseek-v4-flash-vision-exp is served by the Provider API but was
missing from the hardcoded MODEL_INPUT_MODALITIES allowlist, so pi rejected
any conversation containing an image block. Notably this also rejected images
returned by the read tool via toolResult:
Error: Selected Command Code model does not support image content in tool results
Adding the allowlist entry lets modelSupportsImageInput() return true and the
converters forward images using the current Command Code wire format.
Coverage:
- regression test for modelSupportsImageInput("deepseek/deepseek-v4-flash-vision-exp")
- end-to-end stream test for a tool-result image forwarded as a following user
image (the concrete read reproduction), not only a user-attached image
- end-to-end stream test asserting a text-only model still rejects tool-result
images before any network access
Refs: https://github.com/patlux/pi-commandcode-provider/issues/54
Fetches live account quota from Command Code alpha usage endpoints
(whoami, billing/credits, billing/subscriptions, usage/summary) and
renders a plain-text dashboard via ui.notify.
- Graceful degradation: optional endpoint transport/timeout/parse
failures degrade to null sections instead of aborting; only 401/403
are hard failures. 429 is transient, not fatal.
- Overall deadline bounds the whole command to QUOTA_TIMEOUT_MS
(per-request controllers are chained; post-deadline phases fail fast).
- OMP auth: filter unresolved $COMMANDCODE_API_KEY placeholder and fall
back to the host resolver via pickCommandCodeApiKey.
- ZDR privacy header respected on quota requests.
- Redaction reuses redactCommandCodeErrorText plus JSON-quoted
credential fields; outer-catch errors are redacted too.
- resetAt parsed from seconds, ms, numeric string, or ISO string.
- 21 hermetic unit tests wired into npm test (test:quota).
OMP converts custom and hook messages (advisor notes, todo reminders,
retry nudges) to role "developer" before calling the provider.
messagesToCC() only handled user, assistant, and toolResult, so those
messages were dropped before params.messages was sent to
/alpha/generate. Steering still interrupted pending tools, but the
model never saw the message content.
/alpha/generate has no developer role: the official command-code CLI
(0.32.3) only emits user, assistant, and tool messages plus a separate
params.system. Forward developer messages as user messages with
identical content in the same chronological position. Hoisting them
into params.system would turn a mid-conversation note into a global
top-priority instruction.
Resolve the Command Code model cache through the host's getAgentDir helper so pi, OMP, and PI_CODING_AGENT_DIR use their own agent state directory instead of the official Command Code client directory.
