Skip to content

Collector 0.7.46: install heartbeat with the computer name, and relay-aware capture checks

Choose a tag to compare

View all tags
@CryptoJym CryptoJym released this 01 Oct 15:53
v0.7.46
82dc901
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Collector 0.7.46 replaces 0.7.45. Setup now shows each machine by its own name and whether it is really capturing, even when it is idle. Usage from a tool's own repository finds its project. The capture checks also understand the fleet's standard OpenTelemetry relay.

  • A heartbeat with the computer's name (#444).
    • The collector checks in about every 15 minutes while it runs, even when idle, and once at start. Each check-in carries the collector version, the last capture time and the capture state.
    • Setup shows an idle machine as healthy instead of silent.
    • The machine name comes from the computer's name and is trimmed and capped at 64 characters.
    • The heartbeat never delays uploads, backs off on errors, and stops quietly if the cloud has no endpoint.
  • Relay-aware capture checks (#445). A Claude Code or Codex seat that reports through the fleet's OpenTelemetry relay on 127.0.0.1:4318 counts as live coverage, not as a capture gap. The relay forwards every request to this collector unchanged.
  • Usage finds its project from the tool's own repository (#441). When a session has no project of its own, usage takes the repository the tool itself works in, from earlier context in the same session only.
  • Plan-limit readings carry the cloud's account key (#432). Each AI account's plan-limit percent arrives under the same key the cloud's Accounts page uses.
  • Startup survives a passing lsof glitch (#443). A transient process-probe failure at startup no longer rolls a fresh ledger back, and workers share the probe allowlist.
  • Restore retries an inconclusive probe (#440). An inconclusive archive-handle probe is retried before a restore is refused.
  • Queued summaries read only the queue (#437). Summary repair reads its queued rows instead of every event.

Updating and rolling back:

  • The ledger change is additive: two new tables, created if missing. Rolling back to 0.7.45 leaves them unused.
  • The cloud's install-contact endpoint is live (cloud #219). Older clouds answer 404, and the heartbeat then stops quietly until restart.

Runtime CLI SHA256: a2622864d501ccbffc154c1c810238f5df55b0c65c66262ddc29d5e8ca3abc55.

Qualification: typecheck, the full proof suite and system end-to-end qualification ran on the merged commit. The published package is the qualified artifact from that run.

Assets 5
Loading