Skip to main content
An agent that can run commands can connect itself. One that can’t can be connected by the user from the agent’s own settings. The page an agent reads to do this is eversince.ai/get-started.md, and the setup line in the app’s Settings points there. The same steps are below, for a user or a developer doing it by hand.

Addresses and credentials

1. The agent runs commands on the user’s own computer

Claude Code, Codex, Cursor, VS Code and any other agent with a shell on that machine.
  1. npm install -g eversince
  2. eversince init --agent claude-code (or codex, cursor, vscode, claude-desktop, other). This adds the server to the agent’s own settings, or prints the entry when it can’t.
  3. Start a new session in the agent so it loads the server.
With the Eversince desktop app installed, init connects the agent through the app, and opens the app if it is closed. The app is already signed in, the connection works in the workspace the app has open, and work the computer can do is free. claude-desktop installs the bundle that Claude Desktop connects through. Without the app, init adds the hosted server to Claude Code’s, Cursor’s or VS Code’s settings and prints the entry for any other agent. The first time the agent connects, it opens a browser sign-in where the user can sign in or create an account and pick a workspace. eversince login is a separate sign-in, needed only to run tools from the shell; an API key set as ES_API_KEY signs in the CLI instead. Work then runs in the cloud and is charged to the account’s balances. The desktop app for Mac and Windows is at eversince.ai.

2. The agent runs commands, but not on the user’s computer

A cloud sandbox, such as Claude Code on claude.ai or Grok Bot with a sandbox. Installing the CLI there would not help: it could not reach the user’s files and would be gone when the session ends. The agent can add an HTTP MCP server named eversince at https://mcp.eversince.ai/mcp to its own settings, and the connection asks the user to sign in.

3. The agent runs no commands

A chat product, such as ChatGPT, Claude, Muse or Grok Bot in a chat. The user can add Eversince as a connector in the product’s own settings, with the server address above and OAuth as the sign-in method, then sign in or create an account when asked. Products call this different things: connector, custom connector, plugin or MCP server. With the Eversince desktop app on the same computer, eversince init --agent claude-desktop installs the bundle that Claude Desktop connects through. Work through a hosted connection runs in the cloud and is charged to the account’s balances.

4. The agent cannot add a server or complete a browser sign-in

An agent on its own machine or in a sandbox with no MCP settings. It can connect through a link the user opens, and gets an API key.
  1. POST https://eversince.ai/api/v1/connect with { "name": "<the agent's name>" }. The response carries link, device_code, expires_in and interval.
  2. The agent passes link to the user, who opens it, signs in or creates an account, and allows the agent in a workspace they own.
  3. POST https://eversince.ai/api/v1/connect/claim with { "device_code": "…" } returns, once, api_key, workspace_id, workspace_name, account_email, mcp_url and rest_base.
Until the user allows it, the claim returns 202 and can be repeated every interval seconds. 403 means the user declined, 409 that the account already has 10 keys, and 410 that the link expired or was already used. The link stays open for 15 minutes, and once allowed, the key can be collected for 30 minutes. The key goes in Authorization: Bearer es_live_… to the MCP server or the REST API.

From the app

Settings, Agents lists the connected agents, has the setup line to paste into an agent, and shows the address and commands for setting one up by hand. An account can have several agents connected at once. A hosted connection starts in the workspace chosen when it was made, and can switch to any other workspace the user has allowed, then or later in Settings, Agents. A connection through the desktop app works in the workspace the app has open. API keys can only be created for workspaces the user owns, so a member of someone else’s workspace can connect with OAuth.

After connecting

The agent gets the server’s instructions, the operating manual described on MCP server, and the tool list. Over REST, GET /api/v1/tools?instructions=cloud returns the same manual and tools. get_workspace_overview returns a summary of the workspace. No state is kept between calls, so each call includes everything it needs.