cmd

cmd/

CLI command layer built on Cobra. Each file defines one or more commands and registers them via init().

Files

Command Tree

confab
├── hook
│   ├── session-start          (also: sync start)
│   ├── session-end            (also: sync stop)
│   ├── pre-tool-use
│   ├── post-tool-use
│   └── user-prompt-submit
├── sync
│   ├── start / stop
│   └── status
├── hooks
│   ├── add
│   └── remove
├── login / logout
├── setup
├── status
├── list
├── save
├── install
├── update
├── autoupdate [enable|disable]
├── version
└── redaction-test

How to Extend

Adding a new command

1. Create cmd/<name>.go
2. Define a cobra.Command with Use, Short, RunE
3. In init(), call rootCmd.AddCommand(<name>Cmd) (or attach to a parent command)
4. Register flags in init() via <name>Cmd.Flags()
5. Follow existing patterns — look at save.go for a simple example, login.go for a complex one

Adding a new hook type

This is a cross-cutting change spanning multiple packages:

1. cmd/hook_<name>.go — Create hook handler. Read JSON from stdin, do work, write HookResponse JSON to stdout
2. pkg/config/config.go — Add Install<Name>Hook(), Uninstall<Name>Hook(), Is<Name>HookInstalled()
3. cmd/hooks.go — Add install/uninstall calls in hooksAddCmd and hooksRemoveCmd
4. cmd/status.go — Add status check for the new hook
5. cmd/setup.go — Add to the setup flow
6. cmd/hook.go — Register the new hook command under hookCmd

Invariants

• Hook commands must read JSON from stdin and complete quickly. Claude Code blocks waiting for hook responses. Long-running work must be delegated (e.g., daemon spawn).
• Hook commands must not write to stdout except for HookResponse JSON. Claude Code parses stdout as the hook response. Use stderr for status messages.
• All hooks use pkg/types.HookInput. Parsed via types.ReadHookInput(os.Stdin) (base validation) or discovery.ReadHookInputFrom(os.Stdin) (adds transcript_path validation for session hooks).
• Hook handlers must always output valid JSON, even on error. An error should produce a response with continue: true rather than crashing with no output.
• Commands use RunE (not Run) to return errors. Cobra handles error display.

Design Decisions

Hooks are thin wrappers. Hook command files read stdin, call into pkg/ packages, and write the response. Business logic lives in the packages, not in command handlers. This keeps hooks testable and the command layer simple.

hook.go dispatches vs. separate binaries. All hooks go through a single confab hook <type> command rather than separate binaries. This simplifies installation (one binary) and hook management (consistent command pattern).

spawn.go uses os.StartProcess with Setpgid. The daemon must outlive the hook command. Setpgid: true creates a new process group so the daemon isn't killed when the hook exits. exec.Command with Start() would work too, but os.StartProcess gives more control over the process attributes.

maybeSpawnDaemon is called from both session-start and user-prompt-submit. The user-prompt-submit hook handles the "teleport" case where Claude Code resumes a session without firing SessionStart. If the daemon isn't running, it spawns one.

Testable function pattern. Hook handlers extract core logic into functions that take io.Reader/io.Writer parameters (e.g., sessionStartFromReader(r io.Reader, w io.Writer)). Tests call these directly without needing stdin/stdout. Some functions use overridable function variables (e.g., spawnDaemonFunc) for test injection.

Testing

go test ./cmd/...

Tests use the io.Reader/io.Writer pattern and function variable overrides to test hook behavior without actual process spawning or stdin/stdout.

Dependencies

Uses: all pkg/ packages

Used by: main.go (calls cmd.Execute())