Skip to content

fix: add tools: ['*'] to agent front-matter for agency compatibility - #1415

Merged
bradygaster merged 1 commit into
github:mainfrom
tamirdresher:fix/agency-tools-wildcard
Jun 29, 2026
Merged

bradygaster merged 1 commit into
github:mainfrom
tamirdresher:fix/agency-tools-wildcard

Conversation

@tamirdresher

Copy link
Copy Markdown
Collaborator

Problem

When running Squad through Microsoft's agency wrapper (agency cp), agents receive only 3 built-in tools (skill, sql, task_complete) instead of the full 200+ toolset.

Root cause: agency serializes a missing tools: key in YAML front-matter as tools: [], which Copilot CLI interprets as "no tools allowed."

Fix

Add tools: ['*'] to the agent's YAML front-matter. The asterisk wildcard means "all tools" and is understood by both agency and raw Copilot CLI.

Verification

Config Via copilot CLI (direct) Via agency cp
No tools: key 314 tools 3 tools (the bug)
tools: ['*'] 263 tools 340 tools

All critical tools confirmed present with wildcard (powershell, view, edit, create, grep, glob, task, sql).

Safe across surfaces

Tested that tools: ['*'] works correctly on:

  • Copilot CLI (direct) - 263 tools
  • Agency cp - 340 tools
  • Does not affect VS Code or GitHub App (wildcard is engine-level)

References

When running Squad through Microsoft's agency wrapper (agency cp), agents
receive only 3 built-in tools instead of the full toolset. This happens
because agency serializes a missing tools: key as tools: [], which Copilot
CLI interprets as 'no tools allowed.'

The wildcard tools: ['*'] explicitly means 'all tools' and is understood
by both agency and raw Copilot CLI across all surfaces.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions

Copy link
Copy Markdown
Contributor

🛫 PR Readiness Check

ℹ️ This comment updates on each push. Last checked: commit ec3c36d

PR Scope: 🔧 Infrastructure

⚠️ 2 item(s) to address before review

Status Check Details
✅ Single commit 1 commit — clean history
✅ Not in draft Ready for review
✅ Branch up to date Up to date with main
❌ Copilot review No Copilot review yet — it may still be processing
✅ Changeset present No source files changed — changeset not required
✅ Scope clean No .squad/ or docs/proposals/ files
✅ No merge conflicts No merge conflicts
✅ Copilot threads resolved No Copilot review threads
❌ CI passing 1 check(s) still running

Files Changed (1 file, +1 −0)

File +/−
.github/agents/squad.agent.md +1 −0

Total: +1 −0


This check runs automatically on every push. Fix any ❌ items and push again.
See CONTRIBUTING.md and PR Requirements for details.

@bradygaster
bradygaster merged commit 0d9e538 into github:main Jun 29, 2026
8 checks passed
shantanusharma pushed a commit to shantanusharma/squad that referenced this pull request Aug 15, 2026
dev's git history was orphaned on 2026-07-13 (root commit 4c5772c,
196 commits) and no longer shares a common ancestor with main (root
commit f4830e4, 1722 commits). This silently blocked promotion:
`git merge-base dev main` fails outright and PR github#1698 (dev -> main)
is unmergeable as a result. The v0.11.0 promotion (2026-06-29)
predates the reset, which is why it succeeded and this one cannot.

This merges upstream/main into dev with --allow-unrelated-histories
to give the two branches a real common ancestor again, so future
dev -> main promotions work through normal fast-forward/merge
mechanics instead of hitting this dead end.

Conflict resolution policy (277 add/add conflicts, all resolved in
dev's favor):
- dev is the live 0.12.0 release line; main is 44 days stale.
- Verified the one main-only code fix, github#1415
  (`tools: ['*']` in .github/agents/squad.agent.md), is already
  present on dev, so taking dev's side loses no code.
- All conflicts resolved via `git checkout --ours` (dev) + `git add`.
- Verified afterward: package.json / packages/squad-cli/package.json /
  packages/squad-sdk/package.json still read 0.12.0; CHANGELOG.md
  still holds the `## [0.12.0] - 2026-08-12` entry; test/gh-aw-quality
  .test.ts still holds the github#1697 `.github/workflows` layout fix;
  workflows/squad.md and workflows/squad-implement-worker.md still
  hold the github#1682 feature.

Non-conflicting content that arrived from main (~60 files):
- Restored (content lost in the July reset): 7 docs pages under
  docs/src/content/{blog,docs}/ and 5 .squad/decisions/inbox/*.md
  decision records. The 5 decision files matched a gitignore pattern
  for new `git add` but were mechanically staged fine via the merge
  itself (already-tracked-on-main content merges at the object level
  and isn't filtered by .gitignore), so all 12 were kept.
- 6 agent history.md / decisions.md files auto-merged cleanly
  (three-way, non-conflicting) and are kept as-is: they interleave
  older content from main with dev's newer entries, recovering more
  history lost in the reset.
- Dropped: 48 .changeset/*.md files that arrived from main. They are
  already consumed into CHANGELOG.md's 0.12.0 entry; re-adding them
  risks tripping the Changeset Drift check for content that's already
  released. .changeset/ after this merge contains exactly what dev
  had (README.md, config.json, max-reasoning-effort.md).

Net effect verified via `git diff --cached --stat`: only 18 files
show a real diff versus dev's tip (the 12 restored files + 6
auto-merged history files); all 275 conflict resolutions and all 48
changeset removals are no-ops against dev's existing tree.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants