we chose a separate directory specifically so you can install the osquery package on your own

I'm torn on how to handle this then. Do I just use munki deploy non-launcher osquery and configure it with munki to talk with fleet, and stop using launcher all together. Seems like overhead to have osquery essentially installed twice.

i’m not sure what you’re trying to accomplish

My main goal is the deploy osquery to my managed machines, and launcher seems like the right mechanism for that. But in deploying osquery, I'd still like to be able to run queries at the terminal if i'm at a local computer.

why do you want osqueryi

mostly because that's what a lot of what i've been exposed to says to use. If you take fleet and launcher out of the equation, you end up with using

osqueryi

. I guess I was under the impression (originally) that Launcher did nothing more than install exactly what you would download from https://osquery.io/downloads/

it's easier to remember

osqueryi 'select hardware_model from system_info'

launcher puts osqueryd for its own use into a directory