We’re building Ever Works in public. Some things may be incomplete, missing, or broken while we continue improving the platform.We’re building Ever Works in public — expect a few rough edges.
Developers · Terminal
The CLI installs a single binary, ever-works, and talks to exactly the same REST API as the dashboard, signed in as you. Four command groups — auth, work, plugins and kb — take you from an empty terminal to a deployed site, and the non-interactive subset drops straight into CI. Version 0.1.5, MIT-licensed, Node 20 or newer.
Run ever-works --help and you see four groups — these, and nothing else. Every group and subcommand below is in the published binary today.
ever-works auth login opens a browser tab and completes OAuth against a loopback callback, then writes ~/.ever-works/.credentials.json with mode 0600 inside a 0700 directory. Add --manual to skip the browser and be prompted for a pasted token instead, --api-url to point at your own API, and check the session any time with auth status; auth logout removes the file.
Thirteen subcommands: create, list, generate, status, update, update-website, deploy, submit-item, remove-item, regenerate-markdown, plugins, delete — plus register, which turns a repo carrying .works/works.yml into a queued Work. Most prompt you with a searchable list instead of taking flags, which makes them excellent in a session and unsuitable for cron.
ever-works plugins opens a searchable browser of every plugin on your account — enable, disable and fill in settings, with secret fields prompted as hidden input and required fields collected before a plugin will enable. In dynamic distribution mode, catalog, install, uninstall and install-status manage plugins pulled from npm or GitHub Packages, with an optional --version pin and --integrity checksum.
kb get, kb lock and kb unlock address a document by UUID or by path, so runbooks/deploy.md works as an argument, while kb list enumerates a Work's documents behind --class, --tag and --q filters and kb upload creates one from a local file. This is the one group that takes arguments and flags rather than prompts throughout — seed a brand voice with kb upload, then kb lock --mode full so no agent run can quietly rewrite it.
npm install -g ever-works-cli, then ever-works --version to confirm 0.1.5. Node 20 or newer is required. Prefer not to install anything? npx ever-works-cli work list runs the same binary on demand.
ever-works auth login --api-url https://api.ever.works opens a browser tab and closes it a few seconds after the callback lands. Pass the origin only — the HTTP client appends /api itself. Then ever-works auth status prints your identity, the API URL and the remaining token lifetime, and verifies the token against the API before it says yes.
Connect a git provider at /settings/plugins/git-provider and an AI provider at /settings/plugins/ai-provider first — work create stops with a clear message when no git provider is configured. Then ever-works work create walks through name, slug and repository, ever-works work generate starts the content pipeline, and ever-works work status polls it.
ever-works work deploy publishes the site to your configured target. Already have a repository with .works/works.yml at its root? ever-works work register --repo https://github.com/acme/awesome-observability creates the account if it does not exist yet and queues the Work in one fully non-interactive call.
The CLI is a client, not a second platform: every command is the same REST call the dashboard and the MCP server make, so anything the command tree has not grown yet is still reachable over the API. What matters for automation is which commands prompt and which do not.
The command tree is auth, work, plugins, kb — and nothing else. Every gap below has a supported route today; it simply is not a CLI command yet.
Everything the dashboard does is an authenticated REST call — documented with OpenAPI, callable with an API key, and observable through signed webhooks.
Learn more →Manage Works from any MCP-compatible assistant — 127 API tools plus Knowledge Base tools, authenticated with an API key, over stdio or HTTP.
Learn more →Bring a data repository, an awesome-list README, or repositories you already run under management — with config-as-code and a GitHub App.
Learn more →A plugin is a capability the platform does not have on its own — a model, a search engine, a Git host, a deploy target — and Ever Works ships 102 of them.
Learn more →Run Ever Works in the cloud, self-host the platform with Docker Compose or Kubernetes manifests, and deploy your Works to Ever Works hosting, Vercel, or your own cluster.
Learn more →Describe what you want to build. Ever Works researches it, ships it, and keeps it improving — content and code, owned in your own Git.