@inetafrica/open-claudia 3.4.18 → 3.4.19

package/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## 3.4.19
+
+- Offer `claude-opus-5-5` in the Claude model picker. Verified against the live API rather than assumed: on Claude Code 2.1.280 the API bills the request to `claude-opus-5-5` (1M context, 128k max output), while 2.1.258 refuses it with "does not support this model; version 2.1.280 or newer is required". An older CLI returns that API 400 instead of degrading, so a pod on a stale image errors on the model rather than falling back — the same constraint already recorded for `claude-fable-5-1` (>= 2.1.251).
+
 ## 3.4.18
 
 - Pass images and files from recent Kazee group messages and quoted replies into the model, retaining sender and message attribution. Follow-up questions can reuse attachments after the text catch-up watermark advances.

package/core/providers/claude.js

@@ -6,11 +6,16 @@ const { createJsonlDecoder } = require("./events");
 const { createClaudeParserState, normalizeClaudeEvent } = require("./claude-events");
 const { createClaudeHookTransport } = require("./claude-hook");
 
-// claude-fable-5-1 requires Claude Code >= 2.1.251; older CLIs reject it with an
-// API 400 rather than falling back, so a pod on a stale image will error on it.
+// New models are gated on the CLI build: claude-fable-5-1 requires Claude Code
+// >= 2.1.251, claude-opus-5-5 requires >= 2.1.280. An older CLI rejects them with
+// an API 400 rather than falling back, so a pod on a stale image will error on
+// them. Verified 2026-09-23 on 2.1.280: the API reported claude-opus-5-5 as the
+// serving model (canonicalModel claude-opus-5-5, 1M context), while 2.1.258
+// returned "does not support this model; version 2.1.280 or newer is required".
 const CLAUDE_MODELS = Object.freeze([
   "claude-fable-5-1",
   "claude-fable-5",
+  "claude-opus-5-5",
   "claude-opus-5",
   "claude-opus-4-8",
   "claude-opus-4-7",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@inetafrica/open-claudia",
-  "version": "3.4.18",
+  "version": "3.4.19",
   "description": "An always-on, provider-agnostic coding-agent harness for Claude Code and OpenAI Codex via chat",
   "main": "bot.js",
   "bin": {

package/test-provider-claude.js

@@ -46,6 +46,7 @@ assert.strictEqual(provider.isAvailable(), true);
 assert.strictEqual(provider.executable(), "/fixture/claude");
 assert.strictEqual(provider.defaultModel(), "claude-default-fixture");
 assert.ok(provider.modelChoices().includes("claude-fable-5-1"));
+assert.ok(provider.modelChoices().includes("claude-opus-5-5"), "opus 5.5 is offered in the model picker");
 assert.ok(provider.modelChoices().includes("claude-fable-5"));
 assert.ok(provider.modelChoices().includes("claude-sonnet-4-6"));
 assert.deepStrictEqual(provider.compatibilityStatus(), {

package/test-provider-language.js

@@ -470,7 +470,14 @@ assert.match(pkg.description, /provider-agnostic coding-agent harness/i);
 // 3.4.15: conversation flow and checked sentence speech; authorized calling rollout, 2026-09-05/06.
 // 3.4.17: bind guard judgments and cached verdicts to runtime caller/room identity; approved calling rollout, 2026-09-07.
 // 3.4.18: group-history/quoted attachments; owner approved implement and release, Sept7 18:32 EAT.
-assert.strictEqual(pkg.version, "3.4.18", "release version must remain unchanged without explicit approval");
+// 3.4.19: offer claude-opus-5-5 in the Claude model picker. Sumeet asked
+// 2026-09-23 ("check if opus 5.5 available on Claude code CLI and if yes please
+// add it"), approved the CLI upgrade ("Yes upgrade the CLI please") and left the
+// release shape to me ("Proceed as you see fit"). Shipped alone, ahead of the
+// unreleased Kazee fail-closed room gate, so a runtime behaviour change and an
+// additive picker entry can be rolled back independently. Local Claude Code went
+// 2.1.258 -> 2.1.280 first; the model is refused outright below that.
+assert.strictEqual(pkg.version, "3.4.19", "release version must remain unchanged without explicit approval");
 for (const keyword of ["claude", "codex", "coding-agent", "provider-agnostic"]) {
   assert.ok(pkg.keywords.includes(keyword), `package keyword missing: ${keyword}`);
 }