Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1d536cbc92
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
5_lmlink/qna.md
Outdated
| A: If you are loading the model via LM Studio or `lms load`, the same model on different devices will show up as separate entries, with the device name identified. If you are loading models via API/SDK, you can set a preferred device from the in-app LM Link page, or use command `lms link set-preferred-device`. Once set, the model will always load on your preferred device. | ||
|
|
||
| #### Q: Can linked devices access resources on my computer? | ||
| A: No. LM Link does not modify your operating system, and your devices are not exposed to each other. Only LM Studio/llmster instances can communicate with each other through LM Link. |
There was a problem hiding this comment.
and your devices are not exposed to each other.
I am not sure what this means, but we are connecting the devices so they are clearly somewhat "exposed" to each other.
There was a problem hiding this comment.
Q: Can linked devices do anything besides LM Studio tasks on my computer?
A: No. LM Link only lets LM Studio/llmster talk to each other for model and API access. It does not expose your operating system, files, or other services to linked devices.
How does this sound?
There was a problem hiding this comment.
Wouldn't users be able to upload files/images to the remote server with the API? Do this enough times and the OS runs out of disk space
Co-authored-by: rugvedS07 <rugved@lmstudio.ai>
Co-authored-by: Neil Mehta <neil@lmstudio.ai>
Co-authored-by: Neil Mehta <neil@lmstudio.ai>
No description provided.