hivehouse 0.5.7

hivehouse 0.5.7 is a hotfix for away mode, for setups where every session runs on its own while the owner is away.

What's new

• Away mode can run without hivehouse's away hook. A root-owned switch in the owner's away file turns the hook off for that user's away sessions, for machines whose own guard does that job: line 9 hook=off in the version 5 file, written by hh-hub away --no-hook. A missing, broken or expired file keeps the hook on, and nothing a session can set or write turns it off. Everywhere else the hook works as before.
• The away hook answers within 20 seconds. Claude Code runs a command when a hook answers after its timeout, so the hook now refuses any call it cannot finish checking in 20 seconds, and its timeout is set to 30 seconds. Nothing the check started is left running after the answer.
• claude.ai connectors work in away sessions. Away sessions no longer start with --strict-mcp-config, which dropped every claude.ai connector. Every MCP server you have set up starts, and while the hook is on, a call to a server you did not allow is still refused. Allow a connector by the name Claude Code shows in its tool names; the exact form can differ between accounts.
• One source for the hub's away start. hh-hub away-args prints the hub's away launch, one item per line, from the same code hh-hub away uses, for tools that start the hub themselves.
• Chrome only when the owner allows it. Chrome stays off in away sessions unless the owner switches it on (hh-hub away --chrome). Then the hub can grant it to an orchestrator it starts (hh-hub start --chrome), and a session holding the grant can pass it to the agents it spawns (hh-spawn --chrome). A grant only goes down, never comes from the environment or a tmux session, and the hub itself never gets Chrome.
• A restarted agent opens where it lived. hh-spawn --respawn uses the tmux server the team record names, not the caller's.

Every change is listed in CHANGELOG.md.

hivehouse 0.5.6

hivehouse 0.5.6 is a small release that gets the plugin ready for Anthropic's plugin directory. Nothing changes in how teams work.

What's new

• Option values are checked where they are used. An effort is one of low, medium, high, xhigh or max (max is new: Claude Code takes it), a commit style is conventional or free, and a permission mode must be one hivehouse knows. A wrong value is refused, and the message names the allowed ones. plugin.json no longer lists the values itself.
• No here-documents in bin/. The six that were there are rewritten so the directory's validator can read every line. They behave the same.
• The README says what hooks/hub.tsx runs: the hh-hub subcommands it calls, the two slash commands it types when hub_auto_start is on, the files it reads, that it sends nothing off the machine, and the edits and git writes it refuses in the hub session.
• A plugin icon.

Every change is listed in CHANGELOG.md.

hivehouse 0.5.5

hivehouse 0.5.5 adds a delete guard that is always on, and stops a second Claude from taking over a running hub.

What's new

• A delete guard, always on. hivehouse puts its own rm, find and rsync in front of the real ones. A call that would delete something that must never go is refused whole, and nothing is deleted: /, your home folder, ~/.claude, the top of a synced cloud folder (iCloud Drive, Dropbox, ~/Library/CloudStorage), a git repository's root, a hub or project folder, hivehouse's own plugin folder, or a temporary folder itself. Work inside a temporary folder, and inside linked worktrees, passes. docs/rm-guard.md has the full list and what the guard does not stop.
• It holds in every session. A SessionStart hook puts the guard first on PATH on every start, clear and resume, also inside subagents. Sessions that hh-spawn and the hub start get it in their launch command too. Several copies of the guard on PATH hand a call on to the real tool once, and a loop between guards ends with an error.
• Scripts that delete follow a rule. The rules and the implementer role ask for set -euo pipefail, ${VAR:?} on every variable given to rm -r, and deletion tested only under a scratch folder.
• One hub at a time. hh-hub self refuses while the hub record names another Claude that is still running, and a second Claude in the hub folder is told it is not the hub.
• Safer tests. The test harness stops when TMPDIR is missing, instead of deleting the folder it was started from.

Known gaps

The guard stops rm, find and rsync called by name. It does not stop /bin/rm, command -p rm, a session that replaces PATH, a program that deletes files itself, git clean, unlink, rmdir, shred, find -exec sh -c '...' or rsync --remove-source-files.

Every change is listed in CHANGELOG.md.