Repository navigation
Drop support for hosted API transports? #2903
olliewalsh
started this conversation in
General
Replies: 3 comments 1 reply
|
@XiaoHuo888-hue FYI. I'm not sure if it's worth adding support for OrcaRouter |
0 replies
|
I agree, the focus of ramalama is local inference and related workloads. There are other, more targeted options for providing a chat interface to hosted APIs. I think dropping support for hosted APIs makes sense. |
0 replies
|
I agree drop the hosted API transports. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
While reviewing #2901... I've given some though to the "hosted API transport" feature in general.
It was never really a good fit, essentially hacked into the
ramalama runcli, but it doesn't "run" anything, and doesn't work with most of theramalama runargs/options.It only provides a very basic chat client to these providers, which nowadays is of very limited value.
Now that we are supporting agentic clients with
ramalama sandbox, which do not work with the hosted API transports, I think we need to stop accepting any new hosted API transports and deprecate/drop the existing transports.@bmahabirbu @mikebonnet @rhatdan WDYT?
All reactions