[RELEASE] feat(sync): deferred-sync mode for auto-provisioned (KiloClaw) users#906
Merged
vivekchand merged 1 commit intomainfrom May 7, 2026
Merged
[RELEASE] feat(sync): deferred-sync mode for auto-provisioned (KiloClaw) users#906vivekchand merged 1 commit intomainfrom
vivekchand merged 1 commit intomainfrom
Conversation
vivekchand
pushed a commit
to vivekchand/cloud
that referenced
this pull request
May 7, 2026
Previously the sync daemon was spawned on the user's first "View Observability" click — which produced two real bugs the E2E test caught: (a) a spawn-on-click race that left users staring at a "Run: clawmetry connect" red banner during cold-start, and (b) the dashboard sometimes rendered "Node not found" because the nodes table hadn't been populated by a heartbeat yet. New shape: - Bootstrap registers with source='kiloclaw' (the cloud-side companion PR uses this to mark the user account as deferred-sync) and spawns the daemon at instance boot. The daemon heartbeats every 60s — that's enough for the dashboard to render correctly the moment the user clicks View Observability — but uploads ZERO content (sessions, events, logs, memory) because the cloud's /ingest/heartbeat returns sync_allowed=false, reason='intent_pending' until the user has signalled intent. - POST /_kilo/clawmetry-start-sync no longer spawns anything (the daemon is already running). Instead it reads api_key from /root/.clawmetry/config.json and POSTs to the cloud's new /api/cloud/intent-start endpoint, which flips users.sync_intent_at. The daemon's next heartbeat (~60s) sees sync_allowed=true and uploads resume. Why this matters: - No spawn-on-click race — daemon is always there, only the data flow is gated. Eliminates the "Run: clawmetry connect" misleading banner for KiloClaw users. - Privacy + cost: 99% of inert KiloClaw boxes never sync any content, only metadata-only heartbeats. Real engagement signal too — we literally know which users opened their dashboard. - "We get to know this user really wants to use ClawMetry" — the intent flag IS that signal. This PR depends on: - vivekchand/clawmetry-cloud#635 (cloud-side gate + intent-start endpoint) - vivekchand/clawmetry#906 (OSS daemon recognises reason='intent_pending') Both must merge + deploy before this is meaningful for KiloClaw users. This PR is safe to ship before them — the daemon will heartbeat, the cloud will accept it (with no special response), and uploads will proceed as before. Once cloud is deployed, deferred mode kicks in.
…sync mode Before this change, the daemon treated every sync_allowed=false response as an expired trial and logged a misleading "Upgrade to Pro" warning. With the new KiloClaw integration, the cloud may also tell the daemon it's in deferred-sync mode — heartbeats accepted, no other uploads — until the user clicks "View Observability" in their KiloClaw dashboard. Surface that as a distinct, friendly log line so the daemon's behavior is comprehensible to both KiloClaw users (auto-provisioned, will engage later) and trial-expired users (existing copy still applies). Also gates two previously ungated startup-sync paths (sync_sessions_recent, sync_claude_cli_sessions) on _sync_allowed(), so deferred / paused sync is airtight: zero session / event / log / memory data leaves the machine until the cloud explicitly says yes. Cloud-side change that emits reason='intent_pending' is in clawmetry-cloud/feat/deferred-sync-kiloclaw — required before this change takes effect for new KiloClaw users.
vivekchand
force-pushed
the
feat/deferred-sync-gate
branch
from
04c51be to
7c1de83
Compare
vivekchand
changed the title
vivekchand
added a commit
that referenced
this pull request
May 7, 2026
…sync (#907) The deferred-sync gate that #906 added (cloud responds with reason='intent_pending' for KiloClaw users until they click View Observability) reuses _sync_allowed() — extend the docstring so a reader notices that this isn't only about trial-expired users. Co-authored-by: vivekchand <vivek@clawmetry.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Lets the cloud tell the OSS daemon "heartbeats yes, everything else no" without the trial-expired UX. KiloClaw auto-provisions ClawMetry on every new instance via `/api/register`, but we don't want session / event / log / memory data flowing to the cloud until the user explicitly clicks "View Observability" — privacy + compute story is much better when 99% of inert KiloClaw boxes never sync content.
The gate: cloud responds to `/ingest/heartbeat` with `{sync_allowed: false, reason: "intent_pending"}`. This commit teaches the daemon that this is a deferred state, not a trial-expired state, so the log message is friendly instead of an upgrade nag.
Changes
Why this and not a separate config flag?
The `_TRIAL_STATE` machinery is already polled on every heartbeat response, already gates every upload, and already supports the exact transition ("sync_allowed flips → uploads resume, no daemon restart") we need for KiloClaw. Adding `reason` is a one-field tweak; a parallel mechanism would be duplicative.
Sequencing
Cloud-side change that emits `reason="intent_pending"` lives in `clawmetry-cloud/feat/deferred-sync-kiloclaw` and must merge + deploy before this is meaningful for KiloClaw users. This OSS PR is safe to ship independently — old cloud (no `reason` field) → daemon falls through the existing trial-expired branch (current behavior, no regression).
Test plan