Skip to content
This repository was archived by the owner on Oct 7, 2026. It is now read-only.

v1.4.0 — skip re-uploading artifacts the server already has

Choose a tag to compare

@waynedev9598 waynedev9598 released this 14 Jun 10:44
· 9 commits to main since this release

Cuts the dominant push bandwidth cost. figs push re-uploaded every referenced artifact's full bytes on every push (the server only skipped the storage write after receiving them). With auto-push on every writing verb, a chatty agent re-sent its whole artifact set repeatedly — a 2 MB report ≈ 2.67 MB base64 per push, even no-ops.

  • The /api/ingest response now returns the agent's artifact manifest ({ name: "sha256:<hex>" }).
  • pushArtifacts re-hashes each local file (sha256 of the raw bytes) and uploads only files the server lacks or whose bytes differ — unchanged bytes never cross the wire.
  • Clearer output: N uploaded, M skipped (already synced — X not re-sent).
  • --reupload forces a full re-send (recovery if a stored object ever drifts from its row).

Compatibility: additive — figs-spec stays v2, MIN_CLI unchanged. Older servers omit the manifest → the CLI uploads everything (today's behavior); older CLIs ignore the field. Attachment immutability (same name + different bytes → 409) is unchanged.