Skip to main content
An agent connects itself when it can run commands. When it cannot, the user connects it from the agent’s own settings. The page an agent reads to do this is eversince.ai/skill.md, and the setup prompt in the app’s Settings is one sentence pointing there. The same steps follow, 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 writes the server into the agent’s own settings, or prints it where it cannot.
  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, opening it 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 Claude Desktop connects through. Without the app, init writes the hosted server into Claude Code’s, Cursor’s or VS Code’s settings and prints the entry for any other agent. The agent opens its own browser sign-in the first time it connects, where the user signs in or creates an account and picks a workspace. eversince login is a separate sign-in, needed only to run tools from the shell; set as ES_API_KEY, an API key signs in the CLI instead. Work then runs in the cloud on the user’s balances. The desktop app is at eversince.ai, for Mac and Windows.

​
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. Nothing is installed, because it would not reach the user’s files and would not outlive the session. The agent adds an HTTP MCP server named eversince at https://mcp.eversince.ai/mcp to its own settings, and the user signs in when asked.

​
3. The agent runs no commands

A chat product, such as ChatGPT, Claude, Muse or Grok Bot in a chat. The user adds Eversince as a connector in the product’s own settings, with the server address above and OAuth as the sign-in method, and signs in or creates an account when asked. Products name this differently: connector, custom connector, plugin or MCP server. With the Eversince desktop app on the same computer, eversince init --agent claude-desktop installs the bundle Claude Desktop connects through. Work through a hosted connection runs in the cloud on the user’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 connects by a link the user opens, and receives 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 gives the user link. The user 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 answers 202: ask again every interval seconds. 403 means the user refused, 409 that the account already has 10 keys, 410 that the link expired or was already used. The link is open for 15 minutes; once allowed, the key can be collected for 30. The key is sent as Authorization: Bearer es_live_… to the MCP server or to the REST API.

​
From the app

Settings, Agents lists the connected agents, gives the one-line setup prompt 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 picked when it is made and may switch to any other the user ticked, there or later in Settings, Agents; a connection through the desktop app works in the workspace the app has open. An API key is made only for workspaces the user owns, so a member of someone else’s workspace connects with OAuth.

​
After connecting

The agent receives 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. Its first call is get_workspace_overview. Nothing is declared or remembered between calls; every call carries what it needs.