Changelog — Features

New capabilities added to CodePulse. — Page 2

All Releases Features Fixes Improvements

featureApril 15, 2026

CodePulse v2.3.103 — UltraPlan raw keyword detection test

Experimental change to UltraPlan keyword detection — drops XML wrapping and plan mode to test whether raw keyword parsing improves cloud-session routing.

UltraPlan (TAB-580)

Raw keyword detection experiment — UltraPlan no longer wraps the user's prompt in XML tags and no longer enters plan mode before routing. This release tests whether the LLM reliably picks up "ultraplan" keywords from the raw message body alone, which would simplify the execution path and remove an entire layer of prompt plumbing. Rolled back in v2.3.104 after the cloud-session path was found to lack a required --remote flag.

featureApril 14, 2026

CodePulse v2.3.99 — UltraPlan Phase 3: Cloud Execution + PR Cards

UltraPlan now detects cloud execution completion and shows a PR notification card with a direct link when the task creates or updates a pull request.

New Features (TAB-580, Phase 3)

Cloud execution detection — UltraPlan monitors the CLI session for completion signals. When the task finishes, the Telegram card updates automatically from "Executing..." to a completion summary with the number of files changed and a brief description of what was done.
PR notification card — If the executed task creates or updates a pull request, a dedicated PR card appears with the PR title, branch name, and a direct link to the PR on GitHub. This closes the loop from planning to PR without leaving Telegram.

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.

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.

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.

featureApril 13, 2026

CodePulse v2.3.77 — Tool Deferred Handling + Auto-Resume

The CLI framework now handles the tool_deferred state natively. When a deferred approval is resolved via Telegram, the CLI auto-resumes execution seamlessly.

New Features (TAB-571)

tool_deferred handling in CLI framework — Added a new tool_deferred state to the CLI's hook response protocol. When the bridge returns a defer signal, the CLI parks the tool call and enters a polling loop waiting for the resolution signal. On approval, execution resumes exactly where it left off with no re-planning or context loss.
Auto-resume signal path — The bridge posts a resume notification to the CLI's local HTTP endpoint when the user responds to a deferred approval card. The CLI picks up the signal within 1–2 seconds and continues execution.

featureApril 13, 2026

CodePulse v2.3.76 — Defer Approval Support in Bridge Server

The bridge server now supports deferred approvals behind a feature flag. Tool calls can be paused and resumed via Telegram without blocking the CLI process.

New Features (TAB-570)

Defer approval support in bridge server — When a tool call requires approval and the feature flag is enabled, the bridge server responds with a defer signal instead of holding the HTTP connection open. The CLI pauses execution locally, and the Telegram bot shows an approval card. When the user approves or denies, a resume signal is sent back to the CLI via the bridge. This eliminates the HTTP timeout risk for long approval waits.

featureApril 13, 2026

CodePulse v2.3.75 — Defer Response Infrastructure

New defer response types, builders, and adapter lay the groundwork for deferred tool approvals — letting the CLI pause execution while waiting for Telegram approval.

New Features (TAB-569)

Defer response infrastructure — Added the foundational types (DeferResponse, DeferResult), builder functions (buildDeferResponse, buildDeferResult), and a DeferAdapter that translates between the CLI's hook protocol and the bridge's deferred approval flow. This is Phase 1 of the deferred approval feature — the infrastructure layer that subsequent releases build on.

featureApril 12, 2026

CodePulse v2.3.71 — Visual Plan Source Indicators

Plan cards now show whether the plan was generated by AI Preview (fast Haiku) or Full Analysis (Opus), so you know the depth of reasoning behind each plan.

New Features

Plan source indicators on cards — Each plan card now displays a badge showing its generation source: "AI Preview" for fast Haiku-generated plans or "Full Analysis" for plans produced by Opus with full codebase context. This helps you decide whether to approve immediately or request a deeper analysis before execution.