diff --git a/docs/features/experimental/codebase-indexing.mdx b/docs/features/experimental/codebase-indexing.mdx
index 60209014..74d3eb44 100644
--- a/docs/features/experimental/codebase-indexing.mdx
+++ b/docs/features/experimental/codebase-indexing.mdx
@@ -136,8 +136,9 @@ The indexer automatically excludes:
- **`text-embedding-ada-002`**: Legacy model, lower cost
**For Ollama:**
-- Choose models based on your hardware capabilities
-- Larger models provide better accuracy but require more resources
+- **`mxbai-embed-large`**: The largest and highest-quality embedding model.
+- **`nomic-embed-text`**: Best balance of performance and embedding quality.
+- **`all-minilm`**: Compact model with lower quality but faster performance.
### Security Considerations
- **API Keys**: Stored securely in VS Code's encrypted storage
@@ -185,4 +186,4 @@ Planned improvements:
- Multi-workspace indexing
- Enhanced filtering and configuration options
- Team sharing capabilities
-- Integration with VS Code's native search
\ No newline at end of file
+- Integration with VS Code's native search
diff --git a/docs/features/shell-integration.md b/docs/features/shell-integration.md
index d09e0d9a..7627b33c 100644
--- a/docs/features/shell-integration.md
+++ b/docs/features/shell-integration.md
@@ -74,6 +74,11 @@ Always restart all open terminals after changing any of these settings.
This setting controls whether Roo Code's terminal sessions use the same environment variables (like `PATH`, API keys, etc.) as your main VSCode/Cursor environment. It directly mirrors the VSCode global setting [`terminal.integrated.inheritEnv`](https://code.visualstudio.com/docs/editor/integrated-terminal#_inherit-environment-variables). Keep this enabled (default for VSCode) if you want Roo commands to operate with the same context and tools available in your regular VSCode terminal. Consider disabling it only if you need a completely clean, isolated environment for Roo's terminal tasks or are troubleshooting complex environment variable conflicts.
+### Runtime Environment
+On macOS (and possibly other operating systems) the environment provided to VSCode, and consequently Roo Code, can differ depending on how VSCode is launched.
+If launched from the command line `vscode` command, VSCode and Roo Code will inherit the environment from the shell that launched it, and all will (usually) be well.
+If launched from the Finder, Dock, or Spotlight, environment exported from `.zshrc`, or `.zprofile` will likely be missing. If you have environment variables set in one of those files, and find they are missing when running VSCode, move them to .zshenv, and log out and back in again, so the window manager will pick up the new environment settings.
+
#### Disable terminal shell integration
This setting determines how Roo Code executes terminal commands.
@@ -427,4 +432,4 @@ If you're still having issues:
- Steps to reproduce
- Error messages
-For additional help, join our [Discord](https://discord.gg/roocode).
\ No newline at end of file
+For additional help, join our [Discord](https://discord.gg/roocode).