onboard
Use when someone wants MemHub working where they are — a first setup, or a check or repair later (e.g. "onboard", "get started", "set up memhub", "set up my brain", "connect this repo to MemHub", "capture stopped working", "my sessions aren't being saved", "verify capture", "check memhub is working", "remove memhub's hooks"). One command signs in, sets up this machine's hooks, checks capture health, creates or reuses the repo's brain with its docs, offers up to five universal safety rules with one answer, and on Codex asks for the one hook approval only the person can give. Every step is skipped when already done; --status only reports, --remove takes the machine hooks out.
Pinned to revision 38fcebbb5125, so it is the text this page describes rather than whatever the author pushed since.
Pre-approved tools experimental
Experimental field. Support varies between clients, so this list is what the author declared, not what your client will enforce.
- Bash(python3 "${CLAUDE_PLUGIN_ROOT}/scripts/login.py" *)
- Bash(python3 "${CLAUDE_PLUGIN_ROOT}/scripts/setup_claude_fork.py" *)
- Bash(python3 "${CLAUDE_PLUGIN_ROOT}/scripts/setup_codex_hooks.py" *)
- Bash(python3 "${CLAUDE_PLUGIN_ROOT}/scripts/capture_health.py")
- Bash(python3 "${CLAUDE_PLUGIN_ROOT}/scripts/capture_health.py" *)
- Bash(python3 "${CLAUDE_PLUGIN_ROOT}/scripts/onboard.py" *)
- Bash(python3 "${CLAUDE_PLUGIN_ROOT}/scripts/save_artifact.py" *)
- Bash(git rev-parse --show-toplevel)
- Bash(git ls-files)
- Read
- Edit(//tmp/memhub-repo-overview.md)
- AskUserQuestion
Files
Every link opens the file at its source, pinned to the revision this page describes.