{"version":"2.1.280","anchor":"directory-sync-push-telemetry-expanded-to-track-chained-push","canonical_anchor":"directory-sync-push-telemetry-expanded-to-track-chained-push","heading":"Directory-sync push telemetry expanded to track chained pushes and basis info","tier":"internal","area":"Directory Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/directory-sync-push-telemetry-expanded-to-track-chained-push","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Directory-sync push telemetry expanded to track chained pushes and basis info\n\nDirectory-sync push telemetry now records whether a push chained off a prior one and other basis details\n\n**What**\n\nThe `tengu_dir_sync_push` telemetry event, which records when Claude Code pushes local directory changes through its git-based sync, now reports several new fields: `chained` (whether this push builds on a previous one), `chains` (how many pushes are chained together), `busy_cause` (why a snapshot was refused when git was busy), `first_upload`, `basis`, `link_edge`, and `chain_broken`.\n\n**Why**\n\nThese extra fields give more detail about how each sync push relates to the ones before it, which can help diagnose sync issues like stalled or broken chains of pushes.\n\n- Area: Directory Sync\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}