René's URL Explorer Experiment


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

direct link

Domain: github.com


Hey, it has json ld scripts:
{"@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-profiling0
react-import-mapreact,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-controllervoltron_issues_fragments
route-actionissue_layout
fetch-noncev2:84e30d39-56fa-eb06-1059-598f0240c45d
current-catalog-service-hash81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114
request-id9060:6365:17806AE:1F56BAE:6B01463B
html-safe-noncecd4da3530a67c42c7ac82f6bfacb972009a54491a4980afa44479802d0eb3ed7
visitor-payloadeyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI5MDYwOjYzNjU6MTc4MDZBRToxRjU2QkFFOjZCMDE0NjNCIiwidmlzaXRvcl9pZCI6IjQ1ODEyNDAxMDUxNjI4NTE5MDAiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ==
visitor-hmac83619b6e4dae6ffe07bda0e66f996cac654a1a0c7f2ded0478d13c077063062d
hovercard-subject-tagissue:4067958373
github-keyboard-shortcutsrepository,issues,copilot
google-site-verificationApib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I
octolytics-urlhttps://collector.github.com/github/collect
analytics-location///voltron/issues_fragments/issue_layout
fb:app_id1401488693436528
apple-itunes-appapp-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/github/squad/366/issue_layout
twitter:imagehttps://opengraph.githubassets.com/cc003bf433df284c38be19dbccc7fa82673c24437d1d2b461b20f7d172abfe4f/github/squad/issues/366
twitter:cardsummary_large_image
og:imagehttps://opengraph.githubassets.com/cc003bf433df284c38be19dbccc7fa82673c24437d1d2b461b20f7d172abfe4f/github/squad/issues/366
og:image:altProblem 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:width1200
og:image:height600
og:site_nameGitHub
og:typeobject
og:author:usernamediberry
hostnamegithub.com
expected-hostnamegithub.com
Nonecc5dfdd32f62ebd3223cab3af3aa2b268d3605218237326a48a99d1efd89495c
turbo-cache-controlno-preview
go-importgithub.com/github/squad git https://github.com/github/squad.git
octolytics-dimension-user_id9919
octolytics-dimension-user_logingithub
octolytics-dimension-repository_id1151205052
octolytics-dimension-repository_nwogithub/squad
octolytics-dimension-repository_publictrue
octolytics-dimension-repository_is_forkfalse
octolytics-dimension-repository_network_root_id1151205052
octolytics-dimension-repository_network_root_nwogithub/squad
turbo-body-classeslogged-out env-production page-responsive
disable-turbofalse
browser-stats-urlhttps://api.github.com/_private/browser/stats
browser-errors-urlhttps://api.github.com/_private/browser/errors
release8c77c9e8439031ad54c75a250694842892f693e1
ui-targetfull
theme-color#1e2327
color-schemelight dark
react-app-nameissues

Links:

Skip to contenthttps://github.com/github/squad/issues/366#start-of-content
https://github.com/
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fgithub%2Fsquad%2Fissues%2F366
GitHubRepository hosting, code review, and collaborationhttps://github.com/platform
CopilotAI coding agent for tasks, projects, and automated workhttps://github.com/features/copilot
ActionsCI/CD and automationhttps://github.com/features/actions
Code QualityQuality analysis, fixes, and enforcementhttps://github.com/features/code-quality
CodespacesCloud development environmentshttps://github.com/features/codespaces
Code SecurityVulnerability detection and remediationhttps://github.com/security/advanced-security/code-security
Secret ProtectionSecret scanning and leak preventionhttps://github.com/security/advanced-security/secret-protection
All Featureshttps://github.com/features
Documentationhttps://docs.github.com/en
Traininghttps://learn.github.com/skills
Certificationshttps://learn.github.com/credentials
Build with Copilothttps://github.com/features/ai
Customize Copilothttps://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/customize-copilot-overview
Integrationshttps://github.com/marketplace
Trending reposhttps://github.com/trending
GitHub Sponsorshttps://github.com/open-source/sponsors
Developer articleshttps://github.com/resources/articles
ChangelogYour source for the latest features, improvements, and fixes across GitHub products, all in one place.https://github.blog/changelog/
Enterpriseshttps://github.com/enterprise
Teamhttps://github.com/team
Startupshttps://github.com/enterprise/startups
Nonprofitshttps://github.com/solutions/industry/nonprofits
Healthcarehttps://github.com/solutions/industry/healthcare
Financial serviceshttps://github.com/solutions/industry/financial-services
Manufacturinghttps://github.com/solutions/industry/manufacturing
Governmenthttps://github.com/solutions/industry/government
See all industrieshttps://github.com/solutions/industry
Why GitHubhttps://github.com/why-github
Customer Storieshttps://github.com/customer-stories
Business insightshttps://github.com/solutions/executive-insights
Trust Centerhttps://github.com/trust-center
GitHub Advanced SecurityEnterprise-grade code securityhttps://github.com/security/advanced-security
Copilot for businessEnterprise-grade AI featureshttps://github.com/features/copilot/copilot-business
Premium SupportEnterprise-grade 24/7 supporthttps://github.com/enterprise/premium-support
Documentationhttps://docs.github.com/en
Resource centerhttps://github.com/resources
Bloghttps://github.blog/
Events & webinarshttps://github.com/resources/events
Community Forumhttps://github.com/orgs/community/discussions
Customer Storieshttps://github.com/customer-stories
Integrationshttps://github.com/marketplace
Customer supporthttps://help.github.com/
Traininghttps://learn.github.com/skills
GitHub Statushttps://www.githubstatus.com/
Abouthttps://github.com/about
Partnershttps://github.com/partners
Changeloghttps://github.blog/changelog/
GitHub UniverseThe event for developers, by developers — talks, workshops, and what’s next for GitHub.https://githubuniverse.com/
Pricinghttps://github.com/pricing
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fgithub%2Fsquad%2Fissues%2F366
Sign uphttps://github.com/signup?ref_cta=Sign+up&ref_loc=header+logged+out&ref_page=%2F%3Cuser-name%3E%2F%3Crepo-name%3E%2Fvoltron%2Fissues_fragments%2Fissue_layout&source=header-repo&source_repo=github%2Fsquad
Reloadhttps://github.com/github/squad/issues/366
Reloadhttps://github.com/github/squad/issues/366
Reloadhttps://github.com/github/squad/issues/366
githubhttps://github.com/github
squadhttps://github.com/github/squad
Codehttps://github.com/github/squad
Issues108 (108)https://github.com/github/squad/issues
Pull requests26 (26)https://github.com/github/squad/pulls
Discussionshttps://github.com/github/squad/discussions
Actionshttps://github.com/github/squad/actions
Projectshttps://github.com/github/squad/projects
Security and qualityhttps://github.com/github/squad/security
Insightshttps://github.com/github/squad/insights
https://github.com/github/squad
New issuehttps://github.com/login?return_to=https://github.com/github/squad/issues/366
New issuehttps://github.com/login?return_to=https://github.com/github/squad/issues/366
Product Enhancement: Native Session Ask-Trackinghttps://github.com/github/squad/issues/366#top
go:needs-researchNeeds investigationhttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22go%3Aneeds-research%22
priority:p1This sprinthttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22priority%3Ap1%22
squadSquad triage inbox — Lead will assign to a memberhttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22squad%22
type:featureNew capabilityhttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22type%3Afeature%22
https://github.com/diberry
diberryhttps://github.com/diberry
on Mar 13, 2026https://github.com/github/squad/issues/366#issue-4067958373
@bradygasterhttps://github.com/bradygaster
@tamirdresherhttps://github.com/tamirdresher
https://github.com/diberry
diberryhttps://github.com/diberry
on Mar 13, 2026https://github.com/github/squad/issues/366#issuecomment-4051378687
@bradygasterhttps://github.com/bradygaster
@tamirdresherhttps://github.com/tamirdresher
https://github.com/tamirdresher
tamirdresherhttps://github.com/tamirdresher
on Mar 13, 2026https://github.com/github/squad/issues/366#issuecomment-4053314190
@diberryhttps://github.com/diberry
https://github.com/bradygaster/squad/issues/365#issuecomment-4053287066https://github.com/bradygaster/squad/issues/365#issuecomment-4053287066
bradygasterhttps://github.com/bradygaster
squadSquad triage inbox — Lead will assign to a memberhttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22squad%22
squad:keatonhttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22squad%3Akeaton%22
squad:fensterhttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22squad%3Afenster%22
priority:p1This sprinthttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22priority%3Ap1%22
type:featureNew capabilityhttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22type%3Afeature%22
on Mar 13, 2026https://github.com/github/squad/issues/366#event-23559340723
github-actionshttps://github.com/apps/github-actions
squad:fidohttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22squad%3Afido%22
go:needs-researchNeeds investigationhttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22go%3Aneeds-research%22
on Mar 13, 2026https://github.com/github/squad/issues/366#event-23559345927
https://github.com/apps/github-actions
github-actionshttps://github.com/apps/github-actions
on Mar 13, 2026https://github.com/github/squad/issues/366#issuecomment-4057847318
GitHub Actionshttps://help.github.com/en/actions
#366https://github.com/github/squad/issues/366
bradygasterhttps://github.com/bradygaster
squad:flighthttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22squad%3Aflight%22
squad:eecomhttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22squad%3Aeecom%22
squad:fidohttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22squad%3Afido%22
squad:keatonhttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22squad%3Akeaton%22
squad:fensterhttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22squad%3Afenster%22
on Mar 13, 2026https://github.com/github/squad/issues/366#event-23560328404
https://github.com/apps/github-actions
github-actionshttps://github.com/apps/github-actions
on Mar 13, 2026https://github.com/github/squad/issues/366#issuecomment-4058730372
GitHub Actionshttps://help.github.com/en/actions
#366https://github.com/github/squad/issues/366
https://github.com/apps/github-actions
github-actionshttps://github.com/apps/github-actions
on Mar 13, 2026https://github.com/github/squad/issues/366#issuecomment-4058730454
GitHub Actionshttps://help.github.com/en/actions
#366https://github.com/github/squad/issues/366
tamirdresherhttps://github.com/tamirdresher
on Mar 16, 2026https://github.com/github/squad/issues/366#event-23607616187
test: hostile input, SDK failure, and stress tests (github#380)https://github.com/tamirdresher/squad/commit/bf00c33ed7cf9b038828970a9cfe24162849dd51
github#380https://github.com/github/squad/pull/380
https://docs.github.com/articles/closing-issues-via-commit-messages
bf00c33https://github.com/tamirdresher/squad/commit/bf00c33ed7cf9b038828970a9cfe24162849dd51
fix: P0 quality fixes from quality review (github#381)https://github.com/tamirdresher/squad/commit/b265b2a888e272d21c682a68a9523af4a43a4b04
github#381https://github.com/github/squad/pull/381
https://docs.github.com/articles/closing-issues-via-commit-messages
b265b2ahttps://github.com/tamirdresher/squad/commit/b265b2a888e272d21c682a68a9523af4a43a4b04
githubhttps://github.com/github
github-actionshttps://github.com/github-actions
on Mar 18, 2026https://github.com/github/squad/issues/366#event-23694398012
githubhttps://github.com/github
github-actionshttps://github.com/github-actions
on Mar 18, 2026https://github.com/github/squad/issues/366#event-23694398246
https://github.com/diberry
diberryhttps://github.com/diberry
on Mar 23, 2026https://github.com/github/squad/issues/366#issuecomment-4110863056
diberryhttps://github.com/diberry
not plannedhttps://github.com/github/squad/issues?q=is%3Aissue%20state%3Aclosed%20archived%3Afalse%20reason%3Anot-planned
on Mar 23, 2026https://github.com/github/squad/issues/366#event-23815188448
bradygasterhttps://github.com/bradygaster
squad:flighthttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22squad%3Aflight%22
squad:eecomhttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22squad%3Aeecom%22
on Sep 11, 2026https://github.com/github/squad/issues/366#event-31000814318
Sign up for freehttps://github.com/signup?return_to=https://github.com/github/squad/issues/366
Sign in to commenthttps://github.com/login?return_to=https://github.com/github/squad/issues/366
go:needs-researchNeeds investigationhttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22go%3Aneeds-research%22
priority:p1This sprinthttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22priority%3Ap1%22
squadSquad triage inbox — Lead will assign to a memberhttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22squad%22
type:featureNew capabilityhttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22type%3Afeature%22
https://github.com
Termshttps://docs.github.com/site-policy/github-terms/github-terms-of-service
Privacyhttps://docs.github.com/site-policy/privacy-policies/github-privacy-statement
Securityhttps://github.com/security
Statushttps://www.githubstatus.com/
Communityhttps://github.community/
Docshttps://docs.github.com/
Contacthttps://support.github.com?tags=dotcom-footer

Viewport: width=device-width


URLs of crawlers that visited me.