Title: Product Enhancement: Native Session Ask-Tracking · Issue #366 · github/squad · GitHub
Open Graph Title: Product Enhancement: Native Session Ask-Tracking · Issue #366 · github/squad
X Title: Product Enhancement: Native Session Ask-Tracking · Issue #366 · github/squad
Description: Problem When users work with Squad for extended sessions (full-day work), there's no native mechanism to track what they've asked for. Users lose track of their requests, and the only existing tools (SQL todos table, plan.md) are opt-in ...
Open Graph Description: Problem When users work with Squad for extended sessions (full-day work), there's no native mechanism to track what they've asked for. Users lose track of their requests, and the only existing tool...
X Description: Problem When users work with Squad for extended sessions (full-day work), there's no native mechanism to track what they've asked for. Users lose track of their requests, and the only exist...
Opengraph URL: https://github.com/github/squad/issues/366
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Product Enhancement: Native Session Ask-Tracking","articleBody":"## Problem\n\nWhen users work with Squad for extended sessions (full-day work), there's no native mechanism to track what they've asked for. Users lose track of their requests, and the only existing tools (SQL todos table, plan.md) are **opt-in** — requiring the user to explicitly say \"track this\" or use the `[[PLAN]]` prefix.\n\n**The gap:** Squad tracks what agents **do** (orchestration logs, history, decisions) but not what users **ask**.\n\n## What Squad Tracks Today (and the Gap)\n\n| Layer | What it captures | The gap |\n|-------|-----------------|---------|\n| **Orchestration log** | Agent spawns, routing, outcomes | Tracks agent work, not user intent |\n| **decisions.md** | Accumulated team policies | Decisions ≠ requests |\n| **history.md** | Per-agent learned knowledge | What agents learned, not what was asked |\n| **Scribe logs** | Post-session narrative | After-the-fact summary, not live list |\n| **Session store** | Raw conversation turns | Unstructured — no semantic extraction |\n| **SQL todos** | Task tracking | **Opt-in** — requires \"track this\" |\n| **plan.md** | Planning artifact | **Opt-in** — requires `[[PLAN]]` prefix |\n\n## Proposed Phased Approach\n\n### Phase 1: Catalog as Directive\nCatalog common enhancements to Squad via directives. Treat auto-tracking as a **directive** — a coordinator behavior that can be captured in `.squad/decisions.md` and applied via `squad.agent.md` prompt engineering. This lets teams opt-in by adding a directive like:\n\n> \"Always extract and track user asks from every message. Maintain a structured ask list throughout the session.\"\n\nThis requires **zero product changes** — it's a prompt pattern that any Squad team can adopt today.\n\n### Phase 2: CLI Switch (Opt-In)\nAdd a CLI flag to explicitly enable ask tracking:\n\n```\nsquad shell --track-asks\nsquad --track-asks\n```\n\nWhen enabled:\n- Coordinator automatically extracts asks from each user message\n- Classifies: new ask vs. follow-up vs. status check vs. directive\n- Maintains a structured ask list in `.squad/sessions/{id}/asks.json`\n- Natural language access: \"What have I asked for?\" / \"What's pending?\"\n- Survives context compaction (file-based, not in-memory)\n\n### Phase 3: Config File Option\nAdd a `squad.config.ts` option for project-level configuration:\n\n```typescript\nexport default defineSquad({\n session: {\n autoTrackAsks: true,\n askSummary: 'end-of-session', // or 'continuous'\n }\n});\n```\n\nThis makes tracking a project-level setting — set once, forget.\n\n### NOT proposed: Default-on\nAuto-tracking should **not** be turned on by default. It should remain opt-in via CLI switch or config to avoid:\n- Unwanted overhead for quick sessions\n- Coordinator context bloat\n- Unexpected behavior changes\n\n## What Auto-Tracking Unlocks\n\n- **Day-long sessions**: Work all day, never lose track of what you asked for\n- **Handoff clarity**: \"Here's what was asked, here's where we are\"\n- **Session summaries**: Automatic done / in-progress / not-started report\n- **Cross-session continuity**: Next session reads yesterday's ask registry\n- **Accountability**: Clear mapping from ask to agent to outcome\n\n## Ask Registry Shape (Phase 2+)\n\n```json\n[\n { \"id\": \"ask-1\", \"text\": \"Set up Express server\", \"agent\": \"Dallas\", \"status\": \"done\", \"turn\": 3 },\n { \"id\": \"ask-2\", \"text\": \"Add search feature\", \"status\": \"in-progress\", \"turn\": 7 },\n { \"id\": \"ask-3\", \"text\": \"Always use Zod for validation\", \"type\": \"directive\", \"status\": \"captured\", \"turn\": 12 }\n]\n```\n\n## Questions for Discussion\n\n1. **Phase 1 scope**: Should we ship a pre-built directive template that teams can copy, or document it as a pattern in the Squad docs?\n2. **Phase 2 UX**: What should the ask list look like when the user says \"What have I asked for?\" — table, bullet list, grouped by status?\n3. **Phase 3 config surface**: Should this live in `squad.config.ts` only, or also in `.squad/config.json` for non-SDK users?\n4. **Classification**: How sophisticated should the ask classifier be? Simple (every user message = ask) vs. smart (distinguish asks from follow-ups, feedback, status checks)?\n\n/cc @bradygaster @tamirdresher for opinions on phasing and approach.\n\n---\n\n*Reported by: Dina Berry*\n*Source: Session conversation analyzing Squad product UX gap*\n","author":{"url":"https://github.com/diberry","@type":"Person","name":"diberry"},"datePublished":"2026-03-13T00:04:02Z","url":"https://github.com/github/squad/issues/366"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:84e30d39-56fa-eb06-1059-598f0240c45d |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 9060:6365:17806AE:1F56BAE:6B01463B |
| html-safe-nonce | cd4da3530a67c42c7ac82f6bfacb972009a54491a4980afa44479802d0eb3ed7 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI5MDYwOjYzNjU6MTc4MDZBRToxRjU2QkFFOjZCMDE0NjNCIiwidmlzaXRvcl9pZCI6IjQ1ODEyNDAxMDUxNjI4NTE5MDAiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | 83619b6e4dae6ffe07bda0e66f996cac654a1a0c7f2ded0478d13c077063062d |
| hovercard-subject-tag | issue:4067958373 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/github/squad/366/issue_layout |
| twitter:image | https://opengraph.githubassets.com/cc003bf433df284c38be19dbccc7fa82673c24437d1d2b461b20f7d172abfe4f/github/squad/issues/366 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/cc003bf433df284c38be19dbccc7fa82673c24437d1d2b461b20f7d172abfe4f/github/squad/issues/366 |
| og:image:alt | Problem When users work with Squad for extended sessions (full-day work), there's no native mechanism to track what they've asked for. Users lose track of their requests, and the only existing tool... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | diberry |
| hostname | github.com |
| expected-hostname | github.com |
| None | cc5dfdd32f62ebd3223cab3af3aa2b268d3605218237326a48a99d1efd89495c |
| turbo-cache-control | no-preview |
| go-import | github.com/github/squad git https://github.com/github/squad.git |
| octolytics-dimension-user_id | 9919 |
| octolytics-dimension-user_login | github |
| octolytics-dimension-repository_id | 1151205052 |
| octolytics-dimension-repository_nwo | github/squad |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 1151205052 |
| octolytics-dimension-repository_network_root_nwo | github/squad |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 8c77c9e8439031ad54c75a250694842892f693e1 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width