docs: reframe sandbox as team-shared in tutorials#184
Merged
Conversation
The earlier wording called the sandbox Foundry project `personal` and `private`, and the prompt-agent quickstart's Team tip suggested giving each developer their own sandbox project. In practice the sandbox project is usually fine for a small team to share - the contrast that matters is `saves never trigger CI` (sandbox) vs `CI promotes from here` (dev), not solo vs shared. - prompt-agent quickstart: drop `personal` / `private` from the intro, prerequisites table, ASCII diagram, naming list, and skill prompt. Replace the per-developer `Team tip` callout with a `Team scaling` note that recommends one shared sandbox by default and only suggests splitting if save collisions become a real problem. - hosted-agent quickstart: change `per developer` to `shared by the team (or per-stream / per-developer if your team prefers that)` and drop the leftover `shared blast radius` phrasing. - end-to-end tutorial: drop `private` / `personal/team author space` / `author's safe space` framing in the env layout block, the `Why a separate sandbox?` callout, and the wrap-up bullets. Tests: python -m pytest tests/ -x -q -> 773 passed, 3 skipped. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tightens the sandbox framing across the three tutorials.
Why
The earlier wording called the sandbox Foundry project personal and private, and the prompt-agent quickstart's Team tip suggested giving each developer their own sandbox project. In practice the sandbox project is usually fine for a small team to share - the contrast that matters is saves never trigger CI (sandbox) vs CI promotes from here (dev), not solo vs shared.
Changes
personal/privatefrom the intro, prerequisites table, ASCII diagram, naming list, and skill prompt. Replace the per-developerTeam tipcallout with aTeam scalingnote that recommends one shared sandbox by default and only suggests splitting if save collisions become a real problem.per developertoshared by the team (or per-stream / per-developer if your team prefers that)and drop the leftovershared blast radiusphrasing.private/personal/team author space/author's safe spaceframing in the env layout block, theWhy a separate sandbox?callout, and the wrap-up bullets.Validation
python -m pytest tests/ -x -q-> 773 passed, 3 skipped.Doc-only change; no code paths affected.