Skip to main content

Introduction

Bitloops is a daemon-first CLI for capturing AI-assisted development activity, storing it in queryable backends, and exposing it through DevQL and the dashboard.

The current architecture has three main parts:

  • A single global user-level daemon service, com.bitloops.daemon
  • A thin CLI that starts, stops, queries, and controls that daemon
  • Optional repo policy files that shape what hooks and the CLI emit to the daemon

Stores, credentials, dashboard defaults, and runtime paths belong to the daemon config. Repo policy belongs to the repository and controls capture behaviour.

If you are upgrading from the older repo-local JSON model, read the upgrade note first.

Core Ideas​

  • The fastest way to get started inside a repository is bitloops init --install-default-daemon
  • bitloops start launches the global daemon and can prompt to create the default daemon config on a fresh machine
  • bitloops start --create-default-config remains the explicit bootstrap path for the default daemon config plus local default store files
  • first-run interactive telemetry consent belongs to that default-config bootstrap in bitloops start
  • bitloops init bootstraps the current project or subproject and can optionally queue an initial current-state sync
  • bitloops enable and bitloops disable toggle capture in the current project policy
  • bitloops dashboard opens the dashboard and starts the daemon if needed
  • bitloops status reports daemon health and sync queue state
  • DevQL commands talk to the daemon over the local HTTP and GraphQL transport

Next Step​

Follow the quickstart to initialise a project with bitloops init --install-default-daemon, or to use the explicit daemon-start flow when you need it.