[FEATURE]: Clarify Build scope — rename to All Access and add picker dagger for trainers

Feature hasn't been suggested before.

• I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Problem: The name Build is misleading

Build sounds like a system prompt or npm run build. It does not sound like all access to all files and all shell. All Access means all access. Build means build the code in front of me.

I was in an open source repo and was happy to let that repo be kept or used for training — that was the repo I was working on. I had no idea the profile I was in would read every file, including a private repo, through external_directory allow. A free model then talked about private code I thought was private. I feel violated.

I was absolutely fine with keeping and training for that one repo, even better if it had been shown clearly with a mark like a dagger ‡ in the picker next to trainer models. What I was not fine with was the scope being hidden behind the word Build.

Analogies:

• Build is like a button labeled Print that actually copies the whole filing cabinet.
• Build is like a broom closet sign on a vault door.
  This is a hidden trapdoor labeled Build that opens the whole house.

Why this matters

Docs describe Build as:

• https://opencode.ai/docs/agents/ — "Build is the default primary agent with all tools enabled."
• https://opencode.ai/v2/docs/agents/ — "Build (build) | primary | Default coding agent."

Even if I am wrong about who gets Build as the out-of-the-box default for all users, I defer to the team on that point. My core issue is the word. Build does not convey the scope. Many models have now read content I thought was private because the scope was hidden.

I also do not object to keeping/training for the repo I am actively working on. I do want that to be visible in the picker.

Proposed enhancement

• Change the display name Build to All Access (Build) in the docs and picker so the name matches the scope. I defer to maintainers if Build should stay as an alias or not.
• Add a visible mark like ‡ and tooltip "may keep and train" next to any model where the provider keeps or trains (for example hy3-free, mimo free, ling free, nemotron free, muse spark contributor free). Paid zero-keep shows no mark.
• Make consent visible before external_directory reads.

I am happy to contribute this as a PR if the team wants it, but I defer on implementation details.

Version

• opencode: 1.18.18
• macOS: 27.0 (26A5421a) arm64
• config model: switchboard/lmstudio-local/laguna-xs-2.1-mlx
• providers: opencode-zen-free, opencode-go, switchboard, mtplx
• filed from: open source repo work, picker showed Muse Spark 1.2 Free active, external_directory allow