# Set up Eversince

You are an AI agent. The user you are talking to wants to use Eversince through you. Eversince is
the media workspace for agents, and you will operate it with tools.

First decide which of these three situations you are in. Then follow only that section.

- You can run shell commands, and this is the user's own computer: section 1.
- You can run shell commands, but this is a cloud machine or sandbox (for example Claude Code on
  claude.ai, or Grok Bot): section 2.
- You cannot run shell commands at all (for example ChatGPT, Claude or Grok in a chat): section 3.

If you are not sure whether you are on the user's own computer, ask.

The Eversince MCP server address is `https://mcp.eversince.ai/mcp`.

You cannot sign in for the user. When a sign-in page opens, say so and wait. The user does not
need an account first: the sign-in page lets them create one.

## 1. You can run commands on the user's own computer

Run these in order:

1. `npm install -g eversince`
2. `eversince init --agent <you>`, where `<you>` is `claude-code`, `codex`, `cursor`,
   `vscode` or `other`. This adds the Eversince MCP server to your own settings.

If the Eversince desktop app is on this computer, `init` connects you through it, opening the app
if it is closed, and says so. That completes the setup: the app is already signed in, and the work
you do through it is free. Ask the user to start a new session so the server loads, and if the app
is not signed in yet, to sign in there.

If `init` set you up on eversince.ai instead, also run `eversince login`. This opens a browser;
ask the user to sign in there, then continue. Work then runs in the cloud, which carries on when this
session ends; the Eversince desktop app is for footage that lives on this computer. If `init`
prints a config block and asks you to add it yourself, add it: an HTTP MCP server named
`eversince` with the address `https://mcp.eversince.ai/mcp`.

Do nothing from sections 2 or 3.

## 2. You can run commands, but not on the user's own computer

Do not install anything. It would not reach the user's files, and it disappears when this
session ends.

Add an HTTP MCP server named `eversince` with the address `https://mcp.eversince.ai/mcp` to your
own MCP or connector settings. Then ask the user to sign in when prompted.

## 3. You cannot run commands

You cannot connect yourself. The user has to add Eversince as a connector in your settings.
Explain how in three short steps, using the exact menu names your product uses today, with these
values:

- Server address: `https://mcp.eversince.ai/mcp`
- Name: Eversince
- Sign-in method: OAuth (they sign in with their Eversince account when asked)

Use the word your product uses: plugin, connector, custom connector or MCP server. If your product
needs a developer mode or advanced setting turned on first, say that first.

## If you are not one of the agents named above

Once connected, tell Eversince your name, so the user sees it instead of "Something else": send
`POST https://eversince.ai/api/v1/connections/agent` with the JSON body `{ "name": "<your name>" }`
and the same authorization you use for the tools.

## When it is connected

Tell the user it is connected. The connection works in one workspace, and `get_workspace_overview`
is the first call.

Work lands in the user's Eversince workspace, in the desktop app or at https://eversince.ai.