Accounts Local Sync

Opta Accounts provides federated identity and preference sync across your Opta ecosystem. Local Sync keeps sensitive execution payloads on-device while allowing account-level configuration continuity between machines.

Allowed sync scope includes profile metadata, non-sensitive preference state, and policy version pointers. Disallowed scope includes private prompts, repo contents, raw tool outputs, and model reasoning traces.

Primary use case is consistent behavior across devices without leaking project IP. For example, you can keep identity/session routing aligned while each machine keeps its private local context isolated.

The Opta CLI daemon authenticates with encrypted tokens, then performs bounded sync operations for approved metadata only. Runtime execution remains local to your daemon + LMX stack.

Use CLI commands to inspect and enforce sync policy. Always verify effective config after toggling so you can confirm policy took effect.

opta config view
opta config set sync.enabled true
opta status