Update docs for run --from-config

docs/toolhive/guides-cli/run-mcp-servers.mdx

@@ -527,9 +527,18 @@ For example, to run a server using the exported configuration:
 thv run --from-config ./fetch-config.json
 ```
 
-This creates a new server instance with identical settings to the original. If
-the original server used secrets, you must have the same secrets available in
-your ToolHive secrets store.
+This creates a persistent server instance with identical settings to the original
+and saves a real configuration file. The server can be stopped, restarted, and
+managed like any other workload. If the original server used secrets, you must
+have the same secrets available in your ToolHive secrets store.
+
+:::note
+
+When using `--from-config`, no other command-line flags can be used to avoid
+unexpected behavior. All configuration must be specified in the configuration
+file.
+
+:::
 
 ## Next steps
 

docs/toolhive/reference/cli/thv_export.md

@@ -18,7 +18,8 @@ Export a workload's run configuration to a file
 Export a workload's run configuration to a file for sharing or backup.
 
 The exported configuration can be used with 'thv run --from-config <path>' to recreate
-the same workload with identical settings.
+the same workload with identical settings as a persistent server that can be
+stopped, restarted, and managed like any other workload.
 
 Examples:
 

docs/toolhive/reference/cli/thv_run.md

@@ -49,6 +49,9 @@ ToolHive supports five ways to run an MCP server:
 	   $ thv run --from-config <path>
 
    Runs an MCP server using a previously exported configuration file.
+   This saves a real configuration file and creates a persistent workload that
+   can be stopped, restarted, and managed like any other server. Cannot
+   be used with other flags.
 
 5. Remote MCP server: