Summary
neurostack hooks install currently requires a separate manual step after neurostack init. Hooks should be set up automatically as part of the init flow.
Proposed Behavior
During neurostack init, after vault setup and config generation:
- Install systemd harvest timer (existing
hooks install logic) — hourly neurostack harvest --sessions 3
- Detect Claude Code and inject a
SessionEnd hook into ~/.claude/settings.json that runs neurostack harvest --sessions 1 on session exit
- Support other agents (Codex, Gemini) if their hook config paths are detected
UX
- Prompt user during interactive init: "Install automation hooks? (harvest timer + session hooks) [Y/n]"
--no-hooks flag to skip in non-interactive mode
- Print summary of what was installed
Why
New users don't know about neurostack hooks install and miss out on automatic session harvesting. This is the highest-value automation NeuroStack provides and should be on by default.
Acceptance Criteria
Summary
neurostack hooks installcurrently requires a separate manual step afterneurostack init. Hooks should be set up automatically as part of the init flow.Proposed Behavior
During
neurostack init, after vault setup and config generation:hooks installlogic) — hourlyneurostack harvest --sessions 3SessionEndhook into~/.claude/settings.jsonthat runsneurostack harvest --sessions 1on session exitUX
--no-hooksflag to skip in non-interactive modeWhy
New users don't know about
neurostack hooks installand miss out on automatic session harvesting. This is the highest-value automation NeuroStack provides and should be on by default.Acceptance Criteria
neurostack initinstalls harvest timer unless declinedneurostack initdetects Claude Code and adds SessionEnd hookneurostack init --no-hooksskips hook setupneurostack hooks statusreflects hooks installed via init