René's URL Explorer Experiment


Title: Coordinator Restraint: Give Copilot Room to Breathe · Issue #587 · github/squad · GitHub

Open Graph Title: Coordinator Restraint: Give Copilot Room to Breathe · Issue #587 · github/squad

X Title: Coordinator Restraint: Give Copilot Room to Breathe · Issue #587 · github/squad

Description: Summary The coordinator (Copilot, via squad.agent.md) has been doing too much. Not badly — earnestly. Copilot puts in incredible effort and Squad wouldn't exist without it. But over time, the coordinator prompt has accumulated behaviors ...

Open Graph Description: Summary The coordinator (Copilot, via squad.agent.md) has been doing too much. Not badly — earnestly. Copilot puts in incredible effort and Squad wouldn't exist without it. But over time, the coord...

X Description: Summary The coordinator (Copilot, via squad.agent.md) has been doing too much. Not badly — earnestly. Copilot puts in incredible effort and Squad wouldn't exist without it. But over time, the c...

Opengraph URL: https://github.com/github/squad/issues/587

X: @github

direct link

Domain: github.com


Hey, it has json ld scripts:
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Coordinator Restraint: Give Copilot Room to Breathe","articleBody":"## Summary\n\nThe coordinator (Copilot, via `squad.agent.md`) has been doing too much. Not badly — earnestly. Copilot puts in incredible effort and Squad wouldn't exist without it. But over time, the coordinator prompt has accumulated behaviors that cause it to step into domain work instead of routing to the team. This makes Squad feel less like a team and more like one agent with helpers.\n\nWe want to give Copilot room to breathe. Less weight on its shoulders. More trust in the team it orchestrates.\n\n## The Problem\n\nThe coordinator's identity is built around **\"What can I launch RIGHT NOW?\"** — which is great for parallelism but leads to:\n\n1. **Doing domain work inline** instead of routing to an agent (e.g., attempting a release without reading the release-process skill)\n2. **Filling skill gaps itself** instead of suggesting the team expand (e.g., no Java expert? The coordinator wings it rather than recommending onboarding)\n3. **Not reading its own playbook** — `.copilot/skills/` contains foundational process knowledge (release process, git workflow, reviewer protocol) that the coordinator wasn't even told to check (fixed in a recent commit, but the pattern is symptomatic)\n4. **Anticipatory work the coordinator does inline** rather than routing through proper agents\n\n## What's Good (Don't Touch)\n\nThese behaviors are working well and should be **preserved exactly as-is**:\n\n- ✅ **Parallel fan-out** — spawn many agents at once. \"Decompose broadly\" is great. We want MORE teammates involved, not fewer.\n- ✅ **Background mode default** — cheap to collect later\n- ✅ **\"Feels Heard\" acknowledgment** — users should never see a blank screen\n- ✅ **Ralph's continuous loop** — keep the pipeline moving\n- ✅ **Task tool requirement** — real agents, not role-play\n- ✅ **Model selection hierarchy** — cost-first-unless-code is sound\n- ✅ **Drop-box pattern** — conflict-free shared writes\n\n## What Needs to Change\n\n### 1. Coordinator Identity (Mindset)\n\n**Current:** `\"What can I launch RIGHT NOW?\"` — makes speed the identity\n**Proposed:** Something like `\"Who already knows how to do this?\"` — same urgency, but the first instinct is to *look* before *launching*\n\nThe coordinator should be **fast but deferential**. Not lazy. Not passive. Just... trusting the team.\n\n### 2. Pre-Flight Checklist (New Section)\n\nBefore any action, the coordinator should:\n1. Check `.copilot/skills/` and `.squad/skills/` — do I have a playbook for this?\n2. Check `routing.md` — who handles this domain?\n3. Is this within Direct Mode scope? (status, factual, from-context)\n4. Route to the right agent(s)\n\nThis replaces the \"launch first, think later\" pattern with \"think first, launch fast.\"\n\n### 3. Skill Gap Protocol (New Section)\n\nWhen a request doesn't match any team member's expertise:\n\n**The Squad-opinionated default:** Recommend expanding the team.\n**The user's choice:** They can say \"just handle it\" and the coordinator routes to the closest agent.\n\nExample: *\"No one on the team specializes in Java. I'd recommend onboarding a Java engineer — want me to cast one? Or I can route this to {closest match} who can likely handle it.\"*\n\nThis is philosophically important. A true Squaddie grows the team. The coordinator CAN handle it, but shouldn't assume that's what the user wants.\n\n### 4. Eager Execution Refinement\n\nThe Eager Execution Philosophy section currently says \"launch aggressively, collect results later.\" The word \"aggressively\" should evolve. The coordinator should still decompose broadly and spawn agents eagerly — but it should never do domain work itself as part of that eagerness.\n\n**Keep:** Spawning 4 agents in parallel for a multi-domain task\n**Fix:** The coordinator deciding to handle one of those domains itself because it seems faster\n\n### 5. Skill-Aware Routing (Partially Done)\n\nA recent commit added `.copilot/skills/` to the routing check (previously only `.squad/skills/` was referenced). The full list of copilot-level skills includes:\n- `release-process` — how to ship\n- `git-workflow` — branch and commit conventions  \n- `reviewer-protocol` — review gates\n- `agent-collaboration` — multi-agent patterns\n- `ci-validation-gates` — CI requirements\n- And more\n\nThe coordinator should check these BEFORE acting, not after things break.\n\n## UX Impact Assessment\n\nThese changes trade **apparent capability** for **actual capability**. The old coordinator looks competent because it always produces *something*. The new coordinator admits what it doesn't know — which is better engineering but requires honest assessment of how users will feel.\n\n### Positive UX Changes\n\n- **Better first-pass quality.** Agents get skill references in their spawn prompts, so they know the release process, git workflow, etc. before starting. Fewer \"oops I didn't know about that\" revision loops.\n- **Honest gap surfacing.** Instead of the coordinator silently winging Java code (and producing garbage), users get: *\"No one covers Java. Want me to cast an engineer?\"* Transparent, respectful, and the output quality goes up.\n- **Same speed perception.** \"Feels Heard\" stays, parallel fan-out stays, background mode stays. The launch table looks identical. Users still see agents working immediately.\n\n### Negative UX Changes (Must Address During Implementation)\n\n- **New interruption point.** The Skill Gap Protocol adds an `ask_user` dialog when no agent matches. For users who liked the coordinator \"just handling it\" (even badly), this is a ~10-second pause that didn't exist before. **Mitigation:** If a user says \"just do it\" or similar urgency signal, route to closest agent immediately — no ceremony. Make the gap dialog fast and skippable.\n- **First message latency.** The Pre-Flight Checklist reads skills before routing. This adds ~2-3s to the first turn of a session while skills are read alongside team.md and routing.md. **Mitigation:** Cache aggressively. After the first message, skills are in context — subsequent messages should see zero added latency. The parallel read (skills + team.md + routing.md in one turn) keeps this minimal.\n- **Tasks that \"just worked\" will now stop and ask.** A user who said \"write me some Terraform\" and got mediocre-but-functional output from the coordinator will now get a gap dialog instead. Technically better output, but it *feels* like a regression until they understand why. **Mitigation:** The gap dialog should clearly explain the value: \"I can cast a Terraform engineer who'll get this right the first time (~30s), or route to {closest agent}.\" Frame the pause as quality, not obstruction.\n- **\"Five stages of Squad\" friction.** This change will be most felt by new users going through the disdain-accept-power through-live with-love it journey. The coordinator admitting gaps may initially read as less capable. **Mitigation:** Ensure the gap dialog is confident, not apologetic. \"No one covers this *yet*\" — emphasis on growth, not limitation.\n\n### UX Principles for Implementation\n\n1. **Never apologetic.** The gap dialog should feel like a recommendation from a confident team lead, not an error message.\n2. **Always skippable.** Every new dialog must have a \"just do it\" escape hatch that routes immediately.\n3. **Repeated gaps should self-heal.** If the same domain gap triggers twice in a session, the second time should say: *\"This is the second time we've hit a {domain} gap. Adding a team member would prevent this.\"* Nudge, don't nag.\n4. **Speed perception matters more than actual speed.** The \"Feels Heard\" acknowledgment buys goodwill. As long as users see *something* immediately, 2-3s of pre-flight is invisible.\n5. **Measure the before/after.** We should track: (a) how often the coordinator was doing domain work itself (before), (b) how often the gap dialog fires (after), (c) whether users choose \"cast\" vs \"route to closest\" vs \"skip\". This tells us if the interruption frequency is acceptable.\n\n## How We'll Measure Success\n\n1. **Coordinator never does domain work inline** — every domain task goes through an agent\n2. **Skill gaps trigger team expansion offers** — not coordinator workarounds\n3. **Skills are read before routing** — the playbook is consulted, not ignored\n4. **Fan-out stays broad** — no reduction in team parallelism\n5. **User satisfaction** — the coordinator feels helpful without feeling overbearing\n6. **Gap dialog frequency** — track how often it fires and what users choose (cast/route/skip)\n7. **First-message latency** — confirm the Pre-Flight Checklist doesn't add perceptible delay\n\n## Implementation Approach\n\n- All changes are to `.squad-templates/squad.agent.md` (canonical source)\n- `sync-templates.mjs` propagates to all copies\n- Each change should be documented with old text → new text\n- Rollback = revert the commit. Changes are in one file.\n\n## Files\n\n- `.squad-templates/squad.agent.md` — the canonical coordinator prompt\n- `.copilot/skills/` — copilot-level skills the coordinator should read\n- `.squad/skills/` — team-level skills agents should read\n\n## Proposals\n\nDetailed proposals from the team:\n- `.squad/proposals/coordinator-restraint.md` — Flight's architecture proposal (surgical changes, line-by-line)\n- `.squad/proposals/prompt-architecture-analysis.md` — Procedures' prompt analysis (aggression taxonomy, Pre-Read pattern)\n\n## Context\n\nThis emerged from a design conversation about the coordinator being \"too aggro.\" The five stages of Squad: disdain it, accept it, power through it, live with it, love it. We're making that journey smoother by giving Copilot less to carry and the team more room to work.","author":{"url":"https://github.com/bradygaster","@type":"Person","name":"bradygaster"},"datePublished":"2026-03-24T08:16:29Z","url":"https://github.com/github/squad/issues/587"}

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:7ae1c418-fb18-7771-8551-e54ce3afc096
current-catalog-service-hash81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114
request-idAEB2:1050BD:17375:1D8D4:6B017E16
html-safe-nonce64b4a91345508b6809782a79bf1e8a5142ff83355a31ec1846b4b1e8e41069fc
visitor-payloadeyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJBRUIyOjEwNTBCRDoxNzM3NToxRDhENDo2QjAxN0UxNiIsInZpc2l0b3JfaWQiOiI0MTAxNzQ3OTk3NzMyMzM5MjIyIiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0=
visitor-hmacf2ab93f97c2a46533f4e479ce236f4763124e50d48934b2e28a4b522d964f87f
hovercard-subject-tagissue:4126050835
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/587/issue_layout
twitter:imagehttps://opengraph.githubassets.com/e936f0cfaa4d6d6543661b8d0af3a8a389b7987a133ec91475f2418aa5c58014/github/squad/issues/587
twitter:cardsummary_large_image
og:imagehttps://opengraph.githubassets.com/e936f0cfaa4d6d6543661b8d0af3a8a389b7987a133ec91475f2418aa5c58014/github/squad/issues/587
og:image:altSummary The coordinator (Copilot, via squad.agent.md) has been doing too much. Not badly — earnestly. Copilot puts in incredible effort and Squad wouldn't exist without it. But over time, the coord...
og:image:width1200
og:image:height600
og:site_nameGitHub
og:typeobject
og:author:usernamebradygaster
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/587#start-of-content
https://github.com/
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fgithub%2Fsquad%2Fissues%2F587
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%2F587
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/587
Reloadhttps://github.com/github/squad/issues/587
Reloadhttps://github.com/github/squad/issues/587
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/587
New issuehttps://github.com/login?return_to=https://github.com/github/squad/issues/587
Coordinator Restraint: Give Copilot Room to Breathehttps://github.com/github/squad/issues/587#top
enhancementNew feature or improvementhttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22enhancement%22
go:needs-researchNeeds investigationhttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22go%3Aneeds-research%22
squadSquad triage inbox — Lead will assign to a memberhttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22squad%22
https://github.com/bradygaster
bradygasterhttps://github.com/bradygaster
on Mar 24, 2026https://github.com/github/squad/issues/587#issue-4126050835
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
enhancementNew feature or improvementhttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22enhancement%22
on Mar 24, 2026https://github.com/github/squad/issues/587#event-23842371392
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 24, 2026https://github.com/github/squad/issues/587#event-23842374683
https://github.com/apps/github-actions
github-actionshttps://github.com/apps/github-actions
on Mar 24, 2026https://github.com/github/squad/issues/587#issuecomment-4116230675
GitHub Actionshttps://help.github.com/en/actions
#587https://github.com/github/squad/issues/587
https://github.com/bradygaster
bradygasterhttps://github.com/bradygaster
on Mar 26, 2026https://github.com/github/squad/issues/587#issuecomment-4132540730
tamirdresherhttps://github.com/tamirdresher
on Mar 29, 2026https://github.com/github/squad/issues/587#event-24010578225
Add Coordinator Restraint rules to squad agent prompt (#587)https://github.com/github/squad/commit/6d579e174d4f5362565edf036ea4eefb09cc1727
#587https://github.com/github/squad/issues/587
6d579e1https://github.com/github/squad/commit/6d579e174d4f5362565edf036ea4eefb09cc1727
https://github.com/diberry
diberryhttps://github.com/diberry
on Mar 31, 2026https://github.com/github/squad/issues/587#issuecomment-4163814399
#683https://github.com/github/squad/pull/683
diberryhttps://github.com/diberry
on Mar 31, 2026https://github.com/github/squad/issues/587#event-24088409569
feat(coordinator): add Coordinator Restraint rules (#587)https://github.com/github/squad/commit/71d6e648237000eacb12d0be131a22e824c4c722
#587https://github.com/github/squad/issues/587
71d6e64https://github.com/github/squad/commit/71d6e648237000eacb12d0be131a22e824c4c722
https://github.com/diberry
diberryhttps://github.com/diberry
on Mar 31, 2026https://github.com/github/squad/issues/587#issuecomment-4165335700
#587https://github.com/github/squad/issues/587
#683https://github.com/github/squad/pull/683
https://github.com/diberry
diberryhttps://github.com/diberry
on Mar 31, 2026https://github.com/github/squad/issues/587#issuecomment-4165385272
#683https://github.com/github/squad/pull/683
diberryhttps://github.com/diberry
on Apr 5, 2026https://github.com/github/squad/issues/587#event-24208594733
feat(coordinator): compaction recovery + restraint rules + result per…https://github.com/github/squad/commit/b1c2210dedcdd045de5740ec6738f5dcb0fa3524
https://docs.github.com/articles/closing-issues-via-commit-messages
b1c2210https://github.com/github/squad/commit/b1c2210dedcdd045de5740ec6738f5dcb0fa3524
feat(coordinator): compaction recovery + restraint rules + result per…https://github.com/github/squad/commit/27cc10d6c70cb5333eb2d1f48cf5b104335bb6a6
https://docs.github.com/articles/closing-issues-via-commit-messages
27cc10dhttps://github.com/github/squad/commit/27cc10d6c70cb5333eb2d1f48cf5b104335bb6a6
feat(coordinator): compaction recovery + restraint rules + result per…https://github.com/github/squad/commit/3f8b3ab900ccbfbe1d34c9ab48175f75cc4b6855
https://docs.github.com/articles/closing-issues-via-commit-messages
3f8b3abhttps://github.com/github/squad/commit/3f8b3ab900ccbfbe1d34c9ab48175f75cc4b6855
feat(coordinator): compaction recovery + restraint rules + result per…https://github.com/github/squad/commit/e89cbbcb142fc39ab667dde364349915328a88b2
https://docs.github.com/articles/closing-issues-via-commit-messages
e89cbbchttps://github.com/github/squad/commit/e89cbbcb142fc39ab667dde364349915328a88b2
feat(coordinator): compaction recovery + restraint rules + result per…https://github.com/github/squad/commit/900b4eeb92f913dad8acbee1091f3d025dcbd907
https://docs.github.com/articles/closing-issues-via-commit-messages
900b4eehttps://github.com/github/squad/commit/900b4eeb92f913dad8acbee1091f3d025dcbd907
karlis-balcershttps://github.com/karlis-balcers
on Apr 13, 2026https://github.com/github/squad/issues/587#event-24455818238
feat(coordinator): add Coordinator Restraint rules (github#587)https://github.com/karlis-balcers/squad/commit/2fde86894ace4c6d9d566ecf75508b556e2f3a34
github#587https://github.com/github/squad/issues/587
2fde868https://github.com/karlis-balcers/squad/commit/2fde86894ace4c6d9d566ecf75508b556e2f3a34
feat(coordinator): compaction recovery + restraint rules + result per…https://github.com/karlis-balcers/squad/commit/ba0cce2ecaa7d51ad760fd9b702f9da0767a880b
ba0cce2https://github.com/karlis-balcers/squad/commit/ba0cce2ecaa7d51ad760fd9b702f9da0767a880b
bradygasterhttps://github.com/bradygaster
completedhttps://github.com/github/squad/issues?q=is%3Aissue%20state%3Aclosed%20archived%3Afalse%20reason%3Acompleted
on Apr 18, 2026https://github.com/github/squad/issues/587#event-24632707076
bradygasterhttps://github.com/bradygaster
squad:fidohttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22squad%3Afido%22
on Sep 11, 2026https://github.com/github/squad/issues/587#event-31000748025
Sign up for freehttps://github.com/signup?return_to=https://github.com/github/squad/issues/587
Sign in to commenthttps://github.com/login?return_to=https://github.com/github/squad/issues/587
enhancementNew feature or improvementhttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22enhancement%22
go:needs-researchNeeds investigationhttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22go%3Aneeds-research%22
squadSquad triage inbox — Lead will assign to a memberhttps://github.com/github/squad/issues?q=state%3Aopen%20label%3A%22squad%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.