Skip to main content
The package is eversince, published by the npm account eversince-ai. A package under any other name is not Eversince’s. The CLI is the REST API from a shell. Every command works for two kinds of caller: a user, and an agent running commands for them. --json gives machine-readable output on success and on failure.

Signing in and connecting

With the Eversince desktop app on the computer, commands go through the app and the work it does is free, and init connects agents through the app rather than the cloud. The app opens if it is closed. --cloud, --base-url, --workspace, ES_WORKSPACE, a workspace chosen with eversince workspace use, ES_API_KEY or ES_BASE_URL keep a command in the cloud, which needs eversince login. Through the desktop app, upload adds images, video and audio where they are on disk, and they are uploaded the first time a cloud feature needs them; --describe or --enrich uploads them right away, and documents are uploaded in any case. A folder is read one level deep. Without --idempotency-key, each run uses a new key, so running a charged command again charges again.

Working

Options

Environment variables: ES_API_KEY, ES_WORKSPACE, ES_BASE_URL, ES_DEBUG=1. Credentials are stored for each server address, in the system keychain where there is one. The CLI’s sign-in is separate from an agent’s connection: connecting or disconnecting an agent doesn’t affect it, and signing out doesn’t affect the agent. eversince tools starts with the operating instructions of whichever it is connected to, the app or the cloud, so a script reads the same rules an MCP agent does.