Changelog

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

All Releases Features Fixes Improvements

fixApril 14, 2026

CodePulse v2.3.97 — UltraPlan URL Regex Hardening

Hardened URL extraction regexes in UltraPlan, eliminated a double card edit race condition, and added a runtime guard against malformed plan responses.

Bug Fixes (TAB-580)

URL regex hardening — The regexes that extract URLs from Claude's plan responses were too greedy, matching partial URLs and markdown syntax as part of the URL. Tightened the patterns to correctly handle parentheses, query strings, and fragment identifiers.
Double card edit race eliminated — When a plan response arrived while a previous card edit was still in flight, both edits could land out of order, showing stale content. Added a serialization queue for card edits.
Runtime guard for malformed plans — Added validation for the plan response structure before attempting to render a card. Malformed responses now show a clear error card instead of crashing the card renderer.

featureApril 14, 2026

CodePulse v2.3.96 — UltraPlan Phase 2: Teleport & Auto-Execute

UltraPlan plans can now teleport back to your terminal and auto-execute. Tap Execute on the plan card, and the task starts on your local machine automatically.

New Features (TAB-580, Phase 2)

Plan teleportation — When you tap Execute on an UltraPlan card, the plan is teleported to your local terminal via the bridge. The CLI receives the plan context and starts execution with full local file access, git integration, and tool permissions.
Auto-execute — After teleportation, execution begins automatically without requiring a second confirmation. The Telegram card updates in real-time to show execution progress.

featureApril 14, 2026

CodePulse v2.3.95 — /ultraplan: Cloud Planning from Telegram

New /ultraplan command enables cloud-based planning directly from Telegram. Send a task description and get a full implementation plan generated by Claude Opus in the cloud.

New Features (TAB-580, Phase 1)

/ultraplan command — Send /ultraplan <task description> from Telegram to generate a detailed implementation plan using Claude Opus in the cloud. The plan is generated without needing a local CLI session, making it accessible from anywhere — your phone, tablet, or any device with Telegram. The plan card shows phases, file changes, and estimated complexity, with an Execute button to kick off the task.

fixApril 14, 2026

CodePulse v2.3.94 — Stop Reply Window Expiry Notification

Users are now notified when the stop reply window expires instead of the stop request being silently dropped. Prevents confusion when stop timing overlaps with task completion.

Bug Fixes (TAB-576)

Stop reply window expiry notification — When a user tapped Stop but the reply window had already expired (e.g., the task finished between the tap and the server processing), the stop request was silently dropped. The bridge now sends a notification explaining that the task already completed, preventing user confusion about whether the stop was received.

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.

Bug Fixes (TAB-580)

URL regex hardening — The regexes that extract URLs from Claude's plan responses were too greedy, matching partial URLs and markdown syntax as part of the URL. Tightened the patterns to correctly handle parentheses, query strings, and fragment identifiers.

Double card edit race eliminated — When a plan response arrived while a previous card edit was still in flight, both edits could land out of order, showing stale content. Added a serialization queue for card edits.

Runtime guard for malformed plans — Added validation for the plan response structure before attempting to render a card. Malformed responses now show a clear error card instead of crashing the card renderer.

New Features (TAB-580, Phase 2)

Plan teleportation — When you tap Execute on an UltraPlan card, the plan is teleported to your local terminal via the bridge. The CLI receives the plan context and starts execution with full local file access, git integration, and tool permissions.

Auto-execute — After teleportation, execution begins automatically without requiring a second confirmation. The Telegram card updates in real-time to show execution progress.

New Features (TAB-580, Phase 1)

/ultraplan command — Send /ultraplan <task description> from Telegram to generate a detailed implementation plan using Claude Opus in the cloud. The plan is generated without needing a local CLI session, making it accessible from anywhere — your phone, tablet, or any device with Telegram. The plan card shows phases, file changes, and estimated complexity, with an Execute button to kick off the task.

Bug Fixes (TAB-576)

Stop reply window expiry notification — When a user tapped Stop but the reply window had already expired (e.g., the task finished between the tap and the server processing), the stop request was silently dropped. The bridge now sends a notification explaining that the task already completed, preventing user confusion about whether the stop was received.

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.