Setup Stash can send a selected setup version back to your PC so it appears in your LMU Settings folder.
This is handled by MyLMU Sync Agent.
What “Send to my LMU folder” means
When you choose Send to my LMU folder, MyLMU:
- takes the selected or latest stash version
- queues it for delivery
- asks Sync Agent to write it into the matching LMU Settings-relative location
The write does not happen inside the browser. The desktop Sync Agent completes the last step.
Requirements
| Requirement | Detail |
|---|---|
| Sync Agent connected | The desktop app must be signed in to your MyLMU account |
| Setup folder configured | The agent needs access to your LMU setup folder |
| Pro access | Setup Stash and setup sync require Pro |
Path and layout expectations
Each version is tied to an LMU Settings-relative path such as a track/layout folder plus file name.
This matters because Sync Agent needs to know where to write the file back on disk.
If the inferred layout is wrong, fix it in Setup Stash before relying on send-back behavior.
Delivery status
Setup cards can show delivery state so you know whether the agent has seen the work yet.
Typical lifecycle:
| Status | Meaning |
|---|---|
| Pending | MyLMU queued the setup for Sync Agent |
| Written / delivered | The file was written successfully on the desktop side |
| Failed | The agent could not complete the write |
If a delivery fails, retrying usually creates a new delivery attempt after you fix the underlying issue.
Common reasons a send can fail
- Sync Agent is offline or disconnected
- the setups folder was never configured
- the target relative path is invalid
- the agent cannot write to the chosen folder
- the selected version metadata points at the wrong layout/path
See Troubleshooting for practical fixes.
How to verify it worked
- Watch the delivery status in Setup Stash
- Open LMU’s setup folder on your PC if needed
- Load the setup in the matching car and track context in-game
Best practice
- Keep Sync Agent connected when testing send-back flows
- Double-check track/layout naming before sending
- Use version notes so you know exactly what you are sending back