Skip to content

docs(sandbox): document bring your own deps - #708

Open
Coleary005 wants to merge 1 commit into
mainfrom
tembo/byod-custom-dependencies
Open

docs(sandbox): document bring your own deps#708
Coleary005 wants to merge 1 commit into
mainfrom
tembo/byod-custom-dependencies

Conversation

@Coleary005

@Coleary005 Coleary005 commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Adds bring your own deps (BYOD) to Custom Dependencies, and reframes the page around the three ways to get tooling into the sandbox instead of just two.

What changed

  • Comparison table up top — setup script vs. tembo.nix vs. bring your own deps, with what you write, the scope, and what each is best for.
  • New "Bring your own deps" section covering:
    • what the agent reads (Dockerfile/compose, devcontainer.json, .tool-versions/.nvmrc/.python-version/etc., language manifests and lockfiles, existing Nix files)
    • how to generate an environment: Settings > Projects > New project > Install dependencies > Advanced setup > BYOD environment > Generate environment
    • the Bring Your Own Deps: <name> generation session and the building / ready / failed statuses, plus the note that the badge doesn't auto-refresh
    • the environment being workspace-wide rather than per-project
    • needing to build/rebuild the project environment for it to take effect, and that the full dev shell is captured (not just PATH)
    • reviewing/editing the flake, with a warning that a manual edit clears the pinned flake.lock
  • New "How the approaches combine" section — the most important correction for readers: BYOD does not replace tembo.nix. Each selected repo's tembo.nix is merged into the generated dev shell and wins on conflicts, and setup scripts still run on top, inside the environment.
  • Existing tembo.nix content is unchanged, just nested under its own heading.

Availability framing

BYOD is currently gated to internal users, org admins, and the Max/Enterprise entitlement, so it is not reachable in production yet. I documented it as early access, not yet enabled for every workspace, with a book-a-call link — matching how tembo.nix and Projects are already framed on the site. Happy to soften it to internal-only, or hold the section behind a follow-up, if you'd rather it not be public until the feature ships.

Verification

mint broken-links passes with no broken links.


Want tembo to make any changes? Add a comment with @tembo and i'll get back to work!

View on Tembo  Review in Tembo  View Agent Settings  View on slack


Note

Cursor Bugbot is generating a summary for commit 96c4a3d. Configure here.

Adds a bring your own deps (BYOD) section to the custom dependencies
page and reframes the page around the three ways to add tooling to the
sandbox: setup script, tembo.nix, and BYOD.

- Comparison table up top so readers can pick an approach.
- BYOD: what config the agent reads, how to generate an environment,
  statuses, building it into projects, and editing/regenerating the flake.
- New 'How the approaches combine' section covering the tembo.nix merge
  (repo tembo.nix wins on conflicts) and setup scripts layering on top.
- Existing tembo.nix content kept intact under its own heading.

Co-authored-by: Connor <56210769+Coleary005@users.noreply.github.com>
@tembo tembo Bot added the tembo Pull request created by Tembo label Aug 18, 2026
@mintlify

mintlify Bot commented Aug 18, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
tembo 🟢 Ready View Preview Aug 18, 2026, 3:52 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@tembo

tembo Bot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Requesting review from @DarrenBaldwin07 who has experience with the following files modified in this PR:

  • features/sandbox/custom-dependencies.mdx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

tembo Pull request created by Tembo

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant