Skip to content

v0.4.0 - URGENT: Fix /enhance Broken XML Output

Choose a tag to compare

View all tags
@ramakay ramakay released this 21 Jul 14:00
· 11 commits to main since this release
v0.4.0
f6a89cb

🚨 Urgent Fix

This release fixes the broken XML output issue where /enhance was generating plans with literal \n characters and unreadable formatting.

The Problem

The previous fix (v0.3.9) told Claude to escape all newlines as \n, which caused the exit_plan_mode to display raw escape sequences instead of formatted text. This made plans unreadable with content like:

│ │ \n\n\n\n<applicable_rules context=file-operations, testing, code-quality>\n- ALWAYS prefer │

The Solution

  • Complete rewrite of the /enhance command
  • exit_plan_mode expects FORMATTED text with real newlines, not escaped strings
  • Removed all conflicting instructions about escaping
  • Updated all examples to show proper multi-line formatting

What Changed

  • ✅ Use actual newlines in the plan content
  • ✅ Keep XML tags as plain text (they display correctly)
  • ✅ No more escape sequences
  • ✅ Readable, properly formatted output

For Users

The /enhance command will now generate properly formatted, readable plans instead of showing escape sequences. Just update to v0.4.0 and the issue will be resolved.

Breaking Change

This is technically a breaking change from v0.3.9, but v0.3.9 was broken, so this fixes it to work as originally intended.

Assets 2
Loading