[Feature]: Add support for oh-my-pi

[kakde-sandeep]

Problem

Since omp is fork of pi, can you please check and add support for this as well.
Github: https://github.com/can1357/oh-my-pi

Proposed solution

Since omp is fork of pi, can you please check and add support for this as well.
Github: https://github.com/can1357/oh-my-pi

Area

models

Suggested priority

p1

Additional context

No response

[kakde-sandeep]

@acorvi Is this possible?

[acorvi]

@kakde-sandeep it should be possible but requires investigation and understanding on how oh my pi works. Did you try to use AI to figure it out? It might help if you flesh out the issue.

[kakde-sandeep]

I've done some initial testing on my end. I managed to replace the pi references with omp, and the core chat functionality is working perfectly. However, it looks like some command-line arguments have been removed (e.g., --list-models), so the model listing feature is currently broken.

I haven't had the bandwidth to test everything thoroughly just yet, but I'll continue testing and update this thread with any other breaking changes I find. Let me know if you have any suggestions or workarounds for the missing CLI arguments!

[acorvi]

ideally it would be good to get them working side by side so users can choose to use Pi or OhMyPi. The change as you're building it is ok for personal use, but can't be shared with others in case somebody also wants to improve it or use it

[kakde-sandeep]

I completely agree having them work side by side is definitely the best approach for the community. I would love to implement it this way, but I could use some advice on how to structure the initial setup.

Just to be fully transparent, I don't have prior experience with Swift, so I'll be relying heavily on AI to help me with the actual coding. Because of that, could you point me in the right direction, or perhaps set up a basic skeleton for the integration? If you can help lay the architectural groundwork, I'd be more than happy to take it from there and build out the rest.