xiaoyaner0201’s hermes-jev-thread-status turns Discord thread titles into a task board. New requests can select [Running] directly; Jev classifies tool results and visible replies into configured statuses such as [Needs feedback] or [Done].

The implementation separates describing progress from granting permission to archive a thread.

Give Jev several bounded questions

The client calls TypeSafe’s decision endpoint with a status menu and NO_CHANGE, plus separate questions about completion and suitability for archiving. Optional title checks ask whether the existing name has become stale.

  • The code uses a 0.90 cutoff for status confidence and the completion and archive scores. These are application settings, not measured accuracy guarantees.
  • Title-change judgments use a separate 0.70 cutoff in the inspected code; the main model generates the replacement name.
  • Low-confidence status results can trigger a main-model second opinion when that integration is available. Otherwise uncertainty keeps the old status.
  • New activity and configuration changes invalidate outdated assessments before they can authorize fresh writes.

That fallback makes the implementation more nuanced than the README’s claim that unclear decisions simply preserve the old status.

Require evidence before archiving

The archive engine requires both positive Jev answers, an enabled archive policy and a verified final-message receipt. It also checks permission and current task facts: active work, unconsumed results and unanswered questions must all be clear.

  • The completion and archive answers are separate questions in the same Jev request, not independent model evaluations.
  • The delay starts from confirmed delivery. New activity can cancel the candidate or reopen an archived thread.
  • The engine records an uncertain-write recovery intent before sending the archive request, then reads the exact thread back.
  • The rename scheduler separately budgets writes and keeps the latest desired state when updates must wait.

Typed output checks answer shape. Whether a task is actually finished still depends on the evidence and the decision policy.

Ordinary Hermes replies cannot yet auto-archive

The runtime starts with a work-facts callback that returns unknown. Its documentation also says native Hermes replies lack a trusted final-delivery receipt. Both gaps block automatic archiving through that path, even when a title says [Done].

The publisher interface exists for trusted integrations, but the documented external consumers remain unconnected. Busy-session follow-ups invalidate stale decisions without receiving full status classification.

The project targets a pinned Hermes version and uses internal host interfaces for some features. Its excerpts leave the machine for TypeSafe; redaction is explicitly best-effort.

Verification: inspected commit 99f188c and ran the Jev-client and consumer/archive test modules: 47 passed against synthetic peers in a network-isolated sandbox. No live Jev or Discord run, production accuracy measurement or security audit was performed.