# Connect me to Kythene

You are an AI coding agent. Complete all of the following steps yourself by
running the commands directly. Do NOT ask the user to run any of these commands
or edit any files by hand - do it for them, then report back.

Kythene is your team's shared memory and output layer: once connected you can
`recall` what the team and their AI instances already know, and `publish` your
own work so theirs can see it. The connection is this instance:

- MCP endpoint: https://kythene.com/mcp/kythene
- Instance:     https://kythene.com

## Step 1 - detect your environment and connect

Work out which agent you are and follow the matching path. Sign-in is interactive
(OAuth in the client) - you never handle a password or token.

### If you are Claude Code
Run these, in order:
1. Download the plugin bundle: `curl -fsSL https://kythene.com/kythene-plugin.zip -o kythene-plugin.zip && unzip -o kythene-plugin.zip`
2. `/plugin marketplace add ./kythene`
3. `/plugin install kythene@kythene`
4. Tell the user to run `/reload-plugins` (plugins load once per session).
This installs the Kythene MCP server (connects on first use via OAuth) and the
kythene-workflow skill.

### If you are Cursor, Windsurf, Codex, GitHub Copilot, OpenCode, or any MCP client
Add Kythene as a streamable-HTTP MCP server in this client's MCP config
(e.g. Cursor's `.cursor/mcp.json`, Windsurf's `mcp_config.json`, Codex/Copilot's
MCP settings). Add this server entry:

    {
      "mcpServers": {
        "kythene": { "url": "https://kythene.com/mcp/kythene" }
      }
    }

Then trigger the connection so the client runs its OAuth sign-in flow against
https://kythene.com/mcp/kythene. The endpoint registers your client automatically (Dynamic Client
Registration); the user just approves sign-in in the browser the client opens.

### Optional - the kythe CLI (for scripts / non-agent use)
Install the latest `kythe` binary from https://github.com/kythene/cli/releases,
then set `KYTHENE_URL=https://kythene.com` and mint an API key from https://kythene.com/ (Connect AI ->
API keys). Not needed if you connected over MCP above.

## Step 2 - confirm it worked, then run the first-session loop
Make one `recall` tool call (any query, e.g. recall the current project). If it
returns without an auth error, you are connected.

Now give the user the payoff, using THEIR real work - never invented samples:

- If recall + timeline are both EMPTY (a fresh workspace): briefly ask "what are
  you working on right now?" (one or two follow-ups at most), then `remember` 2-3
  REAL things from their answers - the project one-liner, a decision, a gotcha -
  and `publish` one small real artifact they already have. Then stage the payoff,
  verbatim: "Start a NEW session and ask me what I know about <project>. That's
  Kythene working."
- If recall already returns content: tell the user, in your own words, that
  you're connected and can now recall what the team knows and publish your work
  so their instances can see it - and carry on the task using that context.

If anything fails, point the user to the docs: https://kythene.com/docs