Repository navigation
[FEATURE]: Skills invocation persistence and rehydration #396
Description
Activity
- added a parent issue
on Jul 22, 2026 @justintime4tea is this one blocked or done?
- added 8 commits that reference this issue
on Sep 10, 2026 - added 4 commits that reference this issue
on Sep 25, 2026
Summary
Without session storage we don't have a good way to track what skills have been activated per session - they live in bounds of a single request and die with that thread. This creates a frustrating continuity problem as subsequent users turns have no idea what skills have already fired and loose context. This change adds a skills model to a session that can live in our session persistance backend. Skills fire and their position in conversation history is tracked and re-inserted on the next turn.
Additional Context
No response
Upload screenshots
No response
Searched Issues
Code of Conduct