Skip to content

rightsize 0.14.0

Latest

Choose a tag to compare

@archid21 archid21 released this 15 Nov 08:04
v0.14.0
edba5df

Cache and compacts

  • Keep warm only while it pays. The default of Before the cache goes cold is now "while it pays" (it was keeping warm until your usual start). rightsize records every idle break, whether you came back before the cache expired, after it, or not at all. At each point a keep-warm request is due, it sends one only when your own chance of coming back before the next expiry covers its cost, at most 2 per break; until it has enough breaks on record it sends one request at the first expiry on a 1-hour cache and none on a 5-minute cache. With no request due it compacts when that pays, else saves a whatsnext handoff note. On a 1-hour cache the band shows the countdown with an Extend 1 hour button. If the rule's own runs cost more than they saved, it pauses itself and says so. A value you set in /config still behaves as before.
  • Keep warm stops on a cache miss. After each keep-warm request, rightsize checks that it read the conversation from the cache. If it read under 80%, the cache missed: keep warm ends, says why in the log, and sends no more requests.
  • Wrap up, and the handoff text for every bare compact. A /compact with nothing after it, and Claude Code's automatic compact, now use rightsize's handoff text; text you type after /compact, whatsnext's text and another plugin's are never replaced. The text comes from a PreCompact hook, so it also works where Claude Code keeps plugin modules away from compaction (Team and Enterprise logins); it needs python3. On the countdown row of keep warm while it pays, a Wrap up button ends keep warm and saves a whatsnext handoff note, or compacts when whatsnext is not set up in the project. Typing wrap up in a project where whatsnext is not set up now compacts too, instead of sending those words to the model. When rightsize compacts where a note would have done, a hint says so: to install whatsnext (at most once in 30 days; Don't show again in the ⋯ menu hides it for good), or to run whatsnext init (once per project). On its first start rightsize also turns your earlier runs into idle breaks, so keep warm has a record to judge from straight away.
  • rightsize's own compact writes a handoff. When whatsnext is not installed or cannot compact, rightsize now asks Claude Code's compaction for a handoff under eight headings: goal, next action, state, files, decisions, your instructions, open questions and dead ends. It quotes your words where they are unclear and drops tool output and file contents. The text was chosen by testing it against the old one on saved sessions. With whatsnext, its own compact text is used as before.

Cost warnings and estimates

  • A warning for unusually expensive turns (opt-in). After a turn that cost more than 99% of your own turns, the band asks once whether to warn you before a prompt that looks that expensive (Advanced · Big-turn warning: off, auto, $1, $2 or $5; off by default). With it on, a prompt whose estimate reaches the amount is held for the Question wait with Run it, Plan first (the prompt goes on with a request to propose a short plan and wait for your go-ahead) and Lower effort (only where rightsize would lower that kind of work now). A turn that is heading for the amount shows a band row with the estimate, what it has spent so far, Keep going and Finish up; Finish up puts a message in your prompt box asking Claude to finish the step and report, for you to send, and nothing is ever sent for you or stopped. If you stop that turn yourself, a request for a report is put in your prompt box too. rightsize learns as you go: early warnings can be false alarms. Non-interactive runs (-p, including --max-budget-usd) are left alone.
  • Estimates learn in dollars. Calibration now weighs each turn by what it cost, instead of averaging how far off each turn was. A cheap turn that ran ten times its estimate used to pull every estimate up; now an expensive turn counts for more, which is what a route choice compares. Your existing calibration carries over and shifts as new turns come in. After a turn's first 5 requests, rightsize also projects its cost again from its own pace and logs it beside the first estimate.
  • Fast mode is priced. rightsize knows fast mode's prices and keeps them current with the price check. It reads Claude Code's fastMode setting and checks each request's real cost, so it sees fast mode even when the setting is not the whole story. Estimates, keep warm and the report use fast rates while fast mode is on. When you turn fast mode on or off, or a model switch does, the band says what reading the conversation again at the new speed costs. On a subscription, the report says fast mode spend is paid from your usage credits.

Report

  • How each task ended. Every finished task now has an outcome: tests passed last, 👍, corrected, undone, 👎, tests failed last, or unknown. Your own signals count first. The Whole tasks section in /rightsize report details counts the outcomes, with unknown shown as unknown and never as success, and shows for each route (unchanged, lowered, raised, handed off) how many tasks were clean and the median cost of a clean task.
  • The rater can say it is not sure. When it cannot tell how hard a request is (too vague, or it depends on something it cannot see), rightsize leaves the prompt as it is: no lower or higher effort, no hand-off, no switch. The log says so, and the report's details count how many prompts it left alone this way.
  • Why lowered turns stepped back up. When a turn rightsize lowered goes back to your effort after a tool error, the log and the run log now say which tool failed and what kind of error it was: a failed test, a missing file, an edit that failed, another failed command, or other. /rightsize report details has a new LOWERING table: for each kind of work and model, the lowered turns, how many stepped back up and the most common cause, the real failures (you corrected, undid or 👎 the turn, or its last test failed), the miss rate the pause uses, and whether lowering is on or paused. When rightsize lowers or steps up has not changed.

Helpers

  • A busy helper is not stopped at a fixed count. A helper on Haiku or Sonnet with no estimate for its task used to stop at 25 or 40 tool calls however well it was going. Past that count it now goes on while it is making progress (a file change or a passing test run in its last 10 calls) and stops when it is not, or at 4 times the count. A helper that repeats itself is still caught at once by rightsize's stuck signs.