API Key, container access to "external" mtplx

[jbgreer]

FYI, I am successfully using your pi-mtplx package. Thanks!

In my scenario, I start mtplx using "mtplx quickstart" and provide a local IP. Since it's not localhost, mtplx requires that I also provide an API Key, which I do via a file. It's the default key, but, again, it must be explicitly provided.

Perhaps unlike you, I am running pi in a container. I have done this successfully in the past using pi + olmx.

Suffice it to say, I had an interesting debugging session, where I would start pi, it would recognize your extension, and under /mtplx even print the correct name of the model being served by mtplx, but also complain that no models were available and that I needed to provide an API Key even after setting it via /mtplx.

I ended up needing to edit not only .pi/agent/models.json, but also .pi/agent/auth.json to get my sessions to connect to my served model.

I wish pi allowed one to configure all settings via a local (i.e. project-level) .pi directory, but unfortunately in my experience these mappings are incomplete and not one-to-one.

Thanks again.

[KrossKinetic]

Hey! Glad to hear that you are finding the extension useful.

I’ll take a look at the issue this weekend and see what’s wrong. You are right I never ran Pi inside a container. I usually run it directly on my MacBook so I never ran into that issue, but I’ll test it and see what’s wrong. Thanks for reporting it!