docs: Add bug report for VSCode extension installation regression

Documents the "1: 1" error that occurs when using /ide command
in Homespace environments. The error appears to be caused by
incorrect parsing of subprocess execution results where the
error field receives the exit code instead of the actual error
message from stderr.

Includes:
- Root cause analysis of the error pattern
- Timeline of when the regression was introduced
- Temporary workaround for affected users
- Required fix description

Slack: https://anthropic.slack.com/archives/C07VBSHV7EV/p1765922691961929

CHANGELOG.md

@@ -1,8 +1,36 @@
 # Changelog
 
+## 2.0.70
+
+- Added Enter key to accept and submit prompt suggestions immediately (tab still accepts for editing)
+- Added wildcard syntax `mcp__server__*` for MCP tool permissions to allow or deny all tools from a server
+- Added auto-update toggle for plugin marketplaces, allowing per-marketplace control over automatic updates
+- Added `plan_mode_required` spawn parameter for teammates to require plan approval before implementing changes
+- Added `current_usage` field to status line input, enabling accurate context window percentage calculations
+- Fixed input being cleared when processing queued commands while the user was typing
+- Fixed prompt suggestions replacing typed input when pressing Tab
+- Fixed diff view not updating when terminal is resized
+- Improved memory usage by 3x for large conversations
+- Improved resolution of stats screenshots copied to clipboard (Ctrl+S) for crisper images
+- Removed # shortcut for quick memory entry (tell Claude to edit your CLAUDE.md instead)
+- Fix thinking mode toggle in /config not persisting correctly
+- Improve UI for file creation permission dialog
+
+## 2.0.69
+
+- Minor bugfixes
+
+## 2.0.68
+
+- Fixed IME (Input Method Editor) support for languages like Chinese, Japanese, and Korean by correctly positioning the composition window at the cursor
+- Fixed a bug where disallowed MCP tools were visible to the model
+- Fixed an issue where steering messages could be lost while a subagent is working
+- Fixed Option+Arrow word navigation treating entire CJK (Chinese, Japanese, Korean) text sequences as a single word instead of navigating by word boundaries
+- Improved plan mode exit UX: show simplified yes/no dialog when exiting with empty or missing plan instead of throwing an error
+- Add support for enterprise managed settings. Contact your Anthropic account team to enable this feature.
+
 ## 2.0.67
 
-- Claude now suggests prompts to speed up your workflow: press Tab to accept or Enter to submit
 - Thinking mode is now enabled by default for Opus 4.5
 - Thinking mode configuration has moved to /config
 - Added search functionality to `/permissions` command with `/` keyboard shortcut for filtering rules by tool name

docs/bugs/vscode-extension-regression-1-1-error.md

@@ -0,0 +1,81 @@
+# VSCode Extension Installation Regression: "1: 1" Error
+
+**Reported**: 2025-12-16
+**Status**: Under Investigation
+**Slack Thread**: https://anthropic.slack.com/archives/C07VBSHV7EV/p1765922691961929?thread_ts=1765922103.768169&cid=C07VBSHV7EV
+
+## Description
+
+Users are unable to use the VSCode IDE integration when running Claude Code in a Homespace (containerized environment). The `/ide` command initially reports success, but a few seconds later an error appears.
+
+### Error Message
+
+```
+IDE: ✘ Error installing VS Code extension: 1: 1
+      Please restart your IDE and try again.
+```
+
+## Steps to Reproduce
+
+1. Run Claude Code in a Homespace environment
+2. Execute `/ide` command
+3. Observe initial success message
+4. Wait a few seconds - error popup appears
+5. Run `/status` to confirm the error
+
+## Root Cause Analysis
+
+### Error Pattern Analysis
+
+The error message `1: 1` follows the pattern from the extension installation error handling:
+
+```javascript
+throw Error(`${result.code}: ${result.error} ${result.stderr}`)
+```
+
+For "1: 1" to appear, the values must be:
+- `result.code` = 1 (exit code from VS Code CLI)
+- `result.error` = "1" (incorrectly set to the exit code instead of error message)
+- `result.stderr` = "" (empty)
+
+### Regression Hypothesis
+
+The async execution result object is incorrectly populating the `error` field with the numeric exit code instead of the actual error message from stderr. This appears to be a regression in subprocess output parsing.
+
+### Timeline
+
+- **Working**: Last week (user confirmed)
+- **Broken**: Current version (2.0.59+)
+- **Likely introduced**: Between versions 2.0.59-2.0.70
+
+## Environment
+
+- Running in Homespace (containerized environment)
+- VSCode Remote development setup
+
+## Temporary Workaround
+
+If experiencing this issue, try:
+
+1. Manually install the Claude Code extension in VS Code:
+   - Open VS Code Command Palette (Ctrl+Shift+P / Cmd+Shift+P)
+   - Type "Extensions: Install Extension"
+   - Search for "Claude Code" (by Anthropic)
+   - Install manually
+
+2. After manual installation, restart your IDE and try `/ide` again
+
+## Related Changes in CHANGELOG
+
+Potentially relevant recent changes:
+- 2.0.64: VSCode: Fixed extension not working on Windows ARM64
+- 2.0.62: Fixed IDE diff tab not closing when rejecting file changes
+- 2.0.61: Reverted VSCode support for multiple terminal clients
+- 2.0.60: VSCode: Added support for multiple terminal clients
+- 2.0.59: VS Code: Fixed .claude.json config file being read from incorrect location
+
+## Fix Required
+
+The fix needs to address how subprocess execution results are parsed, specifically ensuring that:
+1. The `error` field contains the actual error message (from stderr), not the exit code
+2. Proper error handling for when VS Code CLI fails in containerized environments

plugins/code-review/README.md

@@ -22,23 +22,29 @@ Performs automated code review on a pull request using multiple specialized agen
    - **Agent #4**: Analyze git blame/history for context-based issues
 5. Scores each issue 0-100 for confidence level
 6. Filters out issues below 80 confidence threshold
-7. Posts review comment with high-confidence issues only
+7. Outputs review (to terminal by default, or as PR comment with `--comment` flag)
 
 **Usage:**
 ```bash
-/code-review
+/code-review [--comment]
 ```
 
+**Options:**
+- `--comment`: Post the review as a comment on the pull request (default: outputs to terminal only)
+
 **Example workflow:**
 ```bash
-# On a PR branch, run:
+# On a PR branch, run locally (outputs to terminal):
 /code-review
 
+# Post review as PR comment:
+/code-review --comment
+
 # Claude will:
 # - Launch 4 review agents in parallel
 # - Score each issue for confidence
-# - Post comment with issues ≥80 confidence
-# - Skip posting if no high-confidence issues found
+# - Output issues ≥80 confidence (to terminal or PR depending on flag)
+# - Skip if no high-confidence issues found
 ```
 
 **Features:**
@@ -114,17 +120,23 @@ This plugin is included in the Claude Code repository. The command is automatica
 ### Standard PR review workflow:
 ```bash
 # Create PR with changes
+# Run local review (outputs to terminal)
 /code-review
 
 # Review the automated feedback
 # Make any necessary fixes
+
+# Optionally post as PR comment
+/code-review --comment
+
 # Merge when ready
 ```
 
 ### As part of CI/CD:
 ```bash
 # Trigger on PR creation or update
-# Automatically posts review comments
+# Use --comment flag to post review comments
+/code-review --comment
 # Skip if review already exists
 ```
 

plugins/code-review/commands/code-review.md

@@ -52,7 +52,9 @@ Note: Still review Claude generated PR's.
 
 6. Filter out any issues that were not validated in step 5. This step will give us our list of high signal issues for our review.
 
-7. Finally, comment on the pull request.
+7. Finally, output the review.
+   - If the `--comment` argument is provided, post the review as a comment on the pull request using `gh pr comment`
+   - Otherwise (default), output the review directly to the terminal for local viewing
    When writing your comment, follow these guidelines:
    a. Keep your output brief
    b. Avoid emojis