Skip to content

Haiku is out of scope, and the reason is written down (#1334) - #1633

Merged
suleimansh merged 1 commit into
mainfrom
memory-haiku-out-of-scope
Aug 22, 2026
Merged

Haiku is out of scope, and the reason is written down (#1334)#1633
suleimansh merged 1 commit into
mainfrom
memory-haiku-out-of-scope

Conversation

@suleimansh

Copy link
Copy Markdown
Contributor

Rom's answer on #1334: "Again, let's skip Haiku support for now. (Save this in MEMORY.md with reason why.)"

That answers the question the issue was blocked on. I had offered two options — a model floor on unattended runs, or refusing to arm the merge. Neither is built. Haiku is simply not supported, and the existing warn-never-block from #1439 stays the whole treatment.

One bullet under ## Decisions:

  • Haiku is out of scope. It skips the session-finish protocol, so unattended work started on it always ends as an unmerged draft PR that a human has to finish. We deliberately don't work around this: no model floor that overrides the model a user picked, and no refusal to arm the hand-off. The dashboard's warning is the whole treatment — it teaches and never blocks.

Why memory and not a code comment. StartAgentForm.tsx:207-215 already says Haiku skips the finish step. What the code cannot say is that two workarounds were weighed and rejected — a future session reading only the warning would reasonably propose the floor again. That rationale is exactly what the memory format asks ## Decisions to hold: human-communicated, not inferable from code.

No feature added or removed, so FEATURES-SPEC.md is unchanged.

Rom's call on #1334's last open question: neither a model floor nor a
refusal to arm the hand-off. Haiku simply isn't supported, and the
dashboard's existing warn-never-block (#1439) is the whole treatment.

Recorded in MEMORY.md because it is a decision with a rationale that no
future session can infer from the code — the code only shows a warning,
not that the two workarounds were considered and rejected.
@suleimansh
suleimansh merged commit 7e7a207 into main Aug 22, 2026
2 checks passed
@suleimansh
suleimansh deleted the memory-haiku-out-of-scope branch August 22, 2026 00:12
suleimansh added a commit that referenced this pull request Aug 22, 2026
Rom's call on #1334's last open question: neither a model floor nor a
refusal to arm the hand-off. Haiku simply isn't supported, and the
dashboard's existing warn-never-block (#1439) is the whole treatment.

Recorded in MEMORY.md because it is a decision with a rationale that no
future session can infer from the code — the code only shows a warning,
not that the two workarounds were considered and rejected.
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