[Feature Request] Persistent project context for virtual environments and repeated patterns

Resolved 💬 2 comments Opened Jun 4, 2026 by mashmool0 Closed Jun 8, 2026

Bug Description
Claude makes mistakes in the same repeated processes. For example, in a project with a virtual environment, such as a Django project, you need to activate the virtual environment before running commands like migrations or runserver.

However, Claude often makes the same mistake every time. It first tries using python, then python3, and only afterward tries activating the virtual environment. It repeats this pattern again and again.

I think Claude should remember important project-specific details, even if you clear the session, as long as you're working in the same directory. Things like the existence of a virtual environment should be treated as persistent context rather than something it has to rediscover every time.

Environment Info

  • Platform: linux
  • Terminal: gnome-terminal
  • Version: 2.1.161
  • Feedback ID: de11d893-59f3-4d50-97b9-150eb28fa71c

Errors

[]

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗