v0.6.1

Every agent host — and the whole registry on the wall

v0.6.1 is a patch: no API change, no new host. It corrects what the project says it is, removes the star curation that was hiding real hosts, and fixes two paths that 0.6.0's Mux → Xum rename left pointing at a home Xum no longer uses.

The promise covers every agent host, not every agent CLI

The target is the whole class of config-owning surfaces — terminal CLIs, IDE extensions and desktop apps alike — so "agent CLI" understated the scope. "Host" is also the noun the three specs we implement all use: MCP, Agent Plugins and Agent Skills say client, never "harness".

Focus on the implementation, not the distribution. The catchphrase now leads the README, and PROJECT_MEMORY.md records it as the framing everything else serves: you stay in your MCP server and never hand-maintain a per-host integration, package format, or install path.

0.6.0 shipped this to the site but not to the files agents read. llms.txt, llms-full.txt and skills/agent-connector/SKILL.md are updated — and one line there had been saying something untrue about our own code:

…reads each agent CLI's own session logs…

The connector-free usage track's reader set includes cursor.ts (a Cursor IDE reader), zed.ts (a desktop SQLite thread store), plus Kiro, Trae, Warp and Antigravity. It reads hosts, and always grouped by platformId. Corrected throughout, per-CLI / per-model included.

Public coverage now equals the registry: 42 hosts (was 35)

Every star floor is gone. Stars measure repo popularity, never product reach, and they misrank in both directions at once: a first-party agent whose public repo is an issues tracker is under-reported, and a closed host has no count at all — VS Code Copilot's feedback repo sits near 1k against Warp's 65k.

Once both of those were conceded, the last floor standing had inverted:

host	stars	under the old rule
Junie (JetBrains)	422	listed, by vendor exemption
Amazon Q (AWS)	1,985	listed, by vendor exemption
Xum	2,000	hidden
Grok CLI	3,449	hidden
Kiro (AWS)	4,251	listed, by vendor exemption

isPublicCoverageHost now keeps one clause: an archived upstream never renders. The wall still shows star counts, it just does not gate on them.

Breadth is a goal, not a side effect. Comparing this many hosts side by side is how the shared patterns get found — the three hook paradigms, the AGENTS.md convergence, Agent Plugins as a common bundle. Each host is a data point in that survey.

A host whose upstream has ENDED is removed outright, not hidden — as roo-code was in 0.6.0. Leaving a dead host half-supported is the confusing outcome, so the archived check is only a safety net for the window before the adapter is cut.

Two star floors have now been tried and both withdrawn, so the drift test was inverted to match: it asserts every non-archived host is public. A third attempt has to break a test rather than a page.

Fixed: two paths missed by the Mux → Xum rename

0.6.0 moved the config home .mux → .xum and routed the adapter's own paths through xumHome(). Two call sites outside the adapter were not updated:

• src/adapters/base.ts pinned Xum's user-scope memory target to ~/.mux/AGENTS.md, so a fresh Xum install wrote its managed block into a home Xum never reads. It now resolves the way the adapter does — prefer .xum, keep an existing .mux, default new installs to .xum — with all three cases pinned by new tests.
• src/usage/paths.ts offered ~/.mux/sessions alone, so a machine on the new home reported no Xum usage at all. Both roots are offered now; the reader is fail-open and takes whichever exists.

Neither could strand a current user — the legacy home stays readable in both.

Fixed: a .gitignore typo

The entry read .omg/, a directory that has never existed, under a comment naming OMC orchestration. .omc/state/, .omc/project-memory.json and site/.omc/ were therefore untracked and unignored — one git add -A from being committed. It now ignores the contents rather than the directory, so the tracked .omc/RELEASE_RULE.md and the committable .omc/skills/ exception survive (git cannot re-include a path whose parent directory is excluded).

Verified

• Roster confirmed against the live star snapshot: registry 42, public 42, hostLifecycle holding only gemini-cli=sunsetting
• Full suite: 147 files, 3484 tests passing, 1 skipped (3 new); root and site typechecks clean
• npm pack → ken-jo-agent-connector-0.6.1.tgz, 269 files; site build 43 pages

Full changelog: see CHANGELOG.md — 0.6.1.