namirsab

Love it! Really cool idea!

This seems to keep happening, I just had a situation were Claude told me to try a thing, I tried, it didn't work, then It told me to try another thing, I tried, it didn't work, and finally it asked me again to try the first thing again, as if we never tested it before, even though it was in the context from 3 messages ago.

It doesn't use MCP servers when it should and it's also not taking memory files into account.

This is happening with /effort high and in really simple tasks... :(

I asked Claude to do a check of the project memory and it is really confident that this was caused by some server side issue. You can see it here:

https://gist.github.com/namirsab/d6acb1e949d024811df4d2d8ad6...

Hey, WeaselsWin is my colleague and i'm the one who had this weird hallucination. I was in plan mode and i confirmed the plan and suddenly Claude Code started outputting text about completely different topics and hallucinating like this:

see that the database system is already quite well understood in the instructions. Let me provide a brief summary:

  Understanding the Mission System                                                                                                                                   
                                         
  The mission system consists of several interconnected components that work together to manage tasks:                                                               
                                                                                                                                                                     
  Key Components

  ┌─────────────────────────┬─────────────────────────────────────────────────────────────────────────────────────────┐
  │        Component        │                                       Description                                       │
  ├─────────────────────────┼─────────────────────────────────────────────────────────────────────────────────────────┤
  │ Database (Total)        │ A persistent storage layer that maintains the full record of all tasks and their states │
  ├─────────────────────────┼─────────────────────────────────────────────────────────────────────────────────────────┤
  │ Mission Active (active) │ A real-time view of currently running/pending missions                                  │
  ├─────────────────────────┼─────────────────────────────────────────────────────────────────────────────────────────┤
  │ Mission Service         │ Core service managing mission lifecycle (create, update, complete)                      │
  ├─────────────────────────┼─────────────────────────────────────────────────────────────────────────────────────────┤
  │ Mission Calendar        │ Scheduling system for time-based mission planning                                       │
  └─────────────────────────┴─────────────────────────────────────────────────────────────────────────────────────────┘

  How They Interact

  1. Mission Service creates and manages missions through their lifecycle
  2. Database stores all mission data persistently
  3. Active missions are tracked separately for quick access to current work
  4. Calendar provides scheduling capabilities for future missions

  Status Flow

  Created → Active → In Progress → Completed
                   ↘ Cancelled


  The system ensures data consistency across all components while maintaining efficient access patterns for both active and historical missions.


  Confirmation

  I've provided a comprehensive overview of how the mission system works. The existing documentation in the codebase already covers:

  - File structure and locations
  - Service interactions between components
  - Data flow from creation to completion
  - Error handling and edge cases

  Is there anything specific about the mission system you'd like me to elaborate on?

Thx! I still find weird they don't mention it at all in the article, but this is fair at least :)

I find weird they didn't mention excalidraw, or did I miss it?

It's clearly a fork, at least from the UI point of view