# Client automation
**URL:** https://mworks.discourse.group/t/client-automation/604
**Category:** Support
**Created:** [October 23, 2012, 1:48pm UTC](https://mworks.discourse.group/t/client-automation/604 "2012-10-23T13:48:01Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@cstawarz](https://mworks.discourse.group/u/cstawarz)
#### Post date: [October 23, 2012, 1:48pm UTC](https://mworks.discourse.group/t/client-automation/604/1 "2012-10-23T13:48:01Z")
Hi Chris,
I now have glue code that reads and writes the MWClient matlab window defaults every time I start the client - a few times a day on each machine.
We’ve talked about different sorts of automation before.
How about command line options for (1) the server to connect to (IP address?) (2) the experiment to load on startup and maybe (3) the python client bridge script to load on startup?
Then, my script can be a one shot deal:
kill all rogue python scripts, old instances of client/server
load relevant client defaults
start client and server
And then all the user needs to do is load the experiment variables and go.
I’m open to discussion of other alternatives. No rush on this.
Thanks, Mark
---
### Author:  [@cstawarz](https://mworks.discourse.group/u/cstawarz)
#### Post date: [November 20, 2013, 3:23pm UTC](https://mworks.discourse.group/t/client-automation/604/2 "2013-11-20T15:23:02Z")
Mark and I have followed up on these ideas in [another discussion](https://mworks.discourse.group/discussions/suggestions/73), so I’m closing this one.
---
### Author:  [@cstawarz](https://mworks.discourse.group/u/cstawarz)
#### Post date: [July 19, 2022, 11:21pm UTC](https://mworks.discourse.group/t/client-automation/604/3 "2022-07-19T23:21:16Z")