Skip to main content

AccountPilot

A unified per-machine account sync framework. Pulls email, iMessage, calendar, and other personal data into a local SQLite database via a plugin architecture. Designed for individual users who want a queryable archive of their own data.

Features

  • Mail (IMAP IDLE): Gmail + Outlook + generic IMAP, OAuth2 (XOAUTH2) or password auth, RFC 2047 + MIME attachment handling, multi-account.
  • iMessage: macOS chat.db reader with watchdog file-watcher, attachment + group-chat support, attributedBody decoder.
  • Cross-source identity: one phone number = one person whether it appears in iMessage handles or Gmail signatures.
  • SQLite + FTS5 full-text search across every source.
  • Auto-restarting background daemon via launchd (macOS) or systemd (Linux) — install with one command.

Installation

Homebrew (macOS / Linuxbrew):

brew install aren13/tap/accountpilot

pip:

pip install accountpilot

pipx (recommended for CLI-only use, isolates dependencies):

pipx install accountpilot

Requires Python 3.11+. macOS or Linux. (iMessage support is macOS-only; mail works on both.)

Quick start

# Create the config skeleton
accountpilot setup

# Edit ~/.config/accountpilot/config.yaml to add your accounts
$EDITOR ~/.config/accountpilot/config.yaml

# For OAuth-based accounts (recommended): set up Google Cloud Console /
# Azure AD OAuth client JSON, then run the interactive login:
accountpilot oauth login google 1
accountpilot oauth login microsoft 2

# One-shot historical pull:
accountpilot mail backfill 1
accountpilot imessage backfill 2

# Install the auto-restarting background daemon:
accountpilot service install mail
accountpilot service install imessage

# Search across all sources:
accountpilot search 'invoice'
accountpilot search '"meeting tomorrow"'

Configuration

~/.config/accountpilot/config.yaml defines the people you sync FOR (owners) and the accounts you sync FROM. See docs/configuration.md for the full schema.

Documentation

License

AGPL-3.0-or-later. See LICENSE.

The AGPL'ed copy of aioimaplib (an upstream dependency) means AccountPilot ships under AGPL too. If you build a network service that exposes AccountPilot's functionality to end users, you must publish your modifications under AGPL — see the LICENSE file.

Metadata

Release files for accountpilot 0.2.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for accountpilot 0.2.1
File Size Uploaded
accountpilot-0.2.1.tar.gz 298.0 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for accountpilot 0.2.1
File Interpreter ABI Platform
accountpilot-0.2.1-py3-none-any.whl Python 3 none any Details

Total release size: 420.9 kB

Release files / accountpilot-0.2.1.tar.gz

Download URL accountpilot-0.2.1.tar.gz
Size 298.0 kB
Tags Source
SHA-256 checksum
How to use checksums
fb9c29c615df12d7f5243014a4804af10dde82daa43865fc85c050c188267e93
BLAKE2b-256 checksum
How to use checksums
0ff7136fb77c4a2b67768d54303a9493a948cfac7955aeee994940382dabb283
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on May 8, 2026.

Transparency log

Release files / accountpilot-0.2.1-py3-none-any.whl

Download URL accountpilot-0.2.1-py3-none-any.whl
Size 122.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
8b19dab5b07f871f38dcabbfe4da27810d5bb4be3b6abba59893ce1ce3627e23
BLAKE2b-256 checksum
How to use checksums
9e6fc5e097f0c8dae6afd0c67c7addf104d7d0684a6a742f28443b793525d106
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on May 8, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.2.1 This release

2 release files

0.2.0

2 release files

0.1.4

2 release files

0.1.3

2 release files

0.1.2

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page