feat: add Steering view — analyze and learn from the impact of human prompts on outcomes#44
Open
paulyuk wants to merge 3 commits into
Open
feat: add Steering view — analyze and learn from the impact of human prompts on outcomes#44paulyuk wants to merge 3 commits into
paulyuk wants to merge 3 commits into
Conversation
Adds a Steering view that extracts human steering commands from AI coding sessions, pairs them with resulting git commits and code changes, and shows the impact. An agent-assisted analysis runs in the background using the Copilot SDK to improve What Happened, Level-Up, and Impact columns. A steering intelligence panel surfaces density scoring, category breakdown, and actionable insights. New files: - routes/steering.js — git analysis, steering log, AI synthesis endpoint - src/components/SteeringView.jsx — timeline, filters, detail, intelligence - src/lib/steeringExtractor.js — session heuristic extractor - src/lib/steeringAgent.js — Copilot SDK analysis agent - src/__tests__/steeringExtractor.test.js — 27 tests - src/__tests__/steeringRoute.test.js — 15 tests - src/__tests__/steeringView.test.jsx — 6 tests - docs/evals.md, steering-demo.md, steering-insights.md Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Add examples of starting a coding agent, sending prompts, and redirecting to produce the steering data the view captures. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
c01b6db to
fe908d8
Compare
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.
Steering View
Problem
When you watch an AI coding session in Replay or Tracks, you see what the agent did: tool calls, file edits, reasoning. But you can't see which human prompts actually mattered or why. Which ones changed the direction? Which ones led to the most code? Which ones caused bugs that led to better tests? Which ones had too many hallucinations or continues retrying achieve a outcome or taste, requiring interventions (as we see in coach)?
Solution
The Steering view extracts every human prompt that redirected the agent, pairs each one with the git commits and code changes it produced, and shows the impact: lines changed, tests passing, and what was learned.
It understands not just the primary coding agent (Copilot, Claude Code, VS Code Copilot), but also sub-agents and squads — capturing the reasoning from dispatched agents as they respond to steering.
An agent-assisted analysis runs automatically in the background using the Copilot SDK to improve the quality of What Happened, Level-Up, and Impact columns beyond what static heuristics can produce. A steering intelligence panel shows density scoring, category breakdown, and actionable insights derived from the session's steering patterns. This is effectively a "double-click" on the insights we see in coach, but scoped to each and every steering message or intervention.
Think of this as a solution hypothesis. More hypotheses and details around valuable insights we can gain from steering and interventions are here.
Screenshot
Quick Start
git fetch origin pull/44/head:feature/steering-view git checkout feature/steering-view npm install && npm run devThen start a coding session in another terminal. For example with Copilot:
copilot "add a /healthcheck endpoint that returns uptime and version"Work with the agent for a few turns. Redirect it at least once — say things like "that's too verbose, simplify it" or "don't use console.log, use the existing logger." Those redirections are the steering the view captures.
Then open agentviz, load the session file, and click the Steering tab (last tab, after Coach).
What you see
Each row is either a human steering command (italic quotes, bright text) or a git commit (dimmer text, blue hash). For each steering command:
The detail panel shows the full squad response, files changed, commit info, and a Responding To section showing what the agent said that the user was reacting to.
Steering intelligence
Below the timeline, an expandable panel shows:
How it works
Guardrails verified (per #43)
Files (18 total: 11 new, 7 modified)
Built with snap-squad — npx snap-squad init