[email protected]andClaude Opus 4.6 4e8b94a555 fix(engine): persist conversation context across messages ...

The engine was creating a fresh ThreadManager and InMemoryStore per
message, losing all context between turns. A follow-up question like
"what are the latest 10 issues?" had no memory of the prior "how many
issues" response.

Fixes:
- EngineState (ThreadManager, ConversationManager, InMemoryStore) now
  persists across messages via OnceLock, initialized on first use
- ConversationManager builds message history from prior conversation
  entries (user messages + agent responses) and passes it to new threads
- ThreadManager.spawn_thread_with_history() accepts initial_messages
  that are prepended before the current user message
- System notifications (thread started/completed) are filtered out of
  the history (not useful as LLM context)

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

2026-03-22 01:08:05 -07:00

..

ironclaw_engine

fix(engine): persist conversation context across messages

2026-03-22 01:08:05 -07:00

ironclaw_safety

perf(safety): single-pass escape_xml_attr (#1028)

2026-03-20 20:33:09 -07:00