docs(agents): upgrade agent-foundry to b04e778 #46
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "chore/foundry-upgrade-b04e778"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
The agent policy, skills and client settings come from Agent Foundry,
pinned at 6df8975. The source has since gained 102 commits: shared
skills for sandboxed runs, proofs on main and settling review findings,
a pull request template, OpenCode 2 plugins, and Claude Code settings
that keep secret files from agents. This brings the repository to
b04e778 through the
foundry-upgradeskill's three-way merge.What changed
AGENTS.mdsections are unchanged, apart from saying "agent jail" forthe container so it reads apart from Claude Code's sandbox.
It asks before edits to the agent policy files and before the landing
merge, and runs Bash in its sandbox. In Manual and
acceptEditsmode,sandboxed commands,
ansible-playbook,sshandgit pushincluded,no longer ask first. CONTRIBUTING § Working with coding agents says
this, says what stays open, and says how an operator gets the prompt
back.
change).
.forgejo/pull_request_template.md.How to verify
<clone>/scripts/verify-agent-config.sh .on the branch. It printsagent configuration statically valid.make check: exit 0.git -C <clone> diff 6df8975 b04e778againstgit diff main.Every file except
AGENTS.md, CONTRIBUTING and the Record equals thesource.
Steps 1 and 2 pass on this tip.
make test, molecule andtag_propagation, was not run because the agent environment has nopodman.
Considerations
The settings follow the source in full, sandbox included, by
deliberate choice. Three low wording findings from the second review
round are set aside as below the bar: "nothing asks" also covers the
landing merge, which still asks; a missing comma after
socat; "theremedy for each" also covers the missing-tool case, which has no remedy
in the guide.