Repository navigation
orca-move 0.2.0, orca-quota 0.3.0: move-all moves a whole account at once - #22
Merged
Merged
Conversation
…once move.py move-all ends each idle session (or one waiting at the usage limit) with SIGTERM and types its resume line into its own Terminal tab. Busy sessions wait, permission prompts are skipped without --force. after-move rebuilds crons from orca-strator.json by role; switch-all hands over one ! line; orca-quota auto move runs move-all for the whole account at 85%. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
On 12 November an account hit its 5-hour limit during a switch-all. Sessions already out of quota could not take the turn to run
/orca-move:switch, and asking each one in turn was slow. A hand-written script that ended each Claude pid and typed the resume line into its Terminal tab moved 13 sessions in seconds. This makes that the product.What changes
orca-move/skills/switch/scripts/move.py: newmove-all <twin> [--account <from>] [--wait 60] [--force] [--assume-limited] [--dry-run], run by the person with!. Idle, or waiting at the usage limit: SIGTERM, wait up to 30 s, type the resume line into its own Terminal tab (else print it). Busy: wait, then skip. Background command running (shell): moved only at the limit. Permission dialog: never without--force. One line per session. The session running it moves last throughgo.test_move_all.py: 19 unit tests for the selection rules, the limit reading, a full run on fake accounts, and a dry run that writes nothing and ends nothing. CI's Python test step now also runsplugins/*/skills/*/scripts/test_*.py.after-moveskill: when the note says crons are unknown (a move-all note), rebuild them from.claude/orca-strator.jsonby role (orchestrator, Admiral) and tell the reporting line the new address.switch-allskill: dry run, then one!line; the per-session ask stays as the fallback.~/.config/orca-strator/moves/move-py(its move.py path) at start./quota auto on, the first session of an account at the warning level claims the account and runsmove-allfor all its sessions; without move-all it falls back to/orca-move:switch. Default warning level 90% to 85%. Two new tests.What does not change
plan,go,cancel,statusand the helper are untouched. Auto move stays opt-in.Clash with #21
#21 bumps orca-move to 0.1.5 and edits the
lineinplan(). This PR takes 0.2.0 and does not touch that line, so whichever merges second only rebases.Not run live
A real move-all and the auto move have only been tested with fakes, plus one real
--dry-runon a live account (24 sessions, correct moved/skipped lines, nothing written).🤖 Generated with Claude Code