The Rust auto-run command is bind KEY forward;sprint. Open F1 and replace KEY with a free key, for example x. Press Enter to assign it. After closing F1, tap your chosen key to start running; press your normal forward key when you want control back. On the default layout, that is W.
There is a reason for leaving the plus signs out. Forward and sprint keep going after the shortcut is released, which makes this version suitable for crossing a long stretch without holding W. Adding plus signs turns it into the held-input version explained below.
bind x forward;sprintx is just the example. You could use c, v or a recognized side button such as mouse4. Pick one that is free. Only that key name changes in the command; the action names and the semicolon stay as shown.
An auto-run key should fit around your other Rust keybinds. Leave combat and inventory controls on familiar keys so you can take manual control quickly.
Set Up the Rust Auto Run Bind
- Find harmless ground before trying it. Face away from water, roads, drops, traps and other players so an unexpected run does not cost your kit.
- Open the developer console with
F1. This is where Rust accepts the bind, not the chat box. - Enter
bind x forward;sprintexactly as shown. Change onlyxwhen selecting a different activation key. - Press Enter, close the console with
F1, and tap the selected key once. Do not hold it down for the continuous version. - Release the shortcut and check that the sprint continues. Then use your normal forward key to take over. Learn that override before relying on the bind during a journey.
Safe test warning: For the first attempt, face a wall or choose a patch of level ground with nothing dangerous ahead. Once F1 is closed, the assigned key has a real movement action. Keep the ordinary forward key ready to override it; opening a menu is not a dependable stop.
How to Stop Auto Run
Press W to take over, assuming W still means forward in your controls. There is no separate off key in this command. That is worth remembering before you start a long run: the way back to manual movement is an ordinary forward input.
On a custom layout, follow the forward action to its new key. That might be a different letter or even a mouse button. Pressing W will not provide the intended override if W no longer has forward movement assigned to it.
Assigning nothing to a second key does not cancel the run. It only changes what that second key will do when pressed. For movement already in progress, use your forward input first. You can edit assignments in the console after taking control back.
Continuous Auto Run vs Hold-to-Run Bind
A plus-sign bind stays active only for the time the key is held. Releasing your finger ends those actions. It is a convenient way to put forward and sprint together, but somebody wanting hands-free travel needs the continuous version instead.
| Bind Type | Command | Activation | Stop Behavior | Best Use |
|---|---|---|---|---|
| Continuous Auto Run | bind x forward;sprint | Tap once | Press the normal forward key | Long distance travel without holding keys |
| Hold to Run | bind x +forward;+sprint | Hold key | Release the key | Short bursts where timing matters |
Both shortcuts can coexist on different keys. Before using them near an entrance or cover, learn which needs a release and which needs the forward override. Mixing them up is easy when the visible result is a sprint in either case.
How to Change or Remove the Auto Run Bind
Replace x with a different Rust key name to move the shortcut. There is one catch: the old assignment stays. Binding Mouse4 does not clear X, so both will start auto run until you remove or replace the original X bind.
Deal with the active movement before editing the shortcut: use the forward key. Clearing a bind is about the next keypress, not a dependable cancellation of an action already running. Once manual movement is back, the console can be used to remove the assignment.
Use either of these console commands to clear X:
bind x ""bind x clearRemoving auto run leaves X without its old job. If that key previously opened something or triggered another action, assign it again in Rust’s Controls menu or enter its original bind command. Clearing the new shortcut does not undo the earlier replacement.
Check the key’s old job first, whether that is voice chat, crouch, inventory, a weapon slot or a mouse feature. A spare side button can be useful, but Rust needs its input name, for example mouse4. After rebinding, check auto run and reassign any control you displaced before returning to a normal session.
| Purpose | Command | Result |
|---|---|---|
| Assign continuous auto run | bind x forward;sprint | One tap starts persistent sprint |
| Assign hold to run | bind x +forward;+sprint | Runs only while held |
| Clear key with empty bind | bind x "" | Removes assignment |
| Clear key with clear action | bind x clear | Removes assignment |
| Save bindings | writecfg | Writes config to file |
How to Save Rust Keybinds with writecfg
After creating, changing, or clearing a bind, run the following command in the F1 console to make it persistent:
writecfgThe saved bindings are local files, usually at steamapps\common\Rust\cfg\keys.cfg. Find the Steam library containing Rust rather than assuming it is on the system drive. The file opens in a text editor, but there is often no need to edit it there: Rust console commands entered through F1 can be saved by the game itself.
A copied keys.cfg file gives you a way back if a manual edit goes wrong. A server force wipe does not erase this local layout. Removing the config folder, reinstalling, or replacing it with someone else’s file is what can take the saved binds away.
Related Rust Toggle Binds
Other Rust keybinds can reduce repeated inputs during harvesting and travel. Add only the ones you need, choose keys that do not replace important controls, then run writecfg.
Auto-Swim Bind
bind 0 forward;sprint;jumpWhile swimming, tap 0 for the forward, sprint and jump actions together. The jump input takes you upwards towards the surface. Get back to manual movement before you reach a boat, rocks or another player; this is a movement shortcut, not a way to steer around obstacles.
Auto-Crouch Harvest Bind
bind z attack;duckOne tap starts attack and crouch together. Want to release Z and have both actions end? Use bind z +attack;+duck. In either case, Z loses whatever action was assigned to it before, so choose the key carefully and try it somewhere safe.
Left-Handed Viewmodel
graphics.vm_horizontal_flip "true"Your first-person weapon view flips horizontally with this setting. true enables the flip; use false to put the view back.
Expanded Look-at Radius for Pickup
client.lookatradius "20"The pickup check covers a wider look-at area with this setting. That can become awkward when several items are close together: the larger area may include an item you were not trying to select. Avoid increasing it further just because a bigger value is accepted.
Fixes When the Rust Auto Run Bind Does Not Work
| Problem | Cause | Fix |
|---|---|---|
| Only works while held | Plus signs used | Use forward;sprint version |
| The command is not working like it should. | Smart quotes pasted | Retype quotes manually |
| No sprint effect | Missing semicolon | Insert ; between commands |
| The key does nothing when pressed | Invalid key name | Use the correct name like mouse4 instead |
| Another action is lost | Key already occupied | Rebind original action in Controls |
| Nothing happens after entering the command | Command not submitted | Press Enter in console |
| Movement stops instantly | Forward key being pressed | Release forward key before testing |
| Bind disappears later | writecfg not used | Run writecfg after setup |
| Config resets unexpectedly | File overwritten | Restore backup of keys.cfg |
Continuous movement can ease long rotations between Rust monuments, but take manual control around cover, entrances and other players. Your Rust PvP control setup should leave movement, aiming and recovery inputs easy to reach.
Does Auto Run Work on Rust Console Edition?
These are PC instructions. Rust Console Edition does not expose the player’s F1 developer console, so you cannot enter bind x forward;sprint, bind x clear or writecfg there. On PlayStation or Xbox, work with the controller and accessibility options in the menus. Similar movement controls do not mean the PC console commands are available.
Use Auto Run Safely
Safety note: Keep watching the journey. This bind has no idea where the next cliff, animal or ambush is, and your character still needs food, water and protection from cold. Opening the map does not pause a multiplayer server. Take over with the forward key before studying a menu, and stay at the keyboard for the entire run.
Frequently Asked Questions
Is the auto run bind for Rust canceled every time by pressing W?
W overrides continuous movement when W is still your normal forward key. If you reassigned forward movement, press the key carrying that action instead. Use that forward bind before opening the console to change or clear an active auto-run key.
Is it possible to assign auto run to mouse button in Rust?
Yes, if Rust recognizes its input name. For example, mouse4 can take the place of X. A button already used for another action will lose that assignment, so decide where the old action should go before replacing it. Finish with writecfg once the new layout works.
Why did my Rust keybind disappear after I reinstalled the game?
A fresh installation can create fresh configuration files. If the old Rust folder was removed, the previous bind may have been removed with it. A backup of keys.cfg is the easiest recovery; without one, enter the bind again and save it using writecfg. Check the key in game before assuming the old layout survived.
Can I toggle on and off the auto run feature with the same key?
Not with this command. It starts a continuous run, but a second tap is not a dependable off switch. Press your normal forward key to take over. An external macro that imitates an on/off toggle is a different tool, outside this built-in setup, and may break the server’s rules.
Is auto run enabled if you have a map or inventory open?
The map and inventory are not reliable stop controls. Their behavior can depend on the menu and current inputs, and the multiplayer world keeps running behind them. For anything more than a glance, take manual control first. Any experiment with menu behavior should happen on safe, flat ground.
Could an auto run bind get you banned in Rust?
These commands use the game’s own bind system, without third-party software. That does not override a server owner’s rules. Read those rules, and do not extend the setup with macro loops, automation tools or scripts that repeatedly simulate inputs.
Where is the Rust keys.cfg file stored?
The usual location is steamapps\common\Rust\cfg\keys.cfg, inside whichever Steam library holds the game. A second library on another drive has its own copy of that path. For a simple bind change, F1 followed by writecfg avoids manual file formatting. Back up the file if you do decide to edit it.
