Changelog — Fixes

Bug fixes and regressions resolved. — Page 3

All Releases Features Fixes Improvements

fixApril 14, 2026

CodePulse v2.3.93 — Replay Count Reset Before Follow-Up

The replay count is now reset before follow-up execution, eliminating a 30-second timeout that could occur when chaining multiple follow-up tasks.

Bug Fixes (TAB-578)

Reset replay count before follow-up execute — When chaining multiple follow-up tasks on the same session, the replay counter accumulated from previous executions. Once it hit the threshold, a 30-second safety timeout kicked in, making the next follow-up appear to hang. The counter is now reset to zero before each follow-up execution.

fixApril 14, 2026

CodePulse v2.3.92 — Stop Hook Active Shown as Status Cards

stop_hook_active messages now display as visual status cards on Telegram instead of being suppressed, giving clear feedback that a task stop is in progress.

Bug Fixes (TAB-577)

Status card for stop_hook_active — The stop_hook_active signal was being forwarded to the bridge but not rendered visually. It now generates a status card on Telegram showing "Stopping task..." with the task name, giving the user clear feedback that the stop request was received and is being processed.

fixApril 14, 2026

CodePulse v2.3.91 — Forward stop_hook_active to Bridge

The stop_hook_active signal is now forwarded to the bridge instead of being blanket-suppressed, allowing the Telegram UI to show accurate task state.

Bug Fixes (TAB-577)

Forward stop_hook_active to bridge — Previously, stop_hook_active signals were silently suppressed, meaning the Telegram UI had no way to know a stop was in progress. The signal is now forwarded to the bridge, which can update the task card to reflect the stopping state.

fixApril 14, 2026

CodePulse v2.3.90 — UTF-8 Encoding for Stop POST Body

The Stop hook POST body is now encoded as UTF-8 bytes, fixing emoji corruption when stopping tasks via the HTTP transport layer.

Bug Fixes

UTF-8 Stop POST body — The Stop hook was sending its HTTP POST body without explicit UTF-8 encoding, causing emoji characters in stop reasons and status messages to arrive corrupted at the bridge. The body is now encoded as UTF-8 bytes with the correct Content-Type charset header.

fixApril 13, 2026

CodePulse v2.3.89 — Non-Delegate Auto-Allow Notifications

Non-delegate auto-allows now send a notification and record a learning entry, ensuring consistent audit trail and user feedback across all session types.

Bug Fixes (TAB-573)

Notification + learning for non-delegate auto-allows — When a non-delegate session auto-allowed a tool call, neither a notification was sent nor a learning entry recorded. Both paths are now wired in, ensuring the audit trail and user feedback are consistent regardless of session type.

fixApril 13, 2026

CodePulse v2.3.88 — Auto-Approve Notifications Restored

Auto-approve notifications for interactive terminal sessions are restored. Users now see feedback when tool calls are automatically approved in the terminal.

Bug Fixes (TAB-573)

Auto-approve notifications restored — The interactive terminal was silently auto-approving tool calls without any user-visible feedback after the deferred approval changes. Restored the notification path so the terminal shows a brief status line when a tool call is auto-approved by permission rules.

fixApril 13, 2026

CodePulse v2.3.87 — Skip Wait Quietly for Non-Delegate Sessions

The Wait Quietly suppression logic now skips non-delegate (interactive terminal) sessions, restoring normal tool call output in the terminal.

Bug Fixes (TAB-573)

Wait Quietly bypass for interactive sessions — The "Wait Quietly" suppression feature (which hides repetitive tool call output during delegate tasks) was incorrectly activating for interactive terminal sessions, causing the terminal to appear frozen during long operations. Non-delegate sessions now skip Wait Quietly entirely.

fixApril 13, 2026

CodePulse v2.3.86 — UTF-8 Stdin Encoding Fix

Set UTF-8 encoding on stdin to fix emoji and Unicode corruption on Telegram cards. Characters like checkmarks and arrows now render correctly.

Bug Fixes

UTF-8 stdin encoding — The Node.js process stdin was using the system default encoding (often latin1 on Windows), which corrupted emoji and Unicode characters in Telegram card content. Explicitly set process.stdin.setEncoding('utf8') at startup to ensure all incoming text is decoded correctly.

fixApril 13, 2026

CodePulse v2.3.84 — Non-Delegate Guard Moved Above TCVF

The non-delegate session guard now runs before the TCVF pipeline, ensuring interactive terminal sessions skip the entire approval flow without side effects.

Bug Fixes (TAB-573)

Guard priority fix — The non-delegate session check was positioned after the TCVF (Tool Call Verification Framework) entry point, meaning interactive sessions still went through initial TCVF processing before being auto-allowed. Moved the guard above TCVF so interactive sessions exit the pipeline immediately with zero overhead.

fixApril 13, 2026

CodePulse v2.3.83 — Auto-Allow for Non-Delegate Sessions

Non-delegate sessions now auto-allow tool calls instead of holding the HTTP connection, preventing the interactive terminal from blocking on bridge approval.

Bug Fixes (TAB-573)

Auto-allow non-delegate sessions — When the bridge received a hook event from a non-delegate (interactive terminal) session, it was holding the HTTP connection open waiting for Telegram approval that would never come. Non-delegate sessions now immediately return an "allow" response, preventing the interactive terminal from freezing.

Bug Fixes (TAB-578)

Reset replay count before follow-up execute — When chaining multiple follow-up tasks on the same session, the replay counter accumulated from previous executions. Once it hit the threshold, a 30-second safety timeout kicked in, making the next follow-up appear to hang. The counter is now reset to zero before each follow-up execution.

Bug Fixes (TAB-577)

Status card for stop_hook_active — The stop_hook_active signal was being forwarded to the bridge but not rendered visually. It now generates a status card on Telegram showing "Stopping task..." with the task name, giving the user clear feedback that the stop request was received and is being processed.

Bug Fixes (TAB-573)

Auto-approve notifications restored — The interactive terminal was silently auto-approving tool calls without any user-visible feedback after the deferred approval changes. Restored the notification path so the terminal shows a brief status line when a tool call is auto-approved by permission rules.

Bug Fixes (TAB-573)

Wait Quietly bypass for interactive sessions — The "Wait Quietly" suppression feature (which hides repetitive tool call output during delegate tasks) was incorrectly activating for interactive terminal sessions, causing the terminal to appear frozen during long operations. Non-delegate sessions now skip Wait Quietly entirely.

Bug Fixes (TAB-573)

Guard priority fix — The non-delegate session check was positioned after the TCVF (Tool Call Verification Framework) entry point, meaning interactive sessions still went through initial TCVF processing before being auto-allowed. Moved the guard above TCVF so interactive sessions exit the pipeline immediately with zero overhead.

Bug Fixes (TAB-573)

Auto-allow non-delegate sessions — When the bridge received a hook event from a non-delegate (interactive terminal) session, it was holding the HTTP connection open waiting for Telegram approval that would never come. Non-delegate sessions now immediately return an "allow" response, preventing the interactive terminal from freezing.