Class Enable

atomic-cli/src/commands/agent/enable.rs:42–82

/// Install agent hooks for turn-level recording.
#[derive(Debug, Args)]
pub struct Enable {
    /// Which agent to install hooks for.
    ///
    /// If not specified, auto-detects which agent is present in the
    /// repository (looks for `.claude/`, `.gemini/`, etc.).
    #[arg(long, value_name = "NAME")]
    agent: Option<String>,

    /// Force reinstall hooks even if already installed.
    ///
    /// Removes existing Atomic hooks before installing new ones.
    /// Non-Atomic hooks in the agent's config are preserved.
    #[arg(short, long)]
    force: bool,

    /// Install hooks for all detected agents.
    ///
    /// If multiple agents are detected (e.g., both Claude Code and
    /// Gemini CLI are configured), install hooks for all of them.
    #[arg(long)]
    all: bool,

    /// Install hooks globally (~/.claude/settings.json).
    ///
    /// Global hooks fire for every Claude Code session regardless of
    /// project. This is the recommended way to enable Atomic tracking —
    /// install once, works everywhere that has a `.atomic/` directory.
    #[arg(short, long)]
    global: bool,

    /// Install hooks from an integration-supplied manifest file.
    ///
    /// The manifest (shipped by an integration package such as atomic-codex)
    /// names its own target settings file and the hook commands to register,
    /// and is merged in idempotently — preserving non-Atomic hooks. Because the
    /// definitions live in the integration repo, updating an agent's hook
    /// wiring never requires rebuilding `atomic`. When set, `--agent`/`--global`
    /// are not needed; the manifest is self-describing.
    #[arg(long, value_name = "FILE")]
    hooks: Option<std::path::PathBuf>,
}

impl Enable {
    /// Create a default instance for testing.