Skip to content

1.4.3 — Unified task dashboard and verified input receipts

Choose a tag to compare

View all tags
@woosungchoi woosungchoi released this 06 Oct 13:49
· 11 commits to main since this release
v1.4.3
0efcbb9
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Unified task dashboard

  • Start each task with one pinned dashboard containing receipt, file and result
    buttons. Keep detail previews in the same card, with bounded output and a Back
    button; fall back to an ordinary card if pinning is unavailable.
  • Remove the whole card and its buttons only after confirmed final-answer
    delivery. Preserve uncertain or failed delivery, retry failed deletion across
    restarts, and prevent stale callbacks from recreating completed cards.
  • Show native plan, aggregate diff and token snapshots. Execution completion,
    input receipt and Telegram delivery remain separate states.

Input confirmation and safe inspection

  • Reflect durable worker input acknowledgements automatically. Distinguish
    unchecked and pending input from genuinely uncertain delivery; temporary
    lookup failures cannot erase a confirmed receipt.
  • Add owner-bound /progress and /recovery inspection in the current
    chat/topic, plus changed-file, bounded diff and verified result views.
  • Persist native client IDs before app-server submission and acknowledgements
    afterwards. Recover only already completed matching inputs from read-only
    history; uncertain input is never automatically resubmitted.
  • Preserve distinct completed, failed and interrupted outcomes, with English,
    Korean, Russian and Traditional Chinese UI text. See
    Task dashboard and input receipts.

Dependencies and upgrade

  • Update the Codex CLI and SDK packages to 0.160.1.
  • Restart both the bot and worker after upgrading, once active tasks and pending
    final deliveries finish, so the new receipt/inspection protocol is available.
  • Transports without native receipt support can remain unchecked until a
    completed result is available. Telegram API acceptance is not a human read receipt.

Full changes: v1.4.2...v1.4.3

Assets 2
Loading