Skip to content

LMS CLI permission errors with local build #584

@sherrellbc

Description

@sherrellbc

I appear to be completely unable to use the CLI if built locally. I ran into the same AVX-512 issue mentioned here, so I decided to build the tools myself. That appears to work, but now when I try to use the lms CLI for anything I am met only with permission errors of all sorts.

The daemon up command appears to work

$ lms daemon up
W You are using a development build of lms-cli. Privileged features such as "lms push" will not work.
Waking up LM Studio service...
llmster started (PID: 11838).

But I can't daemon down

$ lms daemon down
W You are using a development build of lms-cli. Privileged features such as "lms push" will not work.
Shutting down llmster...
Error: Permission denied. The client "lms-cli-dev" does not have the required permission: [{"type":"system.manage"}]

Nor can I get models

$ lms get
W You are using a development build of lms-cli. Privileged features such as "lms push" will not work.
Error: Permission denied. The client "lms-cli-dev" does not have the required permission: [{"type":"hub.readStaffPicks"}].

Or any other command, really. I can't find anything in the documentation about this.

Can someone provide some guidance on what to do?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions