Project: Cathy Hockey Multi Cam Video (project ID 7e92d24b-454a-4bb0-bd07-49b1caba3624)

Setup: Descript desktop app on Mac, working alongside the Descript project agent / API, which operates on the cloud copy of the project.

The problem: There is no way to see whether the desktop app has finished syncing to the cloud, and no way to force or confirm a sync. When every edit happens in one app this is invisible, but the moment the project agent is involved it becomes a real hazard: the agent edits the cloud copy, so any agent job fired while desktop changes are still uploading runs against a stale composition. The workflow guidance ends up being "wait and hope," because the app exposes no sync state at all.

What this cost us in practice, on one episode:

Manual setup done in the desktop app (sequence build, track fader changes, speaker labels) wasn't verifiably in the cloud before agent jobs ran — the only available check was comparing composition durations by eye between the desktop timeline and an API read.

At one point the cloud copy reported the composition at 2:47:38 (duplicate sequence insertions) while we were troubleshooting in the desktop app — with no way to tell whether we were looking at a synced state, a mid-sync state, or divergence, and no timestamp anywhere saying "cloud last updated at X."

Track volume changes made in the desktop app appeared not to take effect in cloud reads for an extended period — impossible to distinguish "not synced yet" from "changed the wrong control" (both turned out to be true at different points, and diagnosing which was which took hours).

Suggested fixes:

A visible sync indicator in the desktop app — synced / syncing / offline, with a "last synced to cloud" timestamp on the project.

A manual "Sync now" action.

On the agent/API side: expose the project's last-synced timestamp, and have the project agent warn (or refuse) when the cloud copy it's about to edit is older than the most recent desktop session — an "editing a possibly stale composition" guard.

Longer term: a conflict/divergence warning when desktop and cloud states differ materially (e.g. composition duration mismatch).

For a workflow where a human edits in the app and an agent edits via the cloud — which your project agent actively encourages — sync state can't stay invisible.