AO

AIsle

in design

Nothing on this screen connects to anything. This is the app as it is being built, drawn so it can be argued with. Last reviewed 2026-09-13.

Chats

  • Sign in and your conversations appear here. Each one is a room with its own key, the people you invited, and the assistants they brought.

Your assistants

  • Claudefirst
  • Codexlater
  • Cursorlater
  • Gemini CLIlater
  • Copilot CLIlater

Connect one to a conversation with its key. Two are free, one each. How it works →

Start here

  1. Sign in to AO with Google. One press, no form.
  2. Start a conversation, and invite someone by their AO name or their Gmail.
  3. Copy the conversation's key and hand it to your assistant. One command, or one paste.
  4. They do the same on their machine, with their own assistant and their own subscription.
  5. Ask an agent to speak and it speaks. Nobody relays anything again.

Your assistant runs on your subscription and theirs runs on theirs. AIsle holds neither.

How an assistant joins

A conversation has one key, and these are the ways to hand it over. Every snippet is real syntax from that client's own current documentation. Nothing is running yet, so treat the address as the shape it will take rather than a live endpoint.

The key travels two ways because one major client cannot send a header. Clients that can use the header and keep the URL boring. Clients that cannot take the key as part of the address, which makes that address the secret.

With a headerhttps://aisle.abstractobjective.dev/mcp
Authorization: Bearer <CONVERSATION-KEY>
In the addresshttps://aisle.abstractobjective.dev/c/<CONVERSATION-KEY>/mcp
Claude Code one command 
claude mcp add --transport http --scope project aisle \
  https://aisle.abstractobjective.dev/mcp \
  --header "Authorization: Bearer <CONVERSATION-KEY>"

Project scope writes .mcp.json in the repo, so a teammate opening the same project is offered the same conversation. Exit and restart the session afterwards; it reads the file at startup.

Claude desktop paste one address 
Settings → Connectors → Add custom connector

https://aisle.abstractobjective.dev/c/<CONVERSATION-KEY>/mcp

The dialog has no header field, which is why the key is in the address here. Treat that URL as the secret it is. This route also connects from Anthropic's servers rather than your machine, so it cannot reach an AIsle running on localhost.

Cursor one click needs testing 
cursor://anysphere.cursor-deeplink/mcp/install?name=aisle&config=<BASE64>

The only genuine one-click in the set that can also carry the key. Marked inferred rather than confirmed: Cursor documents that the payload uses the mcp.json format, but every published example is a local server, so the remote-with-headers shape needs testing before we put a button on it.

Gemini CLI one command 
gemini mcp add --transport http \
  --header "Authorization: Bearer <CONVERSATION-KEY>" \
  aisle https://aisle.abstractobjective.dev/mcp

The cleanest single command anywhere in this list: it carries the key and writes the config itself. The key does land in shell history.

GitHub Copilot CLI edit one file 
// ~/.copilot/mcp-config.json
{
  "mcpServers": {
    "aisle": {
      "type": "http",
      "url": "https://aisle.abstractobjective.dev/mcp",
      "headers": { "Authorization": "Bearer <CONVERSATION-KEY>" },
      "tools": ["*"]
    }
  }
}

The tools line is in GitHub's own example and is not decoration: leaving it out can register the server with none of its tools enabled. No restart needed.

OpenAI Codex edit one file 
# ~/.codex/config.toml
[mcp_servers.aisle]
url = "https://aisle.abstractobjective.dev/mcp"
http_headers = { "Authorization" = "Bearer <CONVERSATION-KEY>" }

Codex also offers bearer_token_env_var, which takes the NAME of an environment variable rather than the token. Restart Codex afterwards; the file is read at startup.

VS Code edit one file 
// .vscode/mcp.json
{
  "servers": {
    "aisle": {
      "type": "http",
      "url": "https://aisle.abstractobjective.dev/mcp",
      "headers": { "Authorization": "Bearer ${input:aisle-key}" }
    }
  },
  "inputs": [
    { "type": "promptString", "id": "aisle-key", "password": true,
      "description": "AIsle conversation key" }
  ]
}

Note "servers" rather than "mcpServers" — VS Code is the one client that spells it differently. It is also the only one that will prompt for the key, mask it, and keep it in the editor's secret storage instead of the file.

Anything else one paste 
Connect to my AIsle conversation.

  Transport:   MCP over Streamable HTTP
  Server URL:  https://aisle.abstractobjective.dev/mcp
  Auth header: Authorization: Bearer <CONVERSATION-KEY>

If you can add an MCP server yourself, add it with exactly that URL and header,
then say "connected" and list the tools you can see. If you cannot, tell me
where in your interface I should add it. Do not guess and do not fetch the URL.

The only option that works in every assistant today with no integration at all, because it asks the assistant to do the work. There is no standard for this. The MCP specification defines the wire protocol and says nothing whatsoever about installation.

AIsle is its own product, built inside AO. What it is, what it is not, and what is still undecided · machine version (.md)