Skip to Content
Full Sync

Full Sync Command

The bee sync command exports your Bee data to local markdown files, creating a portable backup of your conversations, facts, todos, daily summaries, and insights for use with AI agents.

For incremental polling of recent changes as a feed instead of a file snapshot, see Agentic Sync.

Usage

bee sync [--output <dir>] [--recent-days N] [--only <facts|todos|daily|conversations|insights>] [--full] [--since <epochMs>]

This creates a bee-sync/ directory in your current location with all your data.

Incremental by Default

After a first sync, re-running bee sync into the same output directory is incremental: it re-fetches only the daily summaries, conversations, and insights that have changed since the last run. Facts and todos are always re-fetched in full, since they are small.

Sync state is tracked in a .bee-sync.json manifest inside the output directory (it stores per-target changefeed cursors). Delete the manifest — or the entire output directory — to force a full re-sync.

Deletes are not reconciled. A local file for an item that is later deleted on the server remains on disk until you do a --full re-sync into a fresh directory.

Options

--output <directory>

Specify a custom output directory (default bee-sync):

bee sync --output ~/my-bee-data

--only <target>

Limit sync to a comma-separated list of data types (facts, todos, daily, conversations, insights, or all):

# Only sync facts bee sync --only facts # Sync facts and todos bee sync --only facts,todos # Only sync conversations bee sync --only conversations # Only sync daily summaries bee sync --only daily # Only sync insights bee sync --only insights

--recent-days <N>

Limit daily summaries, conversations, and insights to the last N days (facts and todos are always synced in full):

bee sync --recent-days 7

--recent-days applies to full syncs only. It is ignored on an incremental run, where the set of items to fetch is driven by the changefeed cursor.

--full

Force a complete re-sync, ignoring the saved manifest and rewriting it with fresh cursors:

bee sync --full

--since <epochMs>

Advanced/recovery option: override the saved incremental cursor with an explicit epoch-milliseconds timestamp for the changefeed-driven targets (daily summaries, conversations, and insights). Most users never need this — prefer the default incremental behavior or --full.

bee sync --since 1704067200000

Output Structure

After running bee sync, your data is organized as follows. Conversations and insights each live in a separate top-level tree (conversations/ and insights/, one folder per day), parallel to daily/ — they are not nested under daily summaries.

    • .bee-sync.json
    • facts.md
    • todos.md
        • summary.md
        • 123.md
        • 124.md
        • 789.md

File Formats

All timestamps are written in ISO 8601 format (UTC).

facts.md

All facts, organized by confirmation status. Each line is - text [tags] (ISO timestamp, id N); tags are omitted when empty.

# Facts ## Confirmed - Fact text here [tag1, tag2] (2024-01-15T10:30:00.000Z, id 42) - Another fact (2024-01-14T08:00:00.000Z, id 41) ## Pending - Unconfirmed fact (2024-01-16T12:00:00.000Z, id 43)

todos.md

All todos, organized by completion status. Each line is - text (id N, created ISO, alarm ISO); the alarm clause is omitted when no alarm is set. There are no checkboxes.

# Todos ## Open - Buy groceries (id 10, created 2024-01-15T09:00:00.000Z, alarm 2024-01-16T18:00:00.000Z) - Call dentist (id 11, created 2024-01-15T10:00:00.000Z) ## Completed - Finish report (id 9, created 2024-01-14T08:00:00.000Z)

daily/YYYY-MM-DD/summary.md

Daily summary with metadata bullets followed by section headings. Optional sections (Summary, Email Summary, Calendar Summary) appear only when present.

# Daily Summary — 2024-01-15 - id: 100 - date_time: 2024-01-15T00:00:00.000Z - created_at: 2024-01-16T02:00:00.000Z - conversations_count: 5 ## Short Summary Brief overview of the day's activities. ## Summary Detailed summary of conversations and events. ## Email Summary Summary of email activity (if available). ## Calendar Summary Summary of calendar events (if available). ## Locations - 123 Main St, City (37.77490, -122.41940) - Coffee Shop (37.78500, -122.40900) ## Conversations - 123 (2024-01-15T09:00:00.000Z - 2024-01-15T09:30:00.000Z) — Meeting with team - 124 (2024-01-15T14:00:00.000Z - 2024-01-15T14:15:00.000Z) — Quick chat

conversations/YYYY-MM-DD/ID.md

Individual conversation transcripts with full details: metadata bullets, summaries, primary location, suggested links, and transcriptions grouped under ### Transcription <id> with one bullet per utterance (- Speaker: text).

# Conversation 123 - start_time: 2024-01-15T09:00:00.000Z - end_time: 2024-01-15T09:30:00.000Z - device_type: ios - state: processed - created_at: 2024-01-15T09:00:00.000Z - updated_at: 2024-01-15T10:00:00.000Z ## Short Summary Brief description of the conversation. ## Summary Detailed summary of what was discussed. ## Primary Location - 123 Main St, City (37.77490, -122.41940) - created_at: 2024-01-15T09:00:00.000Z ## Suggested Links - https://example.com/resource (2024-01-15T09:15:00.000Z) ## Transcriptions ### Transcription 456 - realtime: false - Speaker 1: Hello, how are you? - Speaker 2: I'm doing well, thanks!

insights/YYYY-MM-DD/ID.md

One file per insight Bee generated about you, filed under the day it was generated. A ## Corrections section is added when the insight has corrections.

# Insight 789 — Morning focus blocks - id: 789 - generated_at: 2024-01-15T16:00:00.000Z ## Description You do your deepest work before 11am on days without early meetings. ## Suggested Actions - Block 9-11am for focused work on Tuesdays and Thursdays.

Insights you dismissed or marked inaccurate in the Bee app are not synced, matching bee insights list. Insight sync requires CLI 0.9.0 or later.

Notes

  • The first sync (or any --full run) fetches everything; facts and todos are always re-fetched in full.
  • Re-runs are incremental: only daily summaries, conversations, and insights that changed since the last run are re-fetched, tracked via the .bee-sync.json manifest in the output directory.
  • Conversations and daily summaries are fetched concurrently for faster syncing.
  • All timestamps are in ISO 8601 format (UTC).
  • The output directory is created if it doesn’t exist.
  • Existing files for changed items are overwritten in place; deletes are not reconciled, so a local file for an item later deleted on the server remains until a --full re-sync into a fresh directory.

Automation

You can automate sync with a cron job:

# Add to crontab (runs daily at midnight); incremental re-runs keep this cheap 0 0 * * * cd ~/bee-backup && bee sync

Or use a shell alias for quick syncing:

# Add to ~/.bashrc or ~/.zshrc alias bee-backup="bee sync --output ~/Dropbox/bee-backup"
Last updated on