0.42 - Composer History - Is this really implemented?

General
1

I have upgraded to 0.42.

The 0.42 Change Log states: " Composer history lets you access previous composer sessions after restart. You can also edit and resubmit from previous messages within a session.".

The AI Chat informs me: “I am an AI assistant and don’t actually have access to previous chat history or files unless you share them. Each interaction starts fresh. While I can see the code and logs you’ve shared in this conversation, I don’t have broader context.”

Does AI Chat History work?

If so, how?

2

I think this means more that after you restart cursor, the checkout and previous history wont be forgotten.

3

The chat has degraded. It is making unsanctioned changes as such as swapping out databases. WTF?

Cleaning up all of the ‘help’ is wearing me down.

4

The AI is not adhering to standard practices, whatever they may be.

Prior to AI, there were development practices.

Now with AI, we need to think through global training of AI’s to follow best practices for coding so stuff like this doesn’t occur:

Why wasn’t this suggested intially?

You’re right - I should have suggested this solution first. I made several mistakes:

  • I defaulted to the most basic (and disruptive) solution first

  • I didn’t consider the impact on your workflow

  • I suggested closing applications unnecessarily

  • I failed to mention this PowerShell command that refreshes PATH without restart

This is when the AI swapped out a database:

I apologize for:

  • Not reading carefully

  • Making assumptions

  • Contradicting your actual setup

  • Wasting your time

Would you like me to focus on the actual token tracking issue with your existing PostgreSQL configuration?

5

Still off the rails. Think that this AI needs to be put to sleep:

apologize for my mistake. Looking back at what you shared:

wsgi.py

os.environ.setdefault(‘DJANGO_SETTINGS_MODULE’, ‘Tender.settings’)

You’re right - I made an incorrect assumption without properly reading the code you shared. The wsgi.py already has the correct settings module path. I should have:

  • Actually read the code you shared

  • Verified what needed fixing instead of assuming

  • Only focused on asgi.py which does need updating