agentic-reasoning-trace-summaries-40k

 # Reasoning Summary JSON Dataset We built this dataset to train models to turn long reasoning/work traces into short structured summaries. Each example has a verbose trace in `input` and a compact JSON summary in `output`. The summary is shaped like the kind of progress update we want a model to produce while it is working: a title, a subtitle, a short summary, and the current task. The dataset is JSONL with `43,734` rows. The rows are ordered from longest to shortest so long-context examples appear first. ## Format Each line looks like this: ```json { "input": "long reasoning or work trace...", "output": "{\"title\":\"...\",\"sub_title\":\"...\",\"summary\":\"...\",\"cur_task\":\"...\"}" } ``` One important detail: `output` is a string, not a nested JSON object. The string itself contains valid JSON. We store it this way because most ChatML and SFT pipelines expect assistant messages to be plain text. If `output` is stored as a native object, some converters either fail or serialize it in surprising ways. The JSON inside `output` follows this shape: ```json { "title": "Short title", "sub_title": "One-line description", "summary": "Compact summary of the trace", "cur_task": "Current task or immediate next step" } ``` ## Example ```json { "input": "Now let me create the SplashScreen and HomeScreen...", "output": "{\"title\":\"Flutter Screen Creation\",\"sub_title\":\"Implementing the initial SplashScreen and planning the HomeScreen structure.\",\"summary\":\"I'm starting to implement the Flutter UI by creating the SplashScreen widget. I'm focusing on setting up the basic structure and planning the routing logic that will determine when to transition to the HomeScreen based on authentication and deep link states.\",\"cur_task\":\"I'm writing the SplashScreen widget code and considering how to handle the routing logic based on authentication and deep link states.\"}" } ``` <div style="font-family:Arial,Helvetica,sans-serif;max-width:1080px;margin:28px auto;color:#3b3b38;background:#fff;box-sizing:border-box;"> <div style="border:1px solid #dddddd;background:#f7f7f6;border-radius:5px;padding:14px;margin-bottom:18px;box-shadow:0 2px 0 rgba(0,0,0,.10),0 10px 24px rgba(0,0,0,.035);box-sizing:border-box;"> <p style="margin:0 0 10px 0;font-size:13px;color:#696966;">Reasoning Chain</p> <p style="margin:0;background:#fff;border:1px solid #dedede;border-radius:4px;min-height:360px;padding:16px 18px;font-size:13px;line-height:1.75;color:#3f3f3c;box-shadow:inset 0 1px 2px rgba(0,0,0,.035);box-sizing:border-box;overflow-wrap:break-word;word-break:normal;overflow:hidden;"> I am investigating a React theme initialization issue in a production build. The app appears to default to light mode during the first render, then switches to dark mode only after localStorage is read. This creates a visible white flash before the saved theme preference is applied. I need to understand whether this is caused by the default React state, the hydration order, the timing of the localStorage effect, or the way the theme class is written to the DOM. <br><br> First, I should inspect the app entry point and check whether any synchronous theme bootstrap exists before React mounts. If the saved theme is only read inside a useEffect, then the browser will paint the initial light UI before the effect runs. That would explain why the app briefly appears in the wrong theme. I should also check whether the theme provider initializes with a hardcoded light value, a system preference, or a value derived from localStorage. <br><br> Next, I need to inspect how the theme is applied. If the implementation replaces classes on document.body, that can be risky because the body may already contain layout, accessibility, or framework classes. A cleaner approach is likely to use document.documentElement with a data-theme attribute, such as data-theme="dark" or data-theme="light". That makes the theme state easier to target from CSS and reduces the chance of accidentally removing unrelated classes. <br><br> I also need to review the settings page because the selected theme may not be clearly represented. The visual state might be obvious to sighted users, but keyboard users and screen readers need proper semantics. I should check whether the controls expose selected or pressed state, whether focus indicators are visible, and whether the component being used is actually a button or just a clickable card. If DashboardCard is used as an interactive control, it should behave like a real control. <br><br> The dashboard card implementation may also be involved. Reusable cards sometimes hide accessibility issues because they look interactive but do not expose the correct behavior. I should inspect whether active state, hover state, focus state, and disabled state are handled consistently. I should avoid redesigning the entire settings page unless the current structure is directly causing the theme bug. <br><br> The likely fix is to apply the saved theme before first paint, keep the DOM update scoped to documentElement, and make the settings UI reflect the selected state clearly. The final summary should preserve the important reasoning without becoming too long. It should explain that the theme initializes too late, that body class replacement may be unsafe, that a pre-render bootstrap or documentElement dataset is safer, and that accessibility should be checked in the theme controls. </p> </div> <div style="border:1px solid #dddddd;background:#f7f7f6;border-radius:5px;padding:14px;margin-bottom:18px;box-shadow:0 2px 0 rgba(0,0,0,.10),0 10px 24px rgba(0,0,0,.035);box-sizing:border-box;"> <div style="display:flex;justify-content:space-between;gap:12px;margin-bottom:14px;align-items:center;"> <p style="margin:0;font-size:14px;font-weight:700;color:#5a5a56;">Q4_K_M</p> <p style="margin:0;font-size:12px;color:#777772;">529.30 MB · 4.51s</p> </div> <div style="display:grid;grid-template-columns:330px 1fr;gap:18px;box-sizing:border-box;"> <div style="box-sizing:border-box;min-width:0;"> <p style="margin:0 0 6px 0;font-size:13px;color:#666663;">Title</p> <p style="margin:0 0 12px 0;background:#fff;border:1px solid #dedede;border-radius:4px;height:54px;padding:10px 11px;font-size:13px;line-height:1.5;color:#3d3d3a;box-shadow:inset 0 1px 2px rgba(0,0,0,.035);box-sizing:border-box;overflow-wrap:break-word;overflow:hidden;">React Theme Initialization</p> <p style="margin:0 0 6px 0;font-size:13px;color:#666663;">Sub-title</p> <p style="margin:0 0 12px 0;background:#fff;border:1px solid #dedede;border-radius:4px;height:64px;padding:10px 11px;font-size:13px;line-height:1.45;color:#3d3d3a;box-shadow:inset 0 1px 2px rgba(0,0,0,.035);box-sizing:border-box;overflow-wrap:break-word;overflow:hidden;">Analyzing theme initialization, hydration, and accessibility considerations in the React app.</p> <p style="margin:0 0 6px 0;font-size:13px;color:#666663;">Current Task</p> <p style="margin:0;background:#fff;border:1px solid #dedede;border-radius:4px;height:78px;padding:10px 11px;font-size:13px;line-height:1.45;color:#3d3d3a;box-shadow:inset 0 1px 2px rgba(0,0,0,.035);box-sizing:border-box;overflow-wrap:break-word;overflow:hidden;">I'm reviewing the React app's theme initialization and accessibility requirements to ensure a responsive and accessible experience.</p> </div> <div style="box-sizing:border-box;min-width:0;"> <p style="margin:0 0 6px 0;font-size:13px;color:#666663;">Summary</p> <p style="margin:0;background:#fff;border:1px solid #dedede;border-radius:4px;height:238px;padding:12px 13px;font-size:13px;line-height:1.65;color:#3d3d3a;box-shadow:inset 0 1px 2px rgba(0,0,0,.035);box-sizing:border-box;overflow-wrap:break-word;word-break:normal;overflow:hidden;">I reviewed the React app's theme behavior, noting that it defaults to light and only switches on localStorage. I considered synchronous initialization and the need for a bootstrap, and examined the settings page to understand the current layout and accessibility needs.</p> </div> </div> </div> <div style="border:1px solid #dddddd;background:#f7f7f6;border-radius:5px;padding:14px;margin-bottom:18px;box-shadow:0 2px 0 rgba(0,0,0,.10),0 10px 24px rgba(0,0,0,.035);box-sizing:border-box;"> <div style="display:flex;justify-content:space-between;gap:12px;margin-bottom:14px;align-items:center;"> <p style="margin:0;font-size:14px;font-weight:700;color:#5a5a56;">Q6_K</p> <p style="margin:0;font-size:12px;color:#777772;">629.74 MB · 5.10s</p> </div> <div style="display:grid;grid-template-columns:330px 1fr;gap:18px;box-sizing:border-box;"> <div style="box-sizing:border-box;min-width:0;"> <p style="margin:0 0 6px 0;font-size:13px;color:#666663;">Title</p> <p style="margin:0 0 12px 0;background:#fff;border:1px solid #dedede;border-radius:4px;height:54px;padding:10px 11px;font-size:13px;line-height:1.5;color:#3d3d3a;box-shadow:inset 0 1px 2px rgba(0,0,0,.035);box-sizing:border-box;overflow-wrap:break-word;overflow:hidden;">Theme Initialization Analysis</p> <p style="margin:0 0 6px 0;font-size:13px;color:#666663;">Sub-title</p> <p style="margin:0 0 12px 0;background:#fff;border:1px solid #dedede;border-radius:4px;height:64px;padding:10px 11px;font-size:13px;line-height:1.45;color:#3d3d3a;box-shadow:inset 0 1px 2px rgba(0,0,0,.035);box-sizing:border-box;overflow-wrap:break-word;overflow:hidden;">Analyzing theme initialization flow, hydration behavior, and accessibility considerations.</p> <p style="margin:0 0 6px 0;font-size:13px;color:#666663;">Current Task</p> <p style="margin:0;background:#fff;border:1px solid #dedede;border-radius:4px;height:78px;padding:10px 11px;font-size:13px;line-height:1.45;color:#3d3d3a;box-shadow:inset 0 1px 2px rgba(0,0,0,.035);box-sizing:border-box;overflow-wrap:break-word;overflow:hidden;">I'm examining the theme initialization logic and accessibility requirements to improve the current implementation.</p> </div> <div style="box-sizing:border-box;min-width:0;"> <p style="margin:0 0 6px 0;font-size:13px;color:#666663;">Summary</p> <p style="margin:0;background:#fff;border:1px solid #dedede;border-radius:4px;height:238px;padding:12px 13px;font-size:13px;line-height:1.65;color:#3d3d3a;box-shadow:inset 0 1px 2px rgba(0,0,0,.035);box-sizing:border-box;overflow-wrap:break-word;word-break:normal;overflow:hidden;">I reviewed the theme initialization sequence, noting that light is applied first and then switched to dark after hydration. I identified that the current approach lacks synchronous initialization and that body class replacement is unsafe. I also considered using documentElement dataset for safer theme handling and explored accessibility and dashboard card inspection.</p> </div> </div> </div> <div style="border:1px solid #dddddd;background:#f7f7f6;border-radius:5px;padding:14px;margin-bottom:18px;box-shadow:0 2px 0 rgba(0,0,0,.10),0 10px 24px rgba(0,0,0,.035);box-sizing:border-box;"> <div style="display:flex;justify-content:space-between;gap:12px;margin-bottom:14px;align-items:center;"> <p style="margin:0;font-size:14px;font-weight:700;color:#5a5a56;">Q8_0</p> <p style="margin:0;font-size:12px;color:#777772;">811.84 MB · 4.00s</p> </div> <div style="display:grid;grid-template-columns:330px 1fr;gap:18px;box-sizing:border-box;"> <div style="box-sizing:border-box;min-width:0;"> <p style="margin:0 0 6px 0;font-size:13px;color:#666663;">Title</p> <p style="margin:0 0 12px 0;background:#fff;border:1px solid #dedede;border-radius:4px;height:54px;padding:10px 11px;font-size:13px;line-height:1.5;color:#3d3d3a;box-shadow:inset 0 1px 2px rgba(0,0,0,.035);box-sizing:border-box;overflow-wrap:break-word;overflow:hidden;">Theme Initialization Analysis</p> <p style="margin:0 0 6px 0;font-size:13px;color:#666663;">Sub-title</p> <p style="margin:0 0 12px 0;background:#fff;border:1px solid #dedede;border-radius:4px;height:64px;padding:10px 11px;font-size:13px;line-height:1.45;color:#3d3d3a;box-shadow:inset 0 1px 2px rgba(0,0,0,.035);box-sizing:border-box;overflow-wrap:break-word;overflow:hidden;">Reviewing theme initialization flow, hydration behavior, and accessibility considerations.</p> <p style="margin:0 0 6px 0;font-size:13px;color:#666663;">Current Task</p> <p style="margin:0;background:#fff;border:1px solid #dedede;border-radius:4px;height:78px;padding:10px 11px;font-size:13px;line-height:1.45;color:#3d3d3a;box-shadow:inset 0 1px 2px rgba(0,0,0,.035);box-sizing:border-box;overflow-wrap:break-word;overflow:hidden;">I'm reviewing the theme initialization logic and accessibility requirements to ensure a smooth and accessible user experience.</p> </div> <div style="box-sizing:border-box;min-width:0;"> <p style="margin:0 0 6px 0;font-size:13px;color:#666663;">Summary</p> <p style="margin:0;background:#fff;border:1px solid #dedede;border-radius:4px;height:238px;padding:12px 13px;font-size:13px;line-height:1.65;color:#3d3d3a;box-shadow:inset 0 1px 2px rgba(0,0,0,.035);box-sizing:border-box;overflow-wrap:break-word;word-break:normal;overflow:hidden;">I examined the theme initialization sequence, noting that light is set first and then switched to dark on reload. I considered the need for synchronous initialization and the importance of using documentElement for safer class replacement. I also reviewed the settings page and dashboard card to understand accessibility and UI requirements.</p> </div> </div> </div> </div> ## Loading ```python from datasets import load_dataset import json ds = load_dataset("json", data_files="dataset.jsonl", split="train") row = ds[0] # Use this directly as assistant text during SFT. assistant_text = row["output"] # Parse only if you want to inspect or validate the fields. parsed = json.loads(row["output"]) ``` ## Chat Format This is the format we use for chat-style training: ```python messages = [ {"role": "user", "content": row["input"]}, {"role": "assistant", "content": row["output"]}, ] ``` ## Validation We ran a full validation pass before upload: ```text rows: 43,734 outer JSONL lines valid: 43,734 input strings: 43,734 output strings: 43,734 output strings that parse as JSON: 43,734 parsed outputs that are JSON objects: 43,734 sort violations: 0 ``` ## Notes The source traces can include code, tool calls, implementation notes, math, debugging steps, and other task-oriented text. The target output stays compact and structured, which makes the dataset useful for training models to produce clean progress summaries instead of long free-form explanations. We intentionally added broken or extremely short samples to teach the model to react to these samples. We recommend not to remove those samples as the model might not learn to react to ambiguous inputs! --- *Credit goes to @QyrouNnet-AI*