Repository navigation
fix: sync model catalog with Pi 1.4 and improve /model discovery - #34
Open
Devendurance wants to merge 1 commit into
Open
Devendurance wants to merge 1 commit into
Devendurance wants to merge 1 commit into
Conversation
Upgrade Earendil Pi SDK ^0.86.1 to ^1.4.0 so Telegram uses the same ModelRuntime and models-store.json as Pi CLI 1.4.0, restoring missing openai-codex and opencode-go models including muse-spark-1.3-contributor. Add /model provider filtering (/model <provider or text>), provider counts matching pi --list-models, and persist selection as Pi default so it survives /new sessions and restarts. Preserve Show all models. Add regression coverage for discovery, auth filtering, provider IDs, switching, and session preservation.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
TelePi
/modelwas showing a stale catalog: the bridge resolved models from an older Pi SDK while Pi CLI 1.4.0 already serves refreshedmodels-store.jsondata (e.g.opencode-go/muse-spark-1.3-contributor,openai-codex/gpt-6*). This syncs Telegram discovery with the installed Pi CLI catalog.@earendil-works/pi-agent-core,pi-ai,pi-coding-agentfrom^0.86.1to^1.4.0(same org, compatibleModelRegistry/ModelRuntimeAPI surface; verified against Pi CLI 1.4.0).listModels()now usesModelRuntime.getAvailable()against the same~/.pi/agent/models-store.json+ auth filtering aspi --list-models(verified parity: 127 authenticated models)./model:/modelshowsProviders: openai-codex (7) • opencode (83) • opencode-go (33) • xai (4)matching CLI counts./model <provider or text>filters (e.g./model opencode-go,/model openai-codex,/model muse-spark).Show all modelspreserved and filter-aware.settingsManager.setDefaultModelAndProvider()so it survives/newsessions and TelePi restarts (best-effort, never breaks in-memory switch).Relation to open PR #33
PR #33 (
chore: upgrade Pi SDK to 1.0.0by @TiaraBasori) does the SDK bump0.86.1 → 1.0.0only (package + lock + pin test). This extends beyond it:^1.4.0to match the currently installed Pi CLI 1.4.0 catalog./modelfix (filtering, provider counts, persistence) and regression tests that chore: upgrade Pi SDK to 1.0.0 #33 does not cover.1.4.0cleanly. No other contributor work touched.Test evidence (actually executed)
npm ci— clean (251 packages).npm run build—tscclean.npm test— 33 files, 455 passed, 1 skipped, 0 failed.npm run test:coverage— Statements 86.76%, Branches 80.71%, Functions 90.33%.listModels(true)= 127,byProvider {openai-codex:7, opencode:83, opencode-go:33, xai:4}matchespi --list-models;muse-spark-1.3-contributorpresent;setModel → newSession retains YES; restart (new service) retains YES.openai 42models exist ingetAll()butopenaiisnot_ready(pi auth check), so correctly absent from available set — no fabricated availability.Disclosure
This work was developed with AI assistance and reviewed/tested by the contributor (@Devendurance), subject to the repository’s disclosure conventions.
Risk / rollback
Docs + SDK + picker only; no systemd unit, config, auth, sessions, or workspace changes. Service restart verified separately in local deploy; this PR does not touch production.