Skip to main content

Capture

Capture is the repo-side part of Bitloops. Hooks and the slim CLI collect context locally, apply repo policy, and send the resulting events to the daemon.

Enabling Capture​

bitloops init

Project bootstrap installs:

  • git hooks
  • supported agent hooks for the current project
  • it may also resolve telemetry consent if the existing daemon config needs it

After that, use capture toggles:

bitloops enable
bitloops disable

These commands edit [capture].enabled in the nearest discovered project policy. Installed hooks stay in place and no-op while capture is disabled.

If the global daemon config already exists but telemetry consent is unresolved, interactive bitloops enable can ask before it edits project policy. In non-interactive mode you must pass an explicit telemetry flag.

Use bitloops uninstall if you want to remove Bitloops hook integration itself.

Policy​

Shared capture policy lives in .bitloops.toml:

[capture]
enabled = true
strategy = "manual-commit"

Local overrides live in .bitloops.local.toml, which can also stand on its own without a sibling shared file.

What Capture Does Not Configure​

Capture policy does not define:

  • store backends
  • daemon runtime paths
  • credentials
  • dashboard bundle locations

Those remain daemon concerns.