Skip to content

fairshare 0.3.0

Latest

Choose a tag to compare

@Dongli99 Dongli99 released this 21 Nov 19:06
· 1 commit to main since this release

pickup now always continues the same session, and the new fork makes a copy on purpose. fairshare can also take over your per-account aliases.

After upgrading, run fairshare doctor --fix to put the updated skill in the hub.

Changed: pickup never copies (decision 32)

fairshare pickup used to continue a session that might still be running as a copy under a new id, without being asked. Tooling that tracks a session by its id then treated the session's own work as someone else's. Now:

  • A session that isn't running resumes in place, under its own id. This includes one you stopped by hand.
  • A worker, picked up by its main session, is stopped and resumed in place, without asking. fairshare started it, and its main session manages it.
  • Another session running in the background: from a terminal, fairshare asks Stop it and continue it here? [Y/n] and says so first if a turn is in progress. Without a terminal it refuses and names the stop command and fork.
  • A session open in a terminal is never stopped. Exit it there, then pick it up.
  • Bare pickup in a session not started by fairshare refuses, since nothing can stop that session. Use fairshare handoff or fairshare fork.

New

  • fairshare fork [SESSION]: a copy under a new id, on the best account (or -a). The original goes on, with its workers. Forks are named <name>-f2, -f3, and so on. The copy is told it is the copy and waits for instructions.
  • A session list. Bare fairshare pickup or fairshare fork from a terminal lists up to 8 recent main sessions to choose from: this folder's first, with their state (at its limit, running, stopped) and the last thing you typed in each. Workers are left out; their main session manages them, and pickup <id> still reaches one.
  • fairshare aliases [--remove]: replaces per-account CLAUDE_CONFIG_DIR aliases that still point at pre-hub folders with one marked block (alias X='fairshare run -a X'). It shows the diff and asks first, and makes a backup. setup and join offer it, and doctor warns while the old aliases are still in effect. fairshare run -a X <subcommand> (such as daemon status, agents --json, rm <id> or stop <id>) goes straight to Claude Code on that account's folder.
  • A usage log (~/.local/state/fairshare/usage/<account>.jsonl) records each change in the usage percentages and the dollars drawn since the previous one. It's groundwork for showing room left in dollars.

Fixed

  • A background session picked up on its own account always became a copy. Claude Code copies a background session resumed with any flag, and fairshare always added --name, --model and --effort. A known background session now resumes with none, keeping its saved name, model and effort. An explicit --model or --effort there is refused, with the matching fork command.
  • A launcher whose terminal closed while it was suspended (Ctrl-Z) stayed stopped forever, unable to clean up its child. It now stops itself the way Ctrl-Z does (SIGTSTP), which the kernel drops when no shell is left to resume it.
  • When a full reset is planned and due, every usage warning on that account now says to work to the limit rather than move.
  • Docs: how to recover when Claude Code's shared background process on an account breaks every worker started from it.