Repository navigation
v0.14.3 — Fail-postpone mode
Fail-postpone mode (new, opt-in)
A third quota-block failure mode alongside fail-closed/fail-open: manually
and temporarily bypass an otherwise-legitimate block when you've decided to
accept the risk of running over quota for a while.
- New
allowPostponeconfig flag (--allow-postpone,OPENCODE_QUOTA_ALLOW_POSTPONE), disabled by default. - New CLI:
opencode-hard-limit postpone [minutes](default 30, clamped 1-240) andopencode-hard-limit postpone --clear. - Runs entirely via OpenCode's native shell-escape (
!command) — no LLM call, no token cost. - When enabled, a block's error message and the sidebar widget both surface a hint on how to postpone.
opencode-hard-limit getshows whether a postpone is currently active and how much time is left.
Fixes
- Sidebar widget crashed entirely on OpenCode restart because the deploy step
didn't shiplib/postpone.jsalongside the sidebar plugin — fixed. - Simplified the quota-block error message; removed AI-directed instruction
text that had no effect (a blocked subagent'schat.paramsthrow happens
before any model text is generated, so OpenCode'stasktool has nothing
to relay to the parent — documented as a known upstream limitation in the
README instead of working around it with unreliable message text). - Clarified that OpenCode's shell mode only triggers when
!is the first
character typed into an empty prompt — pasting the whole
!opencode-hard-limit postpone 30line at once does not switch modes.
The block message, sidebar hint, and README now instruct: type!first,
then paste justopencode-hard-limit postpone 30(without the!).
Docs
- New README "Fail-postpone mode" section: how to enable, the shell-escape
mechanism, the type-then-paste caveat, and the subagent limitation.
Full diff: v0.12.2...v0.14.3