[feature] remove dependency between cli query commands & server spawn

[ologbonowiwi]

describe the feature
currently screenpipe is one-fits-all thing. if you run screenpipe it'll run the API, and then execute any commands on CLI accessing the API exposed if needed.
it would be better if we follow the ollama approach where you need to ollama serve and then execute ollama run in another terminal.
currently if I want to check which are the available monitors for example, I need to stop screenpipe on the app, run the command on the terminal, and then rerun to keep recording.
do things like --list-monitors should not interfere with recording or with the server. I should be able to execute at least these query commands without needing to stop screenpipe.

why is this needed?
bc it's annoying stopping the app just to check available monitors or available audio devices

[louis030195]

it does not interfere

i agree with the first part

maybe we should have like screenpipe serve which runs the API etc without recording anything

and then screenpipe record --audio-device [...]

not super familiar how it'd be in terms of infra and how it'd play out with the UI

[ologbonowiwi]

I didn't knew we had things like audio/vision commands. I was trying --list-monitors only

maybe we should have like screenpipe serve which runs the API etc without recording anything

I like the idea, exactly what I had in mind

how it'd play out with the UI

I guess on start instead of executing the whole command we'd need just to execute screenpipe serve before.

Ideally this could be totally decoupled, but not sure how much work it'd be so for now we could just skip the running server for other commands if the server is already running, maybe that'd be enough and we leave the decoupling to later

[ologbonowiwi]

just updated. as for new release, I think we don't need this issue anymore. I could list the monitors without issue using it. thx