Core docs are the default path through hack.
This section stays focused on local project orchestration: initialize a repo, run it on an isolated network, reach it on stable local hostnames, manage env and lifecycle, and keep working sessions alive. You do not need gateway, remote nodes, or extension setup to use this path.
- Initialize a project — or let an agent drive it with
hack init --with claude|codex|both(existing projects:hack agent onboard) - Architecture
- Env & secrets
- Lifecycle
- Sessions
- CLI overview — supported command surface and agent/scripted ergonomics
- Install + quick start: root README
- Local runtime checks:
hack up --detachhack openhack logs --prettyhack status/hack pshack down/hack restart
- If runtime state looks wrong, run
hack doctor, thenhack doctor --fixbefore manual repair. hack up/down/restart/doctoraccept--jsonfor a stable{ok, data | error: {code, message}}envelope withE_*error codes, and a global--no-interactive(orHACK_NO_INTERACTIVE=1) so scripted/agent runs never block on prompts.- In a linked git worktree,
hack updefaults to a branch instance named after the worktree's git branch (worktree.auto_branch), and the secret key is inherited automatically from the primary checkout via the shared git common dir. A detached linked worktree has no branch name to derive; pass--branch <name>, or setworktree.auto_branch=falsewhen intentionally targeting the base instance.
Move to Beta workflows only when you intentionally want unsupported experimental:
- gateway exposure
- remote nodes
- remote execution
- remote supervisor jobs
Move to Extensions & reference when you need the full command table, extension authoring details, or API-level reference material.