Skip to content

v0.3.0 — lock queue, session cleanup, inbox threading, CLI dashboard

Choose a tag to compare

@garniergeorges garniergeorges released this 22 Jul 23:21
777f116

TL;DR — Locks get a waiting queue with inbox notifications and heartbeat renewal, sessions clean up after dead processes, the inbox learns reply threading, and the CLI gains a live dashboard. Plus configurable retention TTLs and a same-branch warning.

Locks (#28)

  • resource_claim accepts wait: true: when the resource is held, the session joins a FIFO waiting queue and the response includes queue_position.
  • On resource_release (or lock expiry), the first waiter receives an inbox DM (priority warning), surfaced by the existing 🔔 banner at the next prompt.
  • session_heartbeat accepts renew_locks: true to push back the expiry of every held lock by its own TTL during long operations.
  • resource_list now shows waiting sessions per lock.

Sessions (#29)

  • session_unregister accepts client_session_id as an alternative to session_id (cleanup after a client_session_id_conflict).
  • claude-presence clear --session <id> / --client <uuid> remove one session explicitly.
  • claude-presence clear also prunes sessions whose recorded process is dead on the current host (remote/team sessions untouched).

Inbox (#31)

  • Reply threading: broadcast accepts reply_to: <message id>; replies are addressed to the original sender as a DM unless to_session says otherwise.
  • Retention is configurable via CLAUDE_PRESENCE_SESSION_TTL_SECONDS, CLAUDE_PRESENCE_LOCK_TTL_SECONDS and CLAUDE_PRESENCE_INBOX_RETENTION_SECONDS.

CLI (#32)

  • New claude-presence dashboard: sessions, locks and unread counts grouped by project, also in --json.
  • --watch / -w (with --interval <s>) refreshes status, locks and dashboard in place.

Same-branch warning (#33)

  • Registering on, or checking out, a branch another session is already working on now triggers a visible warning (tool response, CLI output and prompt banner).

Maintenance

Test suite: 104 → 144 tests. Schema migrations are applied in place and covered by tests against the verbatim v0.2.1 schema.

Full changelog: v0.2.3...v0.3.0