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.
  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 sets the agent up on the cloud, and eversince login signs in through the browser. The user signs in there, or creates an account on the same page, and picks a workspace. 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. Claude Desktop connects through a bundle the desktop app installs from Settings, Agents. Work through a hosted connection runs in the cloud on the user’s balances.

​
From the app

Settings, Agents lists the agents on the computer and connects each with one click, and gives the steps for a chat product. An account can have several agents connected at once. Each connection is scoped to one workspace when it is made.

​
After connecting

The agent receives the server’s instructions, the operating manual described on MCP server, and the tool list. Its first call is get_workspace_overview. Nothing is declared or remembered between calls; every call carries what it needs.