fix(chat): preserve activity folds across thread switches by Tryanks · Pull Request #301 · Tryanks/tcode

Tryanks · 2026-08-27T05:03:15Z

Root cause

Thread switches cleared the entire automatic activity-expansion state. When a running thread was revisited, every historical command and file edit had no remembered state, so each one took the first-seen path, reopened, and scheduled a fresh 500ms collapse.

Fix

retain automatic expansion state across thread switches
scope state by session so identical activity IDs cannot leak between threads
let inactive-session collapse timers settle their own state without remeasuring the currently visible thread
keep the newest activity behavior unchanged

Regression coverage

a collapsed activity stays collapsed after another session with the same activity ID is visited
a pending collapse only updates its originating session

Verification

cargo fmt --all --check
cargo clippy --workspace --all-targets --locked -- -D warnings
cargo test --workspace --locked

Thread switches cleared the entire auto-expansion state, so revisiting a running thread treated every historical activity as first-seen and reopened it for 500ms. Keep the state scoped by session instead, and prevent inactive-session timers from remeasuring the current thread.

Tryanks · 2026-08-27T05:03:15Z

Root cause

Thread switches cleared the entire automatic activity-expansion state. When a running thread was revisited, every historical command and file edit had no remembered state, so each one took the first-seen path, reopened, and scheduled a fresh 500ms collapse.

Fix

retain automatic expansion state across thread switches
scope state by session so identical activity IDs cannot leak between threads
let inactive-session collapse timers settle their own state without remeasuring the currently visible thread
keep the newest activity behavior unchanged

Regression coverage

a collapsed activity stays collapsed after another session with the same activity ID is visited
a pending collapse only updates its originating session

Verification

cargo fmt --all --check
cargo clippy --workspace --all-targets --locked -- -D warnings
cargo test --workspace --locked

Thread switches cleared the entire auto-expansion state, so revisiting a running thread treated every historical activity as first-seen and reopened it for 500ms. Keep the state scoped by session instead, and prevent inactive-session timers from remeasuring the current thread.

Tryanks · 2026-08-27T05:03:15Z

Root cause

Thread switches cleared the entire automatic activity-expansion state. When a running thread was revisited, every historical command and file edit had no remembered state, so each one took the first-seen path, reopened, and scheduled a fresh 500ms collapse.

Fix

retain automatic expansion state across thread switches
scope state by session so identical activity IDs cannot leak between threads
let inactive-session collapse timers settle their own state without remeasuring the currently visible thread
keep the newest activity behavior unchanged

Regression coverage

a collapsed activity stays collapsed after another session with the same activity ID is visited
a pending collapse only updates its originating session

Verification

cargo fmt --all --check
cargo clippy --workspace --all-targets --locked -- -D warnings
cargo test --workspace --locked

Thread switches cleared the entire auto-expansion state, so revisiting a running thread treated every historical activity as first-seen and reopened it for 500ms. Keep the state scoped by session instead, and prevent inactive-session timers from remeasuring the current thread.

Tryanks · 2026-08-27T05:03:15Z

Root cause

Thread switches cleared the entire automatic activity-expansion state. When a running thread was revisited, every historical command and file edit had no remembered state, so each one took the first-seen path, reopened, and scheduled a fresh 500ms collapse.

Fix

retain automatic expansion state across thread switches
scope state by session so identical activity IDs cannot leak between threads
let inactive-session collapse timers settle their own state without remeasuring the currently visible thread
keep the newest activity behavior unchanged

Regression coverage

a collapsed activity stays collapsed after another session with the same activity ID is visited
a pending collapse only updates its originating session

Verification

cargo fmt --all --check
cargo clippy --workspace --all-targets --locked -- -D warnings
cargo test --workspace --locked

Thread switches cleared the entire auto-expansion state, so revisiting a running thread treated every historical activity as first-seen and reopened it for 500ms. Keep the state scoped by session instead, and prevent inactive-session timers from remeasuring the current thread.

Tryanks · 2026-08-27T05:03:15Z

Root cause

Thread switches cleared the entire automatic activity-expansion state. When a running thread was revisited, every historical command and file edit had no remembered state, so each one took the first-seen path, reopened, and scheduled a fresh 500ms collapse.

Fix

retain automatic expansion state across thread switches
scope state by session so identical activity IDs cannot leak between threads
let inactive-session collapse timers settle their own state without remeasuring the currently visible thread
keep the newest activity behavior unchanged

Regression coverage

a collapsed activity stays collapsed after another session with the same activity ID is visited
a pending collapse only updates its originating session

Verification

cargo fmt --all --check
cargo clippy --workspace --all-targets --locked -- -D warnings
cargo test --workspace --locked

Thread switches cleared the entire auto-expansion state, so revisiting a running thread treated every historical activity as first-seen and reopened it for 500ms. Keep the state scoped by session instead, and prevent inactive-session timers from remeasuring the current thread.

Tryanks · 2026-08-27T05:03:15Z

Root cause

Thread switches cleared the entire automatic activity-expansion state. When a running thread was revisited, every historical command and file edit had no remembered state, so each one took the first-seen path, reopened, and scheduled a fresh 500ms collapse.

Fix

retain automatic expansion state across thread switches
scope state by session so identical activity IDs cannot leak between threads
let inactive-session collapse timers settle their own state without remeasuring the currently visible thread
keep the newest activity behavior unchanged

Regression coverage

a collapsed activity stays collapsed after another session with the same activity ID is visited
a pending collapse only updates its originating session

Verification

cargo fmt --all --check
cargo clippy --workspace --all-targets --locked -- -D warnings
cargo test --workspace --locked

Thread switches cleared the entire auto-expansion state, so revisiting a running thread treated every historical activity as first-seen and reopened it for 500ms. Keep the state scoped by session instead, and prevent inactive-session timers from remeasuring the current thread.

Tryanks · 2026-08-27T05:03:15Z

Root cause

Thread switches cleared the entire automatic activity-expansion state. When a running thread was revisited, every historical command and file edit had no remembered state, so each one took the first-seen path, reopened, and scheduled a fresh 500ms collapse.

Fix

retain automatic expansion state across thread switches
scope state by session so identical activity IDs cannot leak between threads
let inactive-session collapse timers settle their own state without remeasuring the currently visible thread
keep the newest activity behavior unchanged

Regression coverage

a collapsed activity stays collapsed after another session with the same activity ID is visited
a pending collapse only updates its originating session

Verification

cargo fmt --all --check
cargo clippy --workspace --all-targets --locked -- -D warnings
cargo test --workspace --locked

Thread switches cleared the entire auto-expansion state, so revisiting a running thread treated every historical activity as first-seen and reopened it for 500ms. Keep the state scoped by session instead, and prevent inactive-session timers from remeasuring the current thread.

Tryanks · 2026-08-27T05:03:15Z

Root cause

Thread switches cleared the entire automatic activity-expansion state. When a running thread was revisited, every historical command and file edit had no remembered state, so each one took the first-seen path, reopened, and scheduled a fresh 500ms collapse.

Fix

retain automatic expansion state across thread switches
scope state by session so identical activity IDs cannot leak between threads
let inactive-session collapse timers settle their own state without remeasuring the currently visible thread
keep the newest activity behavior unchanged

Regression coverage

a collapsed activity stays collapsed after another session with the same activity ID is visited
a pending collapse only updates its originating session

Verification

cargo fmt --all --check
cargo clippy --workspace --all-targets --locked -- -D warnings
cargo test --workspace --locked

Thread switches cleared the entire auto-expansion state, so revisiting a running thread treated every historical activity as first-seen and reopened it for 500ms. Keep the state scoped by session instead, and prevent inactive-session timers from remeasuring the current thread.