Skip to content

docs: add UID/GID mapping section to Agent Drive overview#582

Open
devin-ai-integration[bot] wants to merge 2 commits into
mainfrom
devin/1779930141-drive-uid-gid-mapping
Open

docs: add UID/GID mapping section to Agent Drive overview#582
devin-ai-integration[bot] wants to merge 2 commits into
mainfrom
devin/1779930141-drive-uid-gid-mapping

Conversation

@devin-ai-integration
Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration Bot commented May 28, 2026

Summary

Adds a new "Map UID/GID on mount" subsection to the Agent Drive Overview page, documenting the optional UID/GID mapping feature introduced in sandbox#211.

The section covers:

  • How to pass uidMap/gidMap when mounting a drive (TypeScript and Python examples)
  • How the mapping works (local UID/GID maps to filer UID/GID 0)
  • Default mapping via BLFS_UID_MAP and BLFS_GID_MAP environment variables
  • Override priority (request > env var > no mapping)

Review & Testing Checklist for Human

  • Verify the TypeScript SDK parameter names match the actual SDK (uidMap, gidMap)
  • Verify the Python SDK parameter names match the actual SDK (uid_map, gid_map)
  • Preview the page locally with npx mint dev to confirm rendering

Notes

This section is placed after "Mount a drive as read-only" and before "List mounted drives", following the existing H3 pattern for mount options.

Link to Devin session: https://app.devin.ai/sessions/1dfaeffa257b47078447110cbb2007fc
Requested by: @Joffref


Note

Adds a "Map UID/GID on mount" subsection to the Agent Drive Overview, documenting uidMap/gidMap mount parameters and BLFS_UID_MAP/BLFS_GID_MAP environment variables. The follow-up commit removes internal filer references that shouldn't be in public docs.

Written by Mendral for commit affe4e8.

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
@devin-ai-integration
Copy link
Copy Markdown
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR that start with 'DevinAI' or '@devin'.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@mintlify
Copy link
Copy Markdown
Contributor

mintlify Bot commented May 28, 2026

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

Project Status Preview Updated (UTC)
blaxel 🟢 Ready View Preview May 28, 2026, 1:04 AM

@devin-ai-integration
Copy link
Copy Markdown
Contributor Author

Devin is archived and cannot be woken up. Please unarchive Devin if you want to continue using it.

mendral-app[bot]

This comment was marked as outdated.

Copy link
Copy Markdown
Contributor

@Joffref Joffref left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

DevinAI don't mention filer and the UID/GID on its end, it's more confusing than anything

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Copy link
Copy Markdown
Contributor

@mendral-app mendral-app Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

No previous comments to address (prior review was LGTM). The new commit cleanly removes internal filer references, leaving the public documentation accurate and consistent.

Tag @mendral-app with feedback or questions. View session

@vikram-blaxel
Copy link
Copy Markdown
Collaborator

@Joffref not sure if you want to merge this now or later but lgtm from my side.

@Joffref
Copy link
Copy Markdown
Contributor

Joffref commented Jun 2, 2026

@vikram-blaxel I believe it hasn't been merge correctly in SDKs. We need to fix auto-gen of the SDK.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants