PicoClaw
PicoClaw’s “list models” command lists only the model already in use
A PicoClaw v0.3.1 report says Telegram /list models renders the current provider and tells users to edit config, even when model_list contains several entries. The output duplicates /show model instead of exposing the configured choices its name promises.
sipeed/picoclaw issue #3294 is the inspected primary source: “/list models only shows the current model instead of all configured models.” Issue #3294 supplies a two-model configuration with model-a selected as the agent default and model-b also present in model_list. Sending /list models through Telegram returns only “Configured Model: model-a,” its provider, and an instruction to update config.json. The expected behavior is either a complete inventory or help text that admits the command is singular. The report also notes that /show model already exposes current state, so the two commands currently collapse onto the same product surface. The source names PicoClaw v0.3.1 at commit 2cf030d and strips sensitive fields from its example.
The facts
- sipeed/picoclaw issue #3294 was created 2026-07-25T19:59:33Z and updated 2026-07-25T19:59:33Z; state is open. - sipeed/picoclaw returned 29720 GitHub stars, 57 open issues, default branch main, and last push 2026-07-23T18:29:33Z. - Latest tagged-release baseline checked: nightly published 2026-07-02T01:26:53Z. - Issue #3294 supplies a two-model configuration with model-a selected as the agent default and model-b also present in model_list. - Sending /list models through Telegram returns only “Configured Model: model-a,” its provider, and an instruction to update config.json. - The expected behavior is either a complete inventory or help text that admits the command is singular. - The report also notes that /show model already exposes current state, so the two commands currently collapse onto the same product surface. - The source names PicoClaw v0.3.1 at commit 2cf030d and strips sensitive fields from its example.
What changed
Issue #3294 supplies a two-model configuration with model-a selected as the agent default and model-b also present in model_list. Sending /list models through Telegram returns only “Configured Model: model-a,” its provider, and an instruction to update config.json. The expected behavior is either a complete inventory or help text that admits the command is singular. The report also notes that /show model already exposes current state, so the two commands currently collapse onto the same product surface. The source names PicoClaw v0.3.1 at commit 2cf030d and strips sensitive fields from its example. The primary record was inspected with its timestamps, state, body, and adjacent project records. ClawCharts supplied the assignment list; it does not establish the claim.
Why it matters
Model inventory is how operators discover available cost, latency, and capability choices without opening a server file. A plural command that reports only effective state hides valid alternatives and makes remote chat administration look less capable than the configuration actually is. Duplicate command semantics also increase the chance that future model-switching work updates one path but not the other. The operational test is whether persisted state, visible control, and runtime behavior agree at the handoff where authority changes.
Current
Issue #3294 was open and created July 25. PicoClaw’s latest stable baseline was v0.3.1; its mutable nightly tag was older than the report. Current pull requests broaden operator tools and repair the chat input surface, but neither is proof that the model inventory command changed. Repository metadata, current issues and pull requests, release baseline, Hacker News discovery, and the rendered ranking row were checked. Weak search residue and historically used source spines were not promoted.
Evidence
The primary URL is https://github.com/sipeed/picoclaw/issues/3294. Supporting links are inspected current project records that establish implementation, adjacent direction, or boundary conditions. Dates, reproductions, test totals, and deployment observations remain attributed to their authors unless this brief explicitly says they were independently rerun.
Source boundary
Open work is described as open, merged work as merged, and operator reports as reports. A closed issue or passing branch test is not silently translated into a released fix. Ranking explains why the project was scanned; it does not prove correctness, adoption, or package behavior.
Operator take
Configure two harmless test models, call both /list models and /show model, and compare output with parsed configuration. Keep current-state display and inventory as separate contracts, with explicit provider names and no secret material. Preserve a before-state receipt and verify the narrowest invariant where state changes. Do not broaden permissions or delete state merely because the visible symptom is inconvenient.
Caveat
Public project records are mutable. Source state was captured at publication time, and later revisions may change status, scope, or evidence. No source here authorizes automatic mutation of a reader’s deployment.
Source inspected; source state, environment, and release boundary remain explicit.