Skip to content

feat: hide model change markers by default with a Timeline setting (ADR 24) - #90

Merged
supermomonga merged 3 commits into
mainfrom
fix/model-banner-empty-parens-83
Nov 9, 2026
Merged

supermomonga merged 3 commits into
mainfrom
fix/model-banner-empty-parens-83

Conversation

@supermomonga

@supermomonga supermomonga commented Nov 9, 2026 •

Copy link
Copy Markdown
Owner

Problem

The Paseo timeline showed ZCode's model change markers as Model: GLM-5.3-Flash (). The text in parentheses is the marker's reasoning level, and ZCode leaves it empty when the selection has none. The line showed only the target model ID, so a reader could not tell which provider ran the turn or what it changed from. In #83 these lines also piled up on every turn and buried the conversation.

Change

  • Wording. The plugin now words the marker as ZCode Desktop does: Using magpie/GLM-5.3-Flash for a marker with no previous model, and Model switched magpie/GLM-5.3-Flash → magpie/auto/glm-5.3-flash for a switch. It shows provider IDs, because the marker carries no display names. The reasoning level is no longer shown: Desktop omits it too, and ZCode does not count a reasoning level change as a model change.
  • Hidden by default. A new Timeline tab in the plugin's Settings screen has a Show model changes switch, off by default. Whether a marker is shown is decided when the plugin first sees it. Lines already in a timeline stay, and markers that arrived while the switch was off are not added later: Paseo cannot remove items, and a late one would land at the end. A reopened agent replays its history with the current setting.
  • Storage. The switch is a Paseo host settings document (timeline, shared/timeline.ts). The server follows it through the registerSettings() handle. The defaults apply until the first read completes and while the stored document is invalid. The tab can reset an invalid document.
  • Minimum Paseo 0.9.0. Paseo 0.8's registerSettings() returns no handle, so the server could not read the switch there. paseo-plugin.json now requires >=0.9.0. ADR 24 records the decision and amends ADR 8, which had ruled out saving settings.
  • Tests. server/presentation.test.ts covers both marker forms, including an empty reasoning level. test/provider.test.ts checks that the setting applies when a marker is first seen and that a reopened session follows the current setting. Both fail without the change. server/timeline-settings.test.ts covers the defaults, saved values, invalid documents and a save that arrives before the first read. test:upstream now gives its mock context registerSettings and checks that the plugin registers the document.
  • Docs. README (requirements, Setup, a Timeline section), AGENTS.md, development.md and the verification record.

Related issue

Refs #83. This fixes the empty parentheses and hides the lines by default. The lines repeating on every turn did not reproduce locally, and questions are pending on the issue.

Verification (Linux x64, Node.js 26.8.1)

  • Reproduction attempt. With the installed managed runtime (ZCode 3.16.2), a local model fixture and a custom API-key provider with model ID auto/glm-5.3-flash, I ran turns before and after closing and resuming the session twice, with and without a subagent. No model change markers appeared, and every request used auto/glm-5.3-flash with max.
  • Static checks. npm run typecheck, npm test (24 files, 233 tests, after merging fix: report why a ZCode turn failed #91 from main), npm run format:check, npm run build, git diff --check and adrs doctor passed. The only doctor warning was already reported for ADR 1.
  • Upstream. npm run test:upstream against Paseo 0.12.0 (cafe4b01c8522ff39560241c5deb01427dc8dc5b) passed, including the settings registration.
  • Real UI. I installed this worktree into a temporary @getpaseo/cli@0.15.1 daemon (temporary home, loopback, relay and MCP off, web UI and plugins on) and opened Settings → Plugins → zcode-provider → Settings → Timeline in headless Chrome. The switch was off by default. Turning it on saved {"showModelChanges":true} to plugin-settings/zcode-provider/timeline.json, and the value survived a reload.

Screenshots

Timeline tab on the temporary Paseo 0.15.1 daemon, with the default (off) and after turning the switch on.

Timeline tab with Show model changes off (default)
Timeline tab with Show model changes on

Not verified

  • Markers in a real agent's timeline on a real daemon. I did not create a ZCode session there.
  • test:upstream with the real compiler of the new minimum, Paseo 0.9.0.
  • Why the reporter's session alternates between two models on every turn.

Model change markers are hidden unless Show model changes is turned on in
the new Timeline tab. The setting is a Paseo host settings document that the
server follows through registerSettings(), so the minimum Paseo is now 0.9.0
(ADR 23). Whether a marker is shown is decided when it is first seen.
@supermomonga supermomonga changed the title fix: show model changes like ZCode Desktop, without empty reasoning levels feat: hide model change markers by default with a Timeline setting (ADR 23) Nov 9, 2026
Renumber the timeline settings ADR to 24, since main added ADR 23.
@supermomonga supermomonga changed the title feat: hide model change markers by default with a Timeline setting (ADR 23) feat: hide model change markers by default with a Timeline setting (ADR 24) Nov 9, 2026
@supermomonga
supermomonga merged commit 2743013 into main Nov 9, 2026
7 checks passed
@supermomonga
supermomonga deleted the fix/model-banner-empty-parens-83 branch November 9, 2026 03:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant