[BUG] Add nano editor to devcontainer - Required for /memory command

Resolved 💬 1 comment Opened Jun 15, 2025 by Masa1984a Closed Jul 28, 2025

Environment

  • Platform (select one):
  • [x] Anthropic API
  • [ ] AWS Bedrock
  • [ ] Google Vertex AI
  • Claude CLI version: 1.0.24
  • Operating System: Windows 11
  • Terminal: PowerShell / VS Code Terminal

Bug Description

The /memory command fails in Claude Code when running inside the devcontainer because the nano editor is not included in the Docker image. This prevents users from being able to edit memory files, which is a core functionality of the /memory feature.

Steps to Reproduce

  1. Build and run Claude Code devcontainer using the provided Dockerfile
  2. Inside the container, execute the /memory command in Claude Code
  3. The command fails with "nano: command not found" error

Expected Behavior

The /memory command should successfully open the nano editor, allowing users to view and edit memory files.

Actual Behavior

The command fails with an error message indicating that nano is not installed, preventing the memory editing functionality from working.

Additional Context

Workaround: Users can manually install nano with sudo apt update && sudo apt install nano, but this needs to be done every time the container is rebuilt.

Proposed fix: Add nano to the apt packages list in the Dockerfile at line 4:

RUN apt update && apt install -y less \
  git \
  procps \
  sudo \
  fzf \
  zsh \
  man-db \
  unzip \
  gnupg2 \
  gh \
  iptables \
  ipset \
  iproute2 \
  dnsutils \
  aggregate \
  jq \
  nano  # <- Add this line

This is a minimal change that would significantly improve the developer experience when using Claude Code in the devcontainer environment.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗