agenthub agent setup — SessionStart hook enters the work loop
Closes the dormancy gap: an agent no longer needs to be told "call agenthub_work". `agenthub agent setup --agent <name> --role <role>` writes a verified Claude Code SessionStart hook (.claude/settings.json) whose command runs `agenthub hook-context`, which prints the work-loop instruction injected into every new session — so the agent claims tasks AND surfaces messages from the first turn, no manual trigger. - agentSetup.ts: agentSetup() (idempotent hook write, project or --user scope) + hookContext() (the injected instruction). - Honest limit (per Claude Code docs): SessionStart context is a strong nudge the model reads, not a hard directive; the guide reinforces it. Can't block startup. - Codex/Kimi aren't Claude Code — their guide already nudges agenthub_work first. Run once per agent machine. Bump 0.8.1 -> 0.9.0. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
AgentHub
Local coordination layer for AI coding agents.
Install
AgentHub is not yet published to npm. Clone the repository, build it, and link it globally:
git clone https://git.rebreak.org/chahine/agenthub.git
cd agenthub
pnpm install
pnpm build
npm link
After npm link, the agenthub command is available everywhere.
Quick Start
agenthub init
agenthub task create --title "Implement DNS cache" --role implementer
agenthub handoff create --fromRole architect --toRole implementer
agenthub status --update
Supported Agents
- Claude Code
- Codex CLI
- Kimi Code CLI
Network Mode
AgentHub can expose a project to other machines on the same network. Discovery is automatic: as soon as the host broadcasts, a client can find it without knowing the IP address.
On the host machine (e.g. Mac):
cd my-project
agenthub init
agenthub server start --host 0.0.0.0 --port 3377
On another machine (e.g. Windows) run init and accept the discovered server:
cd my-project
agenthub init # asks to connect to the LAN server it found
agenthub task create --title "Windows task" --role implementer
agenthub status
For non-interactive setup, let init discover the server automatically:
agenthub init --server auto
After init, every command automatically talks to the configured server. You can still override it per command with --server http://<ip>:3377 or via the AGENTHUB_SERVER environment variable.
The init --server step only stores the server URL locally; it does not create a second project. The host machine keeps the single source of truth.
License
MIT