Skip to content

test(models): Haiku 5.5 reads as Haiku 5.5 and takes effort levels - #218

Merged
httpsphl merged 1 commit into
mainfrom
feat/haiku-5-5
Oct 7, 2026
Merged

httpsphl merged 1 commit into
mainfrom
feat/haiku-5-5

Conversation

@httpsphl

@httpsphl httpsphl commented Oct 7, 2026

Copy link
Copy Markdown
Owner

What

Haiku 5.5 (claude-haiku-5-5) works in Botloft already, and this pins it with tests and fixes the spec.

Botloft sends Claude Code's own alias (--model haiku), which Claude Code points at Haiku 5.5 from version 2.1.293 on (before that, at Haiku 4.5). The app reads the model id, the effort levels and the context window from what Claude Code reports, so nothing in the code changes.

  • modelName("claude-haiku-5-5") reads "Haiku 5.5" (test).
  • A bot on Haiku 5.5 gets the effort slider and its recommended level (test). Haiku 4.5 keeps "no effort levels", from what Claude Code reports.
  • Spec: the window was written as 200k for Haiku, now 1M for Haiku 5.5 and 200k for 4.5; the section 19 effort row says what the docs say about Haiku 5.5.

Checked

  • pnpm vitest on the two test files, biome and tsc pass.
  • The facts come from the official docs (models overview and Claude Code model-config, 2026-10-07).

Manual step

Not tried with a real Haiku 5.5 yet: it needs Claude Code >= 2.1.293 (the machine here has 2.1.287). With it, a bot on Haiku should report claude-haiku-5-5 in system/init and the five effort levels. The spec says "not seen with the real Claude Code" until then.

The haiku alias points to claude-haiku-5-5 from Claude Code 2.1.293 on, with
the five effort levels and a 1M window. The app already reads levels and
window from what Claude Code reports, so no code changes; this pins it with
tests and fixes the spec (the window was said to be 200k for Haiku).
@httpsphl
httpsphl enabled auto-merge October 7, 2026 20:17
@httpsphl
httpsphl merged commit 03d00f9 into main Oct 7, 2026
4 checks passed
@httpsphl httpsphl mentioned this pull request Oct 7, 2026
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