You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit c9d2281
Browse filesBrowse the repository at this point in the historyBrowse files
fix(acq-kits): bump opencode kit to OpenCode 2.0.30 (#499)
## Summary
Bumps the `opencode` acq kit from OpenCode 2.0.22 to 2.0.30, the first
release that loads config `instructions` again (upstream
anomalyco/opencode#55539). Only `spec.yaml` changes: the version and the
three Linux SHA-256 pins.
## Verification
- Hashes computed from the npm tarballs; each matches npm's published
sha512 integrity.
- `make validate`, `validate-kits.py --strict`, and `acq kit validate`
pass.
- Live `RUN_ACQ=1` kit verify (msb 0.7.8, acq 4.0.2,
`devenv-shell:2.0.0`): 23 passed, 0 failed, with 2.0.30 installed.
- An `OPENCODE_CONFIG` probe confirmed 2.0.30 loads `instructions`; the
control without the config returned `NONE`.
## Eligibility & Accountability
- [x] I am a **federal employee or contractor** (PRs merge with
`@GSA-TTS/agentic-coding-team` code-owner approval; eligibility is
attested here, not authenticated).
- [x] **I understand this change and can explain it in my own words** —
I am the author of record and accountable for it.
- [x] By opening this PR, I **attest I have the right to release this
work** under the repository's CC0-1.0 dedication.
## AI Assistance Disclosure
- [x] AI tools were used in this contribution.
- [x] I verified all AI-generated content.
Relates to #482
Copy file name to clipboardExpand all lines: integrations/isolation/acq-kits/examples/team-kit/docs/decisions/0001-team-settings-through-opencode-config.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ that variable; a personal kit does not override it.
25
25
- Settings tier global → team → repo, with no merge script in this kit.
26
26
-`OPENCODE_CONFIG` is single-valued and last-wins across kits, so any later
27
27
kit that sets it hides the team settings without a warning.
28
-
- The conventions reach the agent through OpenCode's `instructions` field,
29
-
which OpenCode 2.x ignores. On an image whose sandbox shells run 2.x, the
30
-
team settings still apply but the conventions do not load; `scripts/verify`
31
-
fails there.
28
+
- The conventions reach the agent through OpenCode's `instructions` field.
29
+
OpenCode 2.0.0 through 2.0.29 accepted that field but did not load its files;
30
+
OpenCode 2.0.30 fixed the behavior. On an affected image, the team settings
31
+
still apply but the conventions do not load; `scripts/verify`fails there.
Copy file name to clipboardExpand all lines: integrations/isolation/docs/scope-layers.md
+15-14Lines changed: 15 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -157,7 +157,7 @@ acq secret set -g <service> --host <host> --env <VAR> # once per machine, host
157
157
| Need | Mechanism |
158
158
|------|-----------|
159
159
| Egress for team hosts (VCS, package mirrors, MCP servers) |`caps.network.allow` (union) |
160
-
| Conventions the agent must follow across the team's repos | A markdown file under `files/`, registered in the agent's instructions path (OpenCode: an `instructions` entry in a team config file). OpenCode 2.x does not load `instructions` files (see [Check against your acq](#check-against-your-acq)). |
160
+
| Conventions the agent must follow across the team's repos | A markdown file under `files/`, registered in the agent's instructions path (OpenCode: an `instructions` entry in a team config file). OpenCode 2.0.0 through 2.0.29 do not load `instructions` files (see [Check against your acq](#check-against-your-acq)). |
161
161
| Team agent settings that override the global defaults | Ship a config file and point the agent's config env var at it (OpenCode: `OPENCODE_CONFIG` in `environment`), giving the tier global → team → repo. Never pin `model` / `small_model` there, and never add an `allow` rule that overrides a global ask or deny (see the gotchas). |
162
162
| Team TUI settings (OpenCode theme, keybinds) | A separate `tui.jsonc`, with `OPENCODE_TUI_CONFIG` pointing at it: OpenCode drops `theme` / `keybinds` / `tui` from `opencode.json(c)` on load. The variable is single-valued, so say in the team README whether a personal kit may override it. |
163
163
| Gating a team CLI (for example the VCS CLI) | Permission rules in the team config, in the same default-allow posture as the global kit: reads fall through to its `"*": "allow"`; `ask` before anything that posts or opens a merge request; `deny` merge and approve, pipeline runs, CI variables, destructive admin commands, and the `api` subcommand's write flags and GraphQL. Any write verb you do not list stays allowed, so review your CLI's close, edit, delete, label, release, and CI retry verbs. Rules match the whole command text, so write each from the exact command prefix and see the gotchas. The team-kit template's `opencode.jsonc` sketches the shape. |
@@ -213,7 +213,7 @@ global layer does.
213
213
| Terminfo for your terminal | Ship the *source* (`infocmp -x`) and compile it in a startup step (`tic -x`) |
214
214
| Git preferences | One startup command per key, or ship a file and add it with `include.path`|
215
215
| Overriding a team setting |`environment` (last wins) or a later file at the same path (last wins) — deliberately, and only for settings the team marks as personal |
216
-
| Your own agent instructions (OpenCode) | A file under `files/`, added through `OPENCODE_CONFIG_CONTENT` in `environment`, for example `{"instructions":["/home/agent/personal/instructions.md"]}`. Do not append to the global rules file: the playbook kit symlinks `~/.config/opencode/AGENTS.md` and `~/.claude/CLAUDE.md` into its managed checkout, so an append edits that checkout. In a local test on OpenCode 1.18, the `instructions` lists combine in order (global, then team through `OPENCODE_CONFIG`, then this one); OpenCode's docs do not say how lists merge, and OpenCode 2.x does not load `instructions` files (see [Check against your acq](#check-against-your-acq)). Put nothing else in it: inline config loads after the repo's own config, so any other key overrides the repo. The variable is single-valued (last kit wins). |
216
+
| Your own agent instructions (OpenCode) | A file under `files/`, added through `OPENCODE_CONFIG_CONTENT` in `environment`, for example `{"instructions":["/home/agent/personal/instructions.md"]}`. Do not append to the global rules file: the playbook kit symlinks `~/.config/opencode/AGENTS.md` and `~/.claude/CLAUDE.md` into its managed checkout, so an append edits that checkout. In a local test on OpenCode 1.18, the `instructions` lists combine in order (global, then team through `OPENCODE_CONFIG`, then this one); OpenCode's docs do not say how lists merge, and OpenCode 2.0.0 through 2.0.29 do not load `instructions` files (see [Check against your acq](#check-against-your-acq)). Put nothing else in it: inline config loads after the repo's own config, so any other key overrides the repo. The variable is single-valued (last kit wins). |
217
217
| Extra egress for your tools |`caps.network.allow` (union) |
0 commit comments