decyde 0.6.1

Changed

• The question list in the TUI and the web inbox shows the agent's name (--name, e.g.
  "Claude, HigherDeal lead") instead of only its type, still coloured by type. Asks
  without a name show the type as before.

decyde 0.6.0

Added

• Why this matters: decyde ask --why takes at most two sentences on the most
  important reason for the ask. It shows under Context in the web inbox, the TUI and
  Telegram.

Changed

• The agent protocol asks for short, plain context with only the facts that change the
  decision, and for --why on every ask. decyde update refreshes the instructions
  your agents already have.

decyde 0.5.2

Added

• decyde telegram setup gives the bot decyde's photo, description and about text, but
  only the ones it does not have yet, so anything set in @Botfather stays as it is.

decyde 0.5.1

Fixed

• decyde telegram setup crashed while waiting for your Start message, and the server's
  Telegram poller hit the same error: the HTTP timeout and Telegram's long-poll timeout
  shared one argument name.

decyde 0.5.0

Added

• Answer from your phone through your own Telegram bot (decyde telegram setup).
  Each question arrives with a button per option and a Dismiss button; replying to the
  message answers it with your own text, and /open lists what is waiting. Answers are
  delivered to the agent like any other. Messages update when a question is answered
  elsewhere or withdrawn. Only the Telegram account that set the bot up can answer.

Changed

• ~/.decyde/config.json is readable only by you, since it can hold the bot token.

decyde 0.4.3

Changed

• The terminal UI header shows the version beside the server address and a purple
  "by HigherOps" under it. Update notices move up to the free row so the two never clash.

decyde 0.4.2

Fixed

• Answers to Claude Code sessions that skip permissions were held behind an approval
  dialog, because Claude Code treats a message from the decyde server as coming from an
  unknown process. decyde ask now starts a small detached relay from inside the asking
  session; it waits for the answer and posts it to the session's inbox itself, which
  Claude Code delivers without approval as the session's own. The server no longer posts
  to Claude inboxes.

decyde 0.4.1

Fixed

• Answers given in the terminal UI are delivered by the background server, not by the
  TUI process. A TUI left open across an upgrade used to deliver with its old code and
  miss newer wake routes.

decyde 0.4.0

Added

• Answers wake agents in any terminal, not just Herdr or tmux:
  • Claude Code: decyde messages the session that asked through its own inbox
    socket (Claude Code 2.1.224+). An idle session starts a new turn; a busy one reads
    the answer at its next step.
  • Codex: decyde starts a turn in the asking thread through Codex's app-server
    daemon (Codex 0.161+), or adds the answer to the turn already running. It shows in
    the Codex terminal as if typed.
  • Grok (and any agent that runs background commands): the agent starts
    decyde wait <id> in the background after asking, and is woken when it returns with
    the answer. While a decyde wait is running, decyde hands the answer to it instead
    of pushing it anywhere else.

Changed

• The Stop hook no longer holds any session decyde can wake, so answers never queue
  behind it. It only holds a session with no wake route at all, until the first answer.
• decyde wait polls every 3 seconds instead of 15.
• ~/.decyde is created private (0700), since it now holds per-session inbox tokens.

decyde 0.3.2

Fixed

• Answers no longer pile up behind a waiting agent. An agent in Herdr or tmux that ended
  its turn with open questions was held by the Stop hook until every question was
  answered, so answers typed into its pane sat queued behind the hook. The Stop hook no
  longer holds the turn when the answer can be typed into a pane; that typed answer wakes
  the agent. In a plain terminal it now lets go at the first answer, not the last.