🎉 v0.3.1 — badge immediacy, test harness, and our first community merges

[engrtarun]

Shipped today, with the community's fingerprints all over it:

What changed in v0.3.1

• 🏃 Immediate model-switch badges (PR fix: update active badges when a session switches model #13 by @Golden007-prog) — when a running session switches model, its badge moves the moment the event lands. No more ~8s window where ● sat on the old row. A revision guard also stops an in-flight session-list response from restoring a stale mapping.
• 🧪 A dependency-free npm test (PR test: cover badge logic and prevent duplicate session counts #5's idea by @xmejl) — 20 node:test cases now cover badge stripping, badge selection, running/retry counting, and the real plugin's model-switch behavior. CI (Node 22 + 24) runs them on every push/PR — green badge on the README.
• 🏷 README badge row, repo topics, and this Discussions space.

Install in 30 seconds

New-Item -ItemType Directory -Force -Path "$env:USERPROFILE\.config\opencode\plugins\model-badges" | Out-Null
Copy-Item index.ts, lib.ts, package.json "$env:USERPROFILE\.config\opencode\plugins\model-badges\"

…then touch opencode.jsonc (or restart OpenCode) and watch the picker.

Credits

Contributor	What
@xmejl	double-count reproduction + suffix regex bug (PR #5)
@Golden007-prog	immediate model-switch badge updates + revision guard (PR #13)

Next stop: the roadmap discussion — tell us what v0.4 should be. 🗺

[engrtarun]

Update - v0.4.0 released

OpenCode v2.2.0 moved the execution-state events off the wire (session.status / session.idle are v1-only now), so Model Badges now speaks both vocabularies:

• v2 model switch (session.model.selected) moves a badge instantly - same as v1's session.model.updated`n- v2 rate-limit back-off (session.retry.scheduled) paints 🔄 with the provider's own resume epoch feeding the ❌ window
• replayed durable frames can no longer resurrect a ghost ? after a reconnect
• 24-test suite, zero child processes - still

Grab it from the repo README (or the v0.4.0 release notes).

[engrtarun]

🛰️ v0.4.2 — AutoBG: sessions move THEMSELVES to background

New in v0.4.2 (release: https://github.com/engrtarun/opencode-model-badges/releases/tag/v0.4.2):

A session whose tool call (bash / scripts / MCP) keeps the foreground blocked longer than 2 minutes now moves itself to background — exactly the Ctrl+B operation, exactly when you would have wanted to press it.

• T-30s: one toast — AutoBG: 30s — "bash" moves to background automatically
• T=0: one toast — AutoBG: moved to background (ran 2m01s) — and your tool keeps running in background (backgrounding never kills tools; that's the engine's own contract)
• Tools-only scope: a model thinking/writing for 10 minutes is never touched — only open tool calls count
• Guards: subagent children (parentID) and unmapped sessions never fire; one shot per session turn; 10-minute zombie cap for missed end events
• Note on toasts: some OpenCode builds dropped the client toast route — the background move still happens; the countdown falls back to debug.log (autobg fire … lines)

Update (4 files now):

# Windows — from the repo folder
Copy-Item index.ts, lib.ts, autobg.ts, package.json "$env:USERPROFILE\.config\opencode\plugins\model-badges\"

# macOS / Linux
cp index.ts lib.ts autobg.ts package.json ~/.config/opencode/plugins/model-badges/

…then restart OpenCode. Upgrading from ≤0.4.1: the new file autobg.ts is required.

Suite: 33 tests green on node 22 + node 24 (fail-fast: false in CI so both versions always report).

[engrtarun]

🛰️ v0.4.3 — AutoBG fires at 1 minute + cross-process fire lock

Real-machine findings from live debug logs drove this one (https://github.com/engrtarun/opencode-model-badges/releases/tag/v0.4.3):

• Threshold 2 min → 1 min. Real long runs (downloads/builds/curl) live 3-6 min; 2 minutes was too patient.
• Warn checkpoint now at T-15s (fires at 45s elapsed): AutoBG: 15s — "bash" moves to background automatically
• Cross-process fire lock. Live evidence: several OpenCode processes share one event stream, and each was firing its own background POST (autobg fire x3 in the log). Now an NTFS-atomic wx lock file means exactly one process moves the session; the rest log autobg lock held … another process fired first.
• Why you never saw the countdown toast: the live debug log showed toast unavailable — this build's client dropped the toast route. The plugin now dumps autobg client keys: into debug.log once so where the toast lives (or that it doesn't) is always provable, and the move happens regardless.
• autobg skip unmapped — the [investigation] Do subagent sessions inflate running counts? #12 guard (subagent children) is now visible in debug.log instead of silently swallowing.

Update: copy the same 4 files (index.ts, lib.ts, autobg.ts, package.json) → restart OpenCode. 35 tests, node 22 + node 24 green.