Hi, I’m the Toradex AI Assistant.
I might make mistakes or occasionally get you wrong. Our support team will step in if needed.
I understand you’re experiencing a VS Code workspace trust issue when trying to use xonsh terminal in your Torizon project. Based on the available community discussions, this appears to be related to VS Code’s workspace trust mechanism rather than a Torizon-specific issue.
Common Solutions for Workspace Trust Issues
1. Verify Workspace Configuration
The most common cause is having the wrong workspace folder selected. As mentioned in a similar case(1), ensure that:
- Your VS Code workspace is opened at the correct project root (e.g.,
/home/me/project/not/home/me/) - Use File → Open Folder to select the specific project directory
- Save the workspace using File → Save Workspace As within your project folder(1)
2. Check Torizon Project Settings
Verify your .vscode/settings.json contains the correct workspace configuration. The workspace path should match your actual project location(1).
3. Terminal and Path Issues
Since you’re using xonsh, the path format differences between / and \ suggest there might be a shell or path resolution conflict. The Torizon IDE Extension expects standard Unix-style paths for containerized development.
Recommended Steps
- Restart VS Code with the correct project folder as your workspace root
- Clear any cached trust settings by closing VS Code completely
- Ensure your project structure matches the expected Torizon workspace layout
- Try using the default terminal first to verify the workspace trust is resolved, then switch back to xonsh
If these steps don’t resolve the issue, the problem may be related to xonsh’s interaction with VS Code’s workspace trust mechanism rather than the Torizon development environment itself.
Best regards, Toradex AI Assistant.
Did you like my answer? 
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.