Changelog

Release history — all CodePulse updates in one place - Page 6

All Releases Features Fixes Improvements

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.

featureApril 13, 2026

CodePulse v2.3.85 — Smart Continuation for Follow-Up Messages

Follow-up messages now auto-resume the most recent CLI session instead of starting fresh. Claude keeps full context from the previous task, making corrections instant.

New Features (TAB-575)

Smart continuation — When you send a follow-up message shortly after a task completes, the bot automatically resumes the same CLI session via --resume. Claude retains full context — files it changed, reasoning it used, and tools it called — so corrections and follow-ups land in context without re-planning. If the previous session has expired or been cleaned up, a new session starts automatically as a fallback.

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.

fixApril 13, 2026

CodePulse v2.3.82 — Defer Only Delegate-Spawned Sessions

Deferred approvals now only activate for delegate-spawned sessions. Interactive terminal sessions skip the defer pipeline entirely, preventing unexpected pauses.

Bug Fixes (TAB-573)

Delegate session scoping — The deferred approval pipeline was incorrectly activating for interactive terminal sessions (started via codepulse directly), causing the terminal to pause and wait for Telegram approval on every tool call. Added a session-type check so only delegate-spawned sessions (triggered via Telegram) enter the defer flow.

fixApril 13, 2026

CodePulse v2.3.81 — Defer Response Includes hookEventName

Added the missing hookEventName field to defer responses. The CLI requires this field to correctly honor the defer signal and pause execution.

Bug Fixes (TAB-573)

hookEventName added to defer response — The CLI's hook protocol requires a hookEventName field on every response to identify which hook event is being answered. The defer response builder was omitting this field, causing the CLI to ignore the defer signal and fall through to the default "allow" behavior. Now included on all defer responses.

fixApril 13, 2026

CodePulse v2.3.80 — Defer Key Fits Telegram Callback Limit

Shortened the deferKey format to fit within Telegram's 64-byte callback data limit, fixing approval buttons that silently failed on long session IDs.

Bug Fixes (TAB-573)

DeferKey shortened for Telegram — Telegram enforces a strict 64-byte limit on callback query data. The original deferKey format included the full session ID and tool call ID, often exceeding this limit. Shortened to a compact hash-based key that fits comfortably within 64 bytes while remaining collision-resistant.

fixApril 13, 2026

CodePulse v2.3.79 — Deferred Approval Edge Case Handling

Handles deferred approval edge cases: session expiry cards, permissionMode compatibility, and an eviction guard to prevent stale deferred entries from leaking memory.

Bug Fixes (TAB-573)

Session expiry card — When a deferred approval's backing CLI session is terminated before the user responds, the system now detects the dead session and updates the Telegram card with an expiry notice instead of leaving it in a "waiting" state forever.
Permission mode compatibility — Deferred approvals now respect the session's permissionMode setting, ensuring that auto-approve rules are checked before deferring.
Eviction guard — A TTL-based eviction mechanism cleans up deferred entries that were never resolved, preventing memory leaks in long-running bridge processes.

featureApril 13, 2026

CodePulse v2.3.78 — Deferred Approval Card UX

New Telegram card UX for deferred approvals: a paused indicator while waiting, resume feedback on approval, and a clear error card if the session expires.

New Features (TAB-572)

Paused indicator on deferred approval cards — When a tool call is deferred, the Telegram card shows a visual "Paused" state with the tool name and a brief description of what's waiting for approval. The user sees exactly what will happen before tapping Allow or Deny.
Resume feedback — After approving a deferred tool call, the card updates to show "Resumed" with a timestamp, confirming that the CLI picked up the signal and continued execution.
Session expiry error card — If the deferred session expires before the user responds (e.g., CLI was stopped), the card updates to show an expiry message instead of silently failing.

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.

New Features (TAB-575)

Smart continuation — When you send a follow-up message shortly after a task completes, the bot automatically resumes the same CLI session via --resume. Claude retains full context — files it changed, reasoning it used, and tools it called — so corrections and follow-ups land in context without re-planning. If the previous session has expired or been cleaned up, a new session starts automatically as a fallback.

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.

Bug Fixes (TAB-573)

Delegate session scoping — The deferred approval pipeline was incorrectly activating for interactive terminal sessions (started via codepulse directly), causing the terminal to pause and wait for Telegram approval on every tool call. Added a session-type check so only delegate-spawned sessions (triggered via Telegram) enter the defer flow.

Bug Fixes (TAB-573)

hookEventName added to defer response — The CLI's hook protocol requires a hookEventName field on every response to identify which hook event is being answered. The defer response builder was omitting this field, causing the CLI to ignore the defer signal and fall through to the default "allow" behavior. Now included on all defer responses.

Bug Fixes (TAB-573)

DeferKey shortened for Telegram — Telegram enforces a strict 64-byte limit on callback query data. The original deferKey format included the full session ID and tool call ID, often exceeding this limit. Shortened to a compact hash-based key that fits comfortably within 64 bytes while remaining collision-resistant.

Bug Fixes (TAB-573)

Session expiry card — When a deferred approval's backing CLI session is terminated before the user responds, the system now detects the dead session and updates the Telegram card with an expiry notice instead of leaving it in a "waiting" state forever.

Permission mode compatibility — Deferred approvals now respect the session's permissionMode setting, ensuring that auto-approve rules are checked before deferring.

Eviction guard — A TTL-based eviction mechanism cleans up deferred entries that were never resolved, preventing memory leaks in long-running bridge processes.

New Features (TAB-572)

Paused indicator on deferred approval cards — When a tool call is deferred, the Telegram card shows a visual "Paused" state with the tool name and a brief description of what's waiting for approval. The user sees exactly what will happen before tapping Allow or Deny.

Resume feedback — After approving a deferred tool call, the card updates to show "Resumed" with a timestamp, confirming that the CLI picked up the signal and continued execution.

Session expiry error card — If the deferred session expires before the user responds (e.g., CLI was stopped), the card updates to show an expiry message instead of silently failing.