Cloud Sync

How preferences sync across machines and projects.

How it works

When you’re logged in, Aspect Code syncs your learned preferences to the cloud. This means:

Switch machines — your preferences follow you

Revisit projects — your corrections are remembered

No local files — preferences are stored in the cloud, not in your project directory

Sync is automatic and non-blocking. If you’re offline, the CLI continues working with an empty preference set.

Only learned preferences sync to the cloud — the allow/deny decisions you make when confirming or dismissing assessments.

These do NOT sync (they stay local):

AGENTS.md — generated per-project, committed to your repo

Scoped rules (.claude/rules/ac-*.md) — generated per-project

Dream state — ephemeral timing data

aspectcode.json — project config

Preferences contain only metadata about your corrections:

Which rule fired (e.g., “co-change”, “naming-convention”)

The file/directory scope

Whether you allowed or denied it

No source code, file contents, or API keys are ever sent to the cloud.