Skip to content

Following the self-host EverOS instructions (EVERME_API_BASE) does not work — auth login fails, and manually configuring the plugin also has no effect #3

Description

@hanai

What I did

Followed the README:

Self-hosting EverOS? Set EVERME_API_BASE=https://your-host before auth login and the CLI will talk to your endpoint instead.

  1. Set EVERME_API_BASE=https://my-self-hosted-everos-host
  2. Ran evercli auth login

Result: login fails / does not talk to my self-hosted endpoint as documented.

  1. As an alternative, I skipped auth login entirely and manually configured the Claude Code plugin (writing the env values myself instead of going through evercli plugin install).

Result: it doesn't take effect either — the plugin doesn't work against my self-hosted EverOS instance.

Expected: per the README, setting EVERME_API_BASE and running auth login should let the CLI talk to a self-hosted EverOS instance instead of the managed service, and/or manually configuring the plugin against that instance should work.

Actual: neither path works.

Happy to provide more logs/detail if needed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    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