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.
- Set
EVERME_API_BASE=https://my-self-hosted-everos-host
- Ran
evercli auth login
Result: login fails / does not talk to my self-hosted endpoint as documented.
- 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.
What I did
Followed the README:
EVERME_API_BASE=https://my-self-hosted-everos-hostevercli auth loginResult: login fails / does not talk to my self-hosted endpoint as documented.
auth loginentirely and manually configured the Claude Code plugin (writing the env values myself instead of going throughevercli 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_BASEand runningauth loginshould 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.