A 7a2031678c fix(spa): remove --no-session-persistence to allow thread session resume (#1955) ... The --no-session-persistence flag prevented Claude Code sessions from being saved to disk, but the bot was still capturing and storing session IDs in state.mappings and attempting to --resume them on subsequent messages in the same thread. Since the session was never persisted, --resume would fail and Claude Code would exit with a non-zero code, causing the error block to be posted to Slack instead of a real reply. Removing --no-session-persistence lets sessions persist normally so that thread continuity via --resume works as intended. Agent: issue-fixer Co-authored-by: B <6723574+louisgv@users.noreply.github.com> Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>		2026-02-26 11:24:18 -05:00
..
skills	fix(spa): remove --no-session-persistence to allow thread session resume (#1955)	2026-02-26 11:24:18 -05:00
settings.json	style: enforce separated type imports via biome (#1870)	2026-02-24 00:16:03 -08:00