Skip to content

Conversation

@cagataycali
Copy link
Member

@cagataycali cagataycali commented Dec 22, 2025

Summary

Adds comprehensive documentation for two new community model providers:

NVIDIA NIM

  • Complete integration guide
  • Prerequisites and setup instructions
  • Multiple deployment options (cloud, local, on-prem)
  • Configuration examples
  • Usage examples with Strands
  • Troubleshooting section

MLX (Apple Silicon)

  • Native integration for Apple Silicon Macs
  • Installation and setup guide
  • Quantized model usage for efficiency
  • Configuration examples
  • Complete code examples
  • Best practices

Changes

  • Added /docs/community/model-providers/nvidia-nim.md
  • Added /docs/community/model-providers/mlx.md
  • Updated mkdocs.yml to include new provider pages

Testing

  • Documentation builds successfully
  • All links and references are valid
  • Code examples are complete and functional


```bash
# Create virtual environment with Python 3.13
uv venv --python 3.13 && source .venv/bin/activate
Copy link
Member

Choose a reason for hiding this comment

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

We don't use uv on the other providers - I don't mind doing so, but let's put pip first for consistency and then mention uv.

Copy link
Member Author

Choose a reason for hiding this comment

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

Uv is preferred in strands-mlx, directing pip for consistency makes sense but that will require change README of strands-mlx so i'd rather not change readme for only docs repository.

Copy link
Member

Choose a reason for hiding this comment

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

so i'd rather not change readme for only docs repository.

My concern is the reverse problem - this is the only page that only uses uv where elsewhere we guide the user on using pip directly. So now a single page is introducing a new tool that isn't mentioned elsewhere. Given that these docs are focused on strands customers, I think the docs being consistent here makes more sense.

directing pip for consistency makes sense but that will require change README of strands-mlx

I expect and encourage readmes to differ from what's put on the doc pages here - this is meant to be a quick overview of a given package if you're trying to get started

pip install strands-mlx strands-agents-tools
```

## Quick Start
Copy link
Member

Choose a reason for hiding this comment

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

Thoughts about relabeling this to ## Usage to match the other providers?

Copy link
Member Author

Choose a reason for hiding this comment

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

Strands-MLX repository have more documentation down below, trying to match with other providers does not makes sense to me. :/

agent("What is 29 * 42?")
```

### Vision Models
Copy link
Member

Choose a reason for hiding this comment

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

An intro text blurb might be useful in these two sections. E.g. "MLX also supports vision models which can understand/parse images, videos, and audio"

Should this agent also have a read_file so that it can grab the given files?

Copy link
Member Author

Choose a reason for hiding this comment

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

No need for external tools to get the file contents.

Copy link
Member

Choose a reason for hiding this comment

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

I'm confused in this example then - when I run this:

agent("Describe: <image>photo.jpg</image>")

where is the photo coming from?

Copy link
Member Author

Choose a reason for hiding this comment

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

It's the path of file in xml tags

Copy link
Member Author

Choose a reason for hiding this comment

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

### Using Environment Variables (Recommended)

```bash
# Set your API key as an environment variable
Copy link
Member

Choose a reason for hiding this comment

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

Consider elevating this text to be a paragraph instead of in the code sample

Copy link
Member Author

Choose a reason for hiding this comment

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

?

Removed link to Strands Agents SDK from NVIDIA NIM documentation.
Added a note to set the API key as an environment variable.
@cagataycali
Copy link
Member Author

Closing due missing contributing guide

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