8eebf7dd40
Master stabilized two of the three hand-built markdown fixtures by spacing their event times, so the stats line's LLM segment stops depending on how fast the replay ran. `markdown-images` was left on the old shape and kept failing for exactly that reason — a different test each run, always the same one-line difference. Pin it the same way and record the segment its golden now always shows. This supersedes the normalizer that dropped those segments outright, reverted here: pinning the fixture keeps a real part of the page in the goldens instead of hiding it from every one of them, and master's two goldens already record it.
50 lines
2.5 KiB
Markdown
50 lines
2.5 KiB
Markdown
- banner:
|
|
- navigation "Session hierarchy":
|
|
- 'button "Plan a small change: add" [disabled]'
|
|
- tablist:
|
|
- tab "Chat" [selected]
|
|
- tab "Trajectory"
|
|
- img
|
|
- text: "plan Plan mode on. Use /plan off to leave. Interjection Plan a small change: add a --greeting flag to a CLI. Do not read or write any files. Call exit_plan_mode with a short plan of at most five bullet points. Once the plan is approved, reply with the single word DONE and stop. {{clock}}"
|
|
- button "Copy":
|
|
- img
|
|
- button "Branch into a new conversation" [disabled]:
|
|
- img
|
|
- text: Available only on the last message of a completed turn
|
|
- button "Context injection @deepseek-ai/dsh-system-prompt":
|
|
- img
|
|
- img
|
|
- text: Context injection @deepseek-ai/dsh-system-prompt
|
|
- 'button "Think The user wants me to plan a small change to add a `--greeting` flag to a CLI. They explicitly told me not to read or write any files, and to call exit_plan_mode with a short plan. Let me do that directly."':
|
|
- img
|
|
- img
|
|
- text: "Think The user wants me to plan a small change to add a `--greeting` flag to a CLI. They explicitly told me not to read or write any files, and to call exit_plan_mode with a short plan. Let me do that directly."
|
|
- paragraph:
|
|
- text: Since the user has explicitly asked me not to read or write any files and to go straight to planning, I'll proceed with
|
|
- code: exit_plan_mode
|
|
- text: .
|
|
- 'button "Tool call exit_plan_mode · # Add `--greeting` flag to CLI"':
|
|
- img
|
|
- img
|
|
- text: "Tool call exit_plan_mode · # Add `--greeting` flag to CLI"
|
|
- 'button "Think The plan was approved. The user''s last instruction says: \"Once the plan is approved, reply with the single word DONE and stop.\" So I should just reply with DONE and stop."':
|
|
- img
|
|
- img
|
|
- text: "Think The plan was approved. The user's last instruction says: \"Once the plan is approved, reply with the single word DONE and stop.\" So I should just reply with DONE and stop."
|
|
- paragraph: DONE
|
|
- button "Copy":
|
|
- img
|
|
- button "Branch into a new conversation":
|
|
- img
|
|
- text: {{clock}} Ran for {{duration}} TTFT {{duration}} {{throughput}} tok/s
|
|
- textbox "Message the agent"
|
|
- button "Commands":
|
|
- img
|
|
- 'button "Access mode, current: Workspace Write"': Workspace Write
|
|
- button "Select model, current DeepSeek-V4-Flash":
|
|
- text: DeepSeek-V4-Flash
|
|
- img
|
|
- button "4% of context used"
|
|
- button "Send message" [disabled]
|
|
- text: 1 turns · 2 steps LLM {{duration}} · Tool call {{duration}} TTFT avg {{duration}} · {{throughput}} tok/s Cache hit 51% Input 10.2K tok · Output 346 tok
|