Headless Talk

How to use GitHub

• Please use the 👍 reaction to show that you are interested into the same feature.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

It would be nice to be able to have a headless system that I could use for automations to start calls, have messages read, and other things.
Just imagine being able to have an automation that you have on your computer, maybe with a script that whenever a certain message gets sent, it automatically does something on the computer, or maybe a keyword in the message or maybe you could tell your computer to start a call with your friend or something.

Describe the solution you'd like
A clear and concise description of what you want to happen.

It would be nice to use on headless systems talk and using links to both start a call, end a call, and other things. Maybe using command line arguments or something in this way.

Whichever you would think would be best to be honest. Just as long as it has external control where I can start calls and get messages and also maybe even see when messages are received.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Not being able to use Talk this way.

Additional context
Add any other context or screenshots about the feature request here.

I was just thinking this would be able to help in a lot of home automation use cases to be able to just use this as a communication option.
Just using my imagination, I can think of a lot of good use cases, or at least a good couple ones.
If you can imagine any use cases and can see any other scripting scenarios that would be possible, that would also be nice to add to this request, since that's what this request is about.

The issue names no file, test, or entry point. Start by mapping the desktop client's existing Electron and command-line surfaces, then clarify the external controls and supported call and message events; done should be defined as a reviewed, testable scope rather than a broad headless automation concept.