[Feature Request] CLI Arguments to directly create a new custom chat on startup

[derDere]

Often there are processes or agents that are running in the background working with AI and at some point they run out of knowledge or find a problem that first requires additional information from a real person. For example, if multiple solutions are possible and someone has to make a decision which to pick. If the running background software is a custom system, it often lags the infrastructure to then create a good solution on how to ask for those informations without for having to develop additional UIs, and it would be very convenient to be able to then just pop up a new chat within one of the best AI chat clients there is.

So being able to start up 5ire with some custom CLI-arguments that allow you to create a custom chat on startup and jump into it directly would solve this problem and also open a lot more of opportunities to integrate 5ire into bigger systems.

A local running API that allows for some control in the background would also have been one Idea.

I have a current use case for this in our company and will probably come up with a solution for this on my own. But I think this feature would also allow many other uses. Such as integration into other systems like normal UI that just start into 5ire for different options, or the ability to pop right into an AI that helps you solve a bug via an MCP server as soon as you get the error notification. As I said, I think this feature would open the door for 5ire to not only be a stand-alone chat client but also become part of many other much bigger infrastructures.

[derDere]

As the demand for this feature is quite urgent for my company, I already came up with a solution for this and created a pull request: #392
As my experience with Node.js and open-source projects is basically none, I hope this is not too bad of a way to handle this.

[khawa-angx]

This is a fantastic and valuable proposal!

Your suggestion of launching a custom chat via CLI parameters is an excellent solution for integrating 5ire into other complex systems. This will indeed save the trouble of developing extra interfaces.

I am very grateful for your time and for submitting pull request.

---

Concerns Regarding the CLI Launch Method

We believe that directly running an executable to achieve this goal might not be the best choice, mainly due to concerns regarding usability and dependencies:

• If the executable is not registered in the PATH environment variable, you would need to input the full path to the executable when calling it, which makes integration into scripts or backend services very cumbersome and inflexible.

• Adding it to the PATH might raise concerns regarding environment management and security policies in large or controlled enterprise environments.

• Directly calling the executable from a backend script might result in unnecessary console windows or orphaned processes in the terminal or service.

Alternative Solution

We believe that Deep Linking is a more elegant solution and better aligns with application integration best practices.

• The 5ire client can be triggered via a unified URI format, regardless of the environment the backend system is running in.

• The 5ire protocol is already successfully registered in the application and is used for features like login callbacks and tool installation, and this capability is currently stable.

• This approach focuses on triggering the main application and will not generate extra console windows or orphaned processes in the backend service.

---

We would like to request if you would be willing to pivot your existing work towards using Deep Linking to implement this feature and resubmit a PR; that would be extremely helpful! If you are unable to, we will reference your PR's logic and proceed with the development ourselves to ensure the best integration practices.

Thank you again for your contribution!

[derDere]

Oh, well thanks for the feedback! I'll have a look at it and see how fast I can port over to this method.