Repository navigation
feat(tui): add opt-in conversation freshness diagnostics - #6327
Draft
schickling-assistant wants to merge 1 commit into
Draft
schickling-assistant wants to merge 1 commit into
schickling-assistant wants to merge 1 commit into
Conversation
agent-identity: agent/dotfiles/fractal-product-lead agent-persona: generalist agent-supervisor: unavailable agent-tool: OMP agent-tool-version: 18.12.5 agent-runtime: OMP 18.12.5 agent-model: openai-codex/gpt-6.1-sol
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
A conversation can appear stale after End even while its live-update footer advances. That footer records receipt, not display freshness. Source inspection did not establish a defect matching the reported reproduction.
Goal
Identify the first stage that stops advancing without recording conversation content.
Decisions
Verification
One admitted final-head ticket runs cargo test --locked -p fractal-tui -p fractal-conversation-ui and cargo clippy --locked -p fractal-tui -p fractal-conversation-ui --all-targets -- -D warnings. Results pending; this draft is not ready. No CI dispatch requested. Automatic local pre-push signing disabled to avoid duplicate builds.
Complexity
Small metadata-only hooks plus a single opt-in tracing module; disabled by default.
Concerns
Identifiers, endpoints and timestamps remain private metadata. Filtered entries and folded tool runs can intentionally change tail IDs. This is a probe, not a claimed repair.
Friction & bottlenecks
None beyond admitted build scheduling.
Follow-ups
Capture an opt-in trace during the next reproduction and locate the first stalled stage.
References
Troubleshooting instructions: docs/when-something-is-wrong.md.
Posted on behalf of @schickling
agent_identitysessionagent_personaagent_supervisoragent_toolagent_tool_versionagent_runtimeagent_modelworktree