antenna-fyi 1.3.20 → 1.3.22

package/lib/cli.js

@@ -67,7 +67,7 @@ export async function handleScan(f) {
 export async function handleProfile(f) {
   const id = resolveId(f);
   if (!id) return console.error("Usage: antenna profile --id <platform>:<user_id> [--name Yi --emoji 🦦 --personal-description '...' --looking-for '...' --conversation-style '...'].']");
-  if (f.name || f["personal-description"] || f["looking-for"] || f["conversation-style"] || f.visible !== undefined || f.hide !== undefined) {
+  if (f.name || f["personal-description"] || f["looking-for"] || f["conversation-style"] || f["more-information"] || f.visible !== undefined || f.hide !== undefined) {
     const visible = f.hide ? false : (f.visible !== undefined ? f.visible === 'true' || f.visible === true : undefined);
     const payload = { device_id: id };
     if (f.name) payload.display_name = f.name;
@@ -75,6 +75,7 @@ export async function handleProfile(f) {
     if (f["personal-description"] !== undefined) payload.line1 = f["personal-description"];
     if (f["looking-for"] !== undefined) payload.line2 = f["looking-for"];
     if (f["conversation-style"] !== undefined) payload.line3 = f["conversation-style"];
+    if (f["more-information"] !== undefined) payload.matching_context = f["more-information"];
     if (visible !== undefined) payload.visible = visible;
     const data = await setProfile(payload);
     console.log("✅ Profile saved");

package/lib/core.js

@@ -109,6 +109,8 @@ export async function scan({ lat, lng, radius_m = 500, device_id, supabaseUrl, s
       personal_description: p.line1,
       looking_for: p.line2,
       conversation_style: p.line3,
+      more_information: p.matching_context || null,
+      profile_slug: p.profile_slug || null,
       distance_m: p.distance_m ?? p.dist_meters ?? null,
     };
   });
@@ -248,19 +250,24 @@ export async function setProfile({
 
   // Pack structured fields into matching_context JSON
   let contextJson = matching_context;
-  if (interest_tags || city || links || is_active !== undefined || archetype_override !== undefined) {
+  if (matching_context || interest_tags || city || links || is_active !== undefined || archetype_override !== undefined) {
+    // Read existing context from DB to merge
     let existing = {};
-    // If matching_context is already JSON, parse and merge
+    try {
+      const current = await getProfile({ device_id, supabaseUrl, supabaseKey });
+      if (current?.matching_context) {
+        try { existing = JSON.parse(current.matching_context); } catch { existing = {}; }
+      }
+    } catch {}
+
+    // If matching_context is a plain string (not JSON), treat it as the "context" field
     if (matching_context) {
-      try { existing = JSON.parse(matching_context); } catch { existing = { context: matching_context }; }
-    } else {
-      // Read existing matching_context from DB to merge
       try {
-        const current = await getProfile({ device_id, supabaseUrl, supabaseKey });
-        if (current?.matching_context) {
-          try { existing = JSON.parse(current.matching_context); } catch { existing = {}; }
-        }
-      } catch {}
+        const parsed = JSON.parse(matching_context);
+        Object.assign(existing, parsed);
+      } catch {
+        existing.context = matching_context;
+      }
     }
     if (interest_tags) existing.interestTags = interest_tags;
     if (city) existing.city = city;
@@ -331,6 +338,7 @@ export async function accept({
   device_id,
   target_device_id,
   ref,
+  profile_slug,
   contact_info,
   supabaseUrl,
   supabaseKey,
@@ -343,8 +351,16 @@ export async function accept({
     const { data } = await sb.rpc("resolve_ref", { p_owner: device_id, p_ref: ref });
     targetId = data;
   }
+  // Resolve profile_slug to device_id
+  if (!targetId && profile_slug) {
+    const { data: slugProfile } = await sb.rpc("get_profile_by_slug", { p_slug: profile_slug });
+    const resolved = Array.isArray(slugProfile) ? slugProfile[0] : slugProfile;
+    if (resolved?.device_id) {
+      targetId = resolved.device_id;
+    }
+  }
   if (!targetId) {
-    return { accepted: false, error: "No target. Ref may have expired — try scanning again." };
+    return { accepted: false, error: "No target. Provide ref, target_device_id, or profile_slug." };
   }
 
   const { error } = await sb.rpc("upsert_match", {
@@ -512,6 +528,8 @@ export async function discover({ device_id, supabaseUrl, supabaseKey }) {
       personal_description: p.line1,
       looking_for: p.line2,
       conversation_style: p.line3,
+      more_information: p.matching_context || null,
+      profile_slug: p.profile_slug || null,
       match_reason: reason,
     });
   }
@@ -703,6 +721,8 @@ export async function eventScan({ code, device_id, supabaseUrl, supabaseKey }) {
       personal_description: p.line1,
       looking_for: p.line2,
       conversation_style: p.line3,
+      more_information: p.matching_context || null,
+      profile_slug: p.profile_slug || null,
       checked_in: !!p.checked_in,
       role: p.role || "participant",
       status: p.status || "active",
@@ -821,3 +841,19 @@ export async function verifyApiKey({ key, supabaseUrl, supabaseKey }) {
   if (error) throw new Error(error.message);
   return data;
 }
+
+// ─── linkAccount (bind user_id to device_id) ─────────────────────────
+
+export async function linkAccount({ device_id, user_id, supabaseUrl, supabaseKey }) {
+  const sb = getClient(supabaseUrl, supabaseKey);
+  const { data, error } = await sb.rpc("bind_user_id", {
+    p_device_id: device_id,
+    p_user_id: user_id,
+  });
+  if (error) throw new Error(error.message);
+  if (data?.error) return data;
+  return {
+    ...data,
+    message: "账号已关联！现在你可以在 antenna.fyi/me 看到你的完整 profile 和匹配记录了。",
+  };
+}

package/lib/hermes-plugin/__init__.py

@@ -33,6 +33,7 @@ from .tools import (
     handle_event_reject,
     handle_event_add_host,
     handle_event_message,
+    handle_link_account,
     _sb,
     _device_id,
     _my_device_ids,
@@ -57,6 +58,7 @@ from .schemas import (
     EVENT_REJECT_SCHEMA,
     EVENT_ADD_HOST_SCHEMA,
     EVENT_MESSAGE_SCHEMA,
+    LINK_ACCOUNT_SCHEMA,
 )
 import re
 import time
@@ -92,6 +94,7 @@ def register(ctx):
     ctx.register_tool("antenna_event_reject", EVENT_REJECT_SCHEMA, handle_event_reject)
     ctx.register_tool("antenna_event_add_host", EVENT_ADD_HOST_SCHEMA, handle_event_add_host)
     ctx.register_tool("antenna_event_message", EVENT_MESSAGE_SCHEMA, handle_event_message)
+    ctx.register_tool("antenna_link_account", LINK_ACCOUNT_SCHEMA, handle_link_account)
 
     # ── Hook: auto-detect location + check web GPS events ─────────
     def on_pre_llm(messages, **kwargs):

package/lib/hermes-plugin/schemas.py

@@ -64,7 +64,8 @@ PROFILE_SCHEMA = {
 ACCEPT_SCHEMA = {
     "name": "antenna_accept",
     "description": (
-        "Accept a match. Use 'ref' from scan results (e.g. '1', '2') or target_device_id. "
+        "Accept a match. Use 'ref' from scan results (e.g. '1', '2'), target_device_id, "
+        "or profile_slug (from a public profile link like antenna.fyi/p/SLUG). "
         "Optionally share contact info."
     ),
     "parameters": {
@@ -79,7 +80,11 @@ ACCEPT_SCHEMA = {
             },
             "target_device_id": {
                 "type": "string",
-                "description": "Device ID (use ref instead when possible)",
+                "description": "Device ID (use ref or profile_slug instead when possible)",
+            },
+            "profile_slug": {
+                "type": "string",
+                "description": "Profile slug from a public profile link (e.g. 'yi' from antenna.fyi/p/yi). Resolves to device_id automatically.",
             },
             "contact_info": {
                 "type": "string",
@@ -378,3 +383,22 @@ EVENT_MESSAGE_SCHEMA = {
         "required": ["code", "sender_id", "channel", "message", "chat_id"],
     },
 }
+
+LINK_ACCOUNT_SCHEMA = {
+    "name": "antenna_link_account",
+    "description": (
+        "Link your Antenna agent profile to your antenna.fyi website account. "
+        "The user needs to provide their user_id from the dashboard (antenna.fyi/me). "
+        "After linking, the dashboard will show the same profile and match history."
+    ),
+    "parameters": {
+        "type": "object",
+        "properties": {
+            "sender_id": {"type": "string", "description": "The sender's user ID"},
+            "channel": {"type": "string", "description": "Platform name"},
+            "chat_id": {"type": "string", "description": "REQUIRED. Pass the chat/channel ID from message context."},
+            "user_id": {"type": "string", "description": "The user's antenna.fyi account UUID, visible on their dashboard"},
+        },
+        "required": ["sender_id", "channel", "chat_id", "user_id"],
+    },
+}

package/lib/hermes-plugin/tools.py

@@ -127,6 +127,8 @@ def handle_scan(params: dict) -> str:
             "line1": p.get("line1"),
             "line2": p.get("line2"),
             "line3": p.get("line3"),
+            "more_information": p.get("matching_context") or None,
+            "profile_slug": p.get("profile_slug") or None,
             "distance_m": p.get("distance_m") or p.get("dist_meters"),
         })
 
@@ -191,8 +193,19 @@ def handle_accept(params: dict) -> str:
                 target = rr.data
         except Exception:
             pass
+    # Resolve profile_slug to device_id
+    if not target and params.get("profile_slug"):
+        try:
+            slug_resp = sb.rpc("get_profile_by_slug", {"p_slug": params["profile_slug"]}).execute()
+            slug_data = slug_resp.data
+            if isinstance(slug_data, list) and slug_data:
+                target = slug_data[0].get("device_id")
+            elif isinstance(slug_data, dict) and slug_data.get("device_id"):
+                target = slug_data["device_id"]
+        except Exception:
+            pass
     if not target:
-        return _ok({"error": "No target. Use 'ref' from scan results or 'target_device_id'."})
+        return _ok({"error": "No target. Provide ref, target_device_id, or profile_slug."})
 
     sb.rpc("upsert_match", {
         "p_device_id_a": did,
@@ -381,6 +394,8 @@ def handle_discover(params: dict) -> str:
             "line1": p.get("line1"),
             "line2": p.get("line2"),
             "line3": p.get("line3"),
+            "more_information": p.get("matching_context") or None,
+            "profile_slug": p.get("profile_slug") or None,
         }
         if match_reason:
             profile["match_reason"] = match_reason
@@ -553,6 +568,8 @@ def handle_event_scan(params: dict) -> str:
             "line1": p.get("line1"),
             "line2": p.get("line2"),
             "line3": p.get("line3"),
+            "more_information": p.get("matching_context") or None,
+            "profile_slug": p.get("profile_slug") or None,
             "checked_in": bool(p.get("checked_in")),
             "role": p.get("role") or "participant",
             "status": p.get("status") or "active",
@@ -700,3 +717,21 @@ def handle_event_message(params: dict) -> str:
         rpc_params["p_target_ref"] = params["ref"]
     resp = sb.rpc("send_event_message", rpc_params).execute()
     return _ok(resp.data or {"error": "send_event_message failed"})
+
+
+def handle_link_account(params: dict) -> str:
+    """Link agent profile to antenna.fyi website account."""
+    sb = _sb()
+    did = _device_id(params["sender_id"], params["channel"], params.get("chat_id"))
+
+    resp = sb.rpc("bind_user_id", {
+        "p_device_id": did,
+        "p_user_id": params["user_id"],
+    }).execute()
+
+    if resp.data and resp.data.get("error"):
+        return _ok(resp.data)
+
+    data = resp.data or {}
+    data["message"] = "账号已关联！现在你可以在 antenna.fyi/me 看到你的完整 profile 和匹配记录了。"
+    return _ok(data)

package/lib/mcp.js

@@ -24,6 +24,7 @@ import {
   rejectParticipant,
   addCohost,
   sendEventMessage,
+  linkAccount,
   deriveDeviceId,
   PROFILE_FIELDS,
 } from "./core.js";
@@ -143,18 +144,19 @@ export async function startMcpServer() {
 
   server.tool(
     "antenna_accept",
-    "Accept a match. Use 'ref' from scan results (e.g. '1', '2') OR target_device_id directly.",
+    "Accept a match. Use 'ref' from scan results (e.g. '1', '2'), target_device_id, or profile_slug (from a public profile link like antenna.fyi/p/SLUG). Optionally share contact info.",
     {
       sender_id: z.string().describe("The sender's user ID"),
       channel: z.string().describe("Channel name"),
       ref: z.string().optional().describe("Ref number from scan results (e.g. '1')"),
-      target_device_id: z.string().optional().describe("Device ID (use ref instead when possible)"),
+      target_device_id: z.string().optional().describe("Device ID (use ref or profile_slug instead when possible)"),
+      profile_slug: z.string().optional().describe("Profile slug from a public profile link (e.g. 'yi' from antenna.fyi/p/yi). Resolves to device_id automatically."),
       contact_info: z.string().optional().describe("Contact info to share"),
     },
-    async ({ sender_id, channel, ref, target_device_id, contact_info }) => {
+    async ({ sender_id, channel, ref, target_device_id, profile_slug, contact_info }) => {
       try {
         const deviceId = deriveDeviceId(sender_id, channel);
-        const result = await accept({ device_id: deviceId, target_device_id, ref, contact_info });
+        const result = await accept({ device_id: deviceId, target_device_id, ref, profile_slug, contact_info });
         return jsonResult(await withMatchNotifications(deviceId, result));
       } catch (e) {
         return jsonResult({ error: e.message });
@@ -508,6 +510,24 @@ export async function startMcpServer() {
     }
   );
 
+  // ─── antenna_link_account ────────────────────────────────
+
+  server.tool(
+    "antenna_link_account",
+    "Link your Antenna agent profile to your antenna.fyi website account. The user needs to provide their user_id from the dashboard (antenna.fyi/me). After linking, the dashboard will show the same profile and match history.",
+    {
+      sender_id: z.string().describe("The sender's user ID"),
+      channel: z.string().describe("Channel name"),
+      user_id: z.string().describe("The user's antenna.fyi account UUID, visible on their dashboard"),
+    },
+    async ({ sender_id, channel, user_id }) => {
+      try {
+        const result = await linkAccount({ device_id: deriveDeviceId(sender_id, channel), user_id });
+        return jsonResult(result);
+      } catch (e) { return jsonResult({ error: e.message }); }
+    }
+  );
+
   const transport = new StdioServerTransport();
   await server.connect(transport);
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "antenna-fyi",
-  "version": "1.3.20",
+  "version": "1.3.22",
   "description": "Antenna \u2014 nearby people discovery. CLI + MCP server + OpenClaw skill & plugin, all in one package.",
   "type": "module",
   "bin": {

package/skill/SKILL.md

@@ -1,325 +1,274 @@
 ---
 name: antenna
-description: "Nearby people discovery via Antenna. Use when a user shares location, asks who's nearby, wants to set up their profile card, or interacts with match results. Handles location-based social discovery through the antenna_scan, antenna_profile, antenna_accept, antenna_check_matches, and antenna_bind tools."
+description: "AI-native social discovery via Antenna. Use when a user wants to meet interesting people — through nearby scan, global recommendations, profile links, or events. Handles profile management, matching, and contact exchange."
 metadata: { "openclaw": { "always": true } }
 ---
 
-# Antenna - Nearby People Discovery
+# Antenna — AI-Native Social Discovery
 
-You have access to Antenna for location-based social discovery.
+Antenna 帮你的用户发现值得认识的人。不只是"附近的人"——profile link、全球推荐、活动，都是发现路径。
 
-**How to call Antenna:**
-- If you have Antenna plugin tools registered (antenna_scan, antenna_profile, etc.) - use them directly.
-- If not, use CLI: `antenna <command> [flags]`. Example: `antenna scan --id <platform>:<user_id>`. The CLI supports all the same features.
-- All tool names map to CLI commands: `antenna_scan` → `antenna scan`, `antenna_event_create` → `antenna event --create`, etc.
-- **Always pass `chat_id`** when calling any Antenna tool. This is the chat/channel ID from your message context (e.g. Discord channel ID, Telegram chat ID). Antenna uses it to send you notifications about matches and event approvals.
+**核心流程：发现 → 判断 → accept → 交换联系方式。**
 
-## Onboarding - 装上之后主动引导
+发现可以来自任何渠道：
+- 📡 **附近扫描** — `antenna_scan`，基于 GPS 的周边发现
+- 🌍 **全球推荐** — `antenna_discover`，每天 1 个最匹配的人
+- 🔗 **Profile 链接** — 用户收到 `antenna.fyi/p/xxx` 链接，agent 读取后直接 accept
+- 🎪 **活动** — `antenna_event_scan`，同一个活动里的人
 
-Plugin 安装后,agent 应该**主动**开始引导,不要等用户问"怎么用"。
+**Accept 不需要先 scan。** 只要你知道对方的 `ref`、`profile_slug` 或 `device_id`，就可以直接 accept。
 
-**前置条件:** 用户需要先在 antenna.fyi 注册账号,从 Dashboard (antenna.fyi/me) 获取 API key,然后把 key 交给 agent。如果用户还没注册,引导他们去 antenna.fyi 注册。
+## How to call Antenna
 
-### 流程
-
-**第一步:打招呼 + 解释**
-> "嘿,你装了 Antenna--它能帮你发现附近有意思的人。先确认一下,你在 antenna.fyi 注册过了吗?拿到 API key 了吗?有了的话我帮你做张名片,然后看看附近有谁。"
-
-**第二步:聊天收集 → 生成名片 → 确认**
+- 如果有 Antenna plugin tools（antenna_scan, antenna_profile 等），直接用。
+- 如果没有，用 CLI：`antenna <command> [flags]`。
+- **所有 tool 必须传 `chat_id`**——Antenna 用它发通知。
 
-Agent 跟用户聊几句,了解他们是谁、做什么、对什么感兴趣、想认识什么人。然后 agent 自己完成以下工作(不需要用户参与):
-- 生成 matching_context(~200 字,用于 embedding 匹配,不展示给别人)
-- 从中提炼 line1/2/3 + 选一个 emoji + display_name
+## Onboarding — 装上后主动引导
 
-然后展示名片预览给用户确认:
-> 你的名片:
-> 🦦 Yi
-> · Product Designer,做 AI 搜索体验
-> · 对 AI agent、音乐、游泳感兴趣
-> · 想认识做 AI 产品和独立创作的人
->
-> 这样可以吗?要改哪里告诉我。
+Plugin 安装后，agent **主动**开始引导，不要等用户问。
 
-用户确认后才调 `antenna_profile(action="set")` 保存(matching_context + line1/2/3 + emoji + name 一起存)。
-用户要改 → 改完重新预览 → 再确认。
+**前置条件：** 用户需要先在 antenna.fyi 注册账号，从 Dashboard 获取 API key。如果没注册，引导去 antenna.fyi。
 
-**不要跳过确认。名片是展示给别人看的,必须让用户看过才存。**
+### 流程
 
-**第二步半:名片存好后,立刻推荐 2-3 个匹配的人**
+**第一步：打招呼 + 解释**
+> "嘿，你装了 Antenna——它能帮你发现有意思的人。先确认一下，你在 antenna.fyi 注册过了吗？拿到 API key 了吗？"
 
-名片保存成功后,**立刻**调 `antenna_discover` 获取 2-3 个全球推荐,让用户马上看到 Antenna 的价值:
-> "名片存好了!我先帮你看看有谁跟你特别像——"
-> (展示 2-3 个推荐 + 个性化匹配理由)
+**第二步：聊天收集 → 生成名片 → 确认**
 
-这一步让用户立刻体验到产品价值,不要跳过。
+跟用户聊几句，了解他们是谁、做什么、想认识什么人。然后 agent 自己生成：
+- more_information（~200 字，给 agent 匹配用的私密上下文，不展示给别人）
+- 从中提炼 line1/2/3 + display_name
 
-**第三步:推荐完后,立刻调 antenna_bind**
+展示预览给用户确认：
+> 你的名片：
+> Yi
+> · Product Designer，做 AI 搜索体验
+> · 对 AI agent、音乐、游泳感兴趣
+> · 想认识做 AI 产品和独立创作的人
+>
+> 这样可以吗？要改哪里告诉我。
 
-**这一步是强制的。** 名片保存成功后,你**必须立刻**调用 `antenna_bind` 生成链接并发给用户。不要问用户要不要,不要等用户说什么,直接调。
+确认后才调 `antenna_profile(action="set")` 保存。**不要跳过确认。**
 
-调用 `antenna_bind` 生成链接,发给用户:
-> "名片存好了 ✅ 点这个链接,在手机浏览器打开,允许定位就行:
-> [链接]
-> 我收到你的位置后会自动帮你看看附近有谁。"
+**第三步：立刻推荐 2-3 个人**
 
-备选:如果用户在 Telegram/WhatsApp 里,也可以直接发位置消息。但优先用链接。
+名片存好后，**立刻**调 `antenna_discover` 获取全球推荐，让用户马上看到价值：
+> "名片存好了！我先帮你看看有谁跟你特别像——"
 
-**⚠️ 如果你保存了名片但没有调 antenna_bind,你就没有完成 onboarding。**
+**第四步：调 antenna_bind 获取 GPS 链接**
 
-**第四步:设置匹配检查定时任务**
+**强制。** 名片存好后**必须立刻**调用 `antenna_bind` 生成链接并发给用户：
+> "点这个链接，在手机浏览器打开，允许定位就行：[链接]"
 
-onboarding 完成后,帮用户设置一个每小时自动检查匹配的 cron 任务,这样有人 accept 用户时能及时通知。
+GPS 不是 Antenna 的唯一入口，但它开启了附近发现的能力。
 
-如果你有 cron 能力(Hermes: `hermes cron`,OpenClaw: `openclaw cron`),创建一个定时任务:
-- 每 1 小时调用 `antenna_check_matches`
-- 如果有新的 mutual match 或 incoming accept,通知用户
-- 如果没有新匹配,不打扰用户
+**第五步：设置定时任务**
 
-示例(Hermes):
+设一个每小时检查匹配的 cron：
 ```
-hermes cron add --every 1h --message "Check antenna matches: call antenna_check_matches. If there are new mutual matches or incoming accepts, tell the user. Also call antenna_discover once per day to get a global recommendation. If nothing new, reply HEARTBEAT_OK."
+openclaw cron add --every 1h --message "Check antenna matches: call antenna_check_matches. If there are new mutual matches or incoming accepts, tell the user. If nothing new, reply HEARTBEAT_OK."
 ```
 
-**第五步:问用户要不要全球推荐**
+**第六步：问要不要全球推荐**
+> "要我每天帮你找一个全球最像你的人吗？"
 
-cron 设完后,问用户一句:
-> "要我每天帮你找一个全球最像你的人吗?"
+### Linking to antenna.fyi account
 
-用户说要 → cron 每天调 `antenna_discover` 推送。
-用户说不要 → 只在 scan 没人时 fallback。
+如果用户之前通过 agent 创建过 profile（没有网站账号），现在注册了 antenna.fyi：
+1. 让用户从 antenna.fyi/me 复制 user ID
+2. 调 `antenna_link_account(user_id = "xxx")`
+3. 确认："关联成功！你现在可以在 dashboard 上看到完整的 profile 和匹配记录了。"
 
-**第六步:启动实时通知**
+这把 agent 创建的 profile（带全部历史）关联到网站账号。
 
-onboarding 完成后,启动 `antenna watch` 后台进程,实时接收匹配通知和活动审批通知。
+## When to use
 
-**判断方法(不要猜):**
-1. 先试 `antenna status --id <device_id>` - 如果输出 "Watch: ✅ running",已经在跑,不需要再启动
-2. 如果不在跑,试 `antenna watch --id <device_id> --push hermes,openclaw &` 启动后台进程
-3. 如果 exec 报错(不支持后台进程),用 cron 替代:
+- **首次安装后**：主动 onboarding
+- 用户分享位置 → `antenna_scan`
+- 用户问"附近有谁" → `antenna_scan`
+- 用户收到 profile 链接（`antenna.fyi/p/xxx`）→ 读取 profile → 判断 → `antenna_accept`
+- 用户想编辑名片 → `antenna_profile`
+- 用户说 accept / skip → `antenna_accept` / `antenna_pass`
+- 用户问匹配状态 → `antenna_check_matches`
 
-Hermes cron:
-```
-hermes cron add --every 1h --message "Check antenna matches: call antenna_check_matches. If there are new mutual matches or incoming accepts, tell the user. If nothing new, reply HEARTBEAT_OK."
-```
+## Discovery Paths
 
-OpenClaw cron:
-```
-openclaw cron add --every 1h --message "Check antenna matches: call antenna_check_matches. If there are new mutual matches or incoming accepts, tell the user. If nothing new, reply HEARTBEAT_OK."
-```
+### 1. 附近扫描（antenna_scan）
+基于 GPS 发现 1km 内的人。需要位置信息。
+- 如果没有 GPS，先调 `antenna_bind` 或让用户发位置
+- 返回 raw profile cards，**agent 判断谁值得推荐**
 
-**优先级:** watch > cron。watch 是 2 分钟延迟,cron 是 1 小时。
+### 2. 全球推荐（antenna_discover）
+每天 1 个全球最匹配的人，不需要 GPS。
+- 用在日常 cron 里，或用户主动要求
 
-## When to use
+### 3. Profile 链接
+用户收到 `antenna.fyi/p/xxx` 链接时：
+1. 用 `web_fetch` 读取页面——页面里有 `<script id="antenna-profile-data">` JSON，包含完整 profile
+2. 读取 more_information、interest_tags、个人描述等
+3. 结合你对用户的了解，判断是否推荐
+4. 如果用户想 accept → 调 `antenna_accept(profile_slug="xxx")`
+
+**不需要先 scan。** Profile 链接是独立的发现路径。
 
-- **首次安装后**: 主动开始 onboarding(名片 → 位置)
-- User shares a location (Telegram live location, WhatsApp pin, or tells you where they are)
-- User asks "附近有谁" / "who's nearby" / "周围有什么人"
-- User wants to set up or edit their profile card (名片)
-- User accepts or skips a match
-- User asks about match status or wants to exchange contact info
+### 4. 活动（Events）
+同一个活动里的人。详见 EVENTS.md。
 
 ## Tools
 
 ### `antenna_scan`
-Scan for nearby people **and events**. Returns raw profile cards + active events within 5km.
-**Read-only - does NOT update your location.** To update location, use `antenna_checkin` or `antenna_bind`.
-- `lat`, `lng`: coordinates (from `LocationLat`/`LocationLon` context, or geocoded from user input)
-- `radius_m`: search radius in meters (default 500, max 1000) for people; events search uses 5km
-- `sender_id`: the user's id from message context
-- `channel`: the platform/channel name (any platform works: telegram, discord, whatsapp, webchat, signal, slack, matrix, clawx, etc.)
-- Returns `profiles` (nearby people) + `nearby_events` (active events with name, participants count, code)
-
-**Location staleness:** Before scanning, check if the user's GPS is recent. If `last_seen_at` is older than 2 hours, prompt the user to update their location (`antenna_bind` or `antenna_checkin`). Stale GPS = wrong results.
-
-## GPS Logic
+扫描附近的人和活动。**只读——不会更新你的位置。**
+- `lat`, `lng`：坐标（可选，没有的话用已绑定的 GPS）
+- `radius_m`：搜索半径（默认 500m，最大 1000m）
+- `sender_id`, `channel`, `chat_id`：必填
+- 返回 `profiles`（附近的人）+ `nearby_events`（5km 内的活动）
+- 每个 profile 包含 `ref`（用于 accept）、`profile_slug`（公开链接）、`more_information`（匹配上下文）
 
-**Profile GPS** - the user's location ("where am I")
-- Updated via `antenna_bind(purpose="profile")` or `antenna_checkin`
-- Location is never stored raw
-- Used for: `antenna_scan` (nearby people/events), `antenna_event_checkin` (distance check)
-- Has `last_seen_at` timestamp. **Expires conceptually after 2h** - agent should prompt refresh
-
-**Event GPS** - the event's location ("where is the event")
-- Set via `antenna_bind(purpose="event")` or `antenna_event_create(lat, lng)`
-- Precise coordinates (NOT blurred)
-- Used for: check-in distance verification (≤1km), `nearby_events` discovery (5km)
-- Does not expire - event location is fixed
-
-**Relationship:** check-in = compare profile GPS vs event GPS. scan = use profile GPS to find nearby people + events.
-
-After receiving the nearby profiles, **you decide** who to recommend:
-- Use everything you know about the user: their SOUL.md, memory, recent conversations, interests, current mood
-- Compare each nearby person's three-line card against your understanding of the user
-- Write a personalized match reason for each person you recommend
-- Skip people who clearly aren't a match - don't recommend everyone
-- If you're unsure, lean toward recommending (let the user decide)
+**GPS 时效：** 如果 `last_seen_at` 超过 2 小时，提示用户更新位置。
 
 ### `antenna_profile`
-View or update the user's name card.
-- `action`: "get" or "set"
-- `sender_id`, `channel`: from context
-- For "set": `display_name`, `emoji`, `line1`, `line2`, `line3`, `visible`, `matching_context`
-
-The name card has:
-- **emoji**: a single emoji that represents them
-- **display_name**: how they want to be called
-- **line1**: who they are / what they do
-- **line2**: what they're into
-- **line3**: what they're looking for right now
-- **matching_context** (not shown to others): A richer description generated by the agent based on what it knows about the user - career background, tech stack, interests, projects, personality traits. ~200 words. **This is the source data for embedding-based matching.** line1/2/3 are derived from it for display, not the other way around.
-
-**During onboarding, generate `matching_context` FIRST** based on your conversation with the user (+ memory, SOUL.md, etc.). Then derive line1/2/3 from it. Don't ask the user to write matching_context - you write it. Example:
-> "Product designer at a tech company in Beijing, focusing on AI search experience. Interested in music (Sakamoto), swimming, cooking, language learning. Recently exploring AI agent ecosystems and social discovery. Looking to connect with AI builders, indie hackers, and creative technologists."
+查看或更新用户名片。
+- `action`："get" 或 "set"
+- `sender_id`, `channel`, `chat_id`
+- "set" 时传：`display_name`, `line1`, `line2`, `line3`, `visible`, `matching_context`
+
+名片内容：
+- **display_name**：显示名称
+- **line1**：个人描述（谁 / 做什么）
+- **line2**：想认识的人
+- **line3**：想要的交流方式
+- **matching_context**（more_information，不展示给别人）：agent 基于对用户的了解生成的详细描述，~200 字。**这是匹配的核心数据源。** line1/2/3 从它提炼出来，不是反过来。
 
 ### `antenna_accept`
-Accept a match after the user sees results. Can optionally include contact info to share.
-- `sender_id`, `channel`, `target_device_id`
-- `contact_info` (optional): e.g. "WeChat: yi_xxx" or "Telegram: @yi"
+接受一个匹配。**不需要先 scan**——任何发现路径都可以触发 accept。
+- `sender_id`, `channel`, `chat_id`：必填
+- 三种方式指定对方（任选一种）：
+  - `ref`：来自 scan/discover 结果的编号
+  - `profile_slug`：来自 profile 链接（如 `antenna.fyi/p/yi` → `profile_slug="yi"`）
+  - `target_device_id`：内部 ID（尽量用 ref 或 slug）
+- `contact_info`（可选）：分享联系方式
+
+### `antenna_pass`
+跳过一个人，不再推荐。
+- `sender_id`, `channel`, `chat_id`
+- `ref` 或 `target_device_id`
 
 ### `antenna_check_matches`
-Check for mutual matches and contact info updates.
-- `sender_id`, `channel`
-- Returns mutual matches with any contact info the other person shared
+检查匹配状态。
+- `sender_id`, `channel`, `chat_id`
+- 返回 mutual matches + incoming accepts + 联系方式
 
 ### `antenna_bind`
-Generate a GPS binding link. **You MUST call this immediately after saving a profile.** Do not skip this step.
-- `sender_id`, `channel`: from context
-- `purpose`: optional - `'profile'` (default) updates user location; `'event'` sets event location
-- `event_code`: required when `purpose='event'`
-- Returns a URL like `https://www.antenna.fyi/locate?token=xxx`
-- Send this link to the user - they open it on their phone, allow GPS, and their location is automatically shared
-- **MANDATORY after profile save. Do not wait for user to ask.**
-- **For events:** When a creator needs to set event location, call with `purpose='event'` and `event_code`. The GPS will update the event's coordinates, NOT the user's profile.
+生成 GPS 绑定链接。
+- `sender_id`, `channel`, `chat_id`
+- `purpose`：`'profile'`（默认，更新用户位置）或 `'event'`（设活动位置）
+- `event_code`：purpose=event 时必填
+- 返回 URL，用户在手机打开后自动共享位置
+- **Onboarding 后必须调用。** 不要等用户问。
+
+### `antenna_link_account`
+关联 agent profile 到 antenna.fyi 网站账号。
+- `sender_id`, `channel`, `chat_id`：必填
+- `user_id`：用户的 antenna.fyi 账号 UUID（从 dashboard 获取）
+- 把已有的 agent profile（带全部历史）绑定到网站账号
+- 如果用户先在网站注册了（产生空 profile），空 profile 自动删除
+- 一次性操作
 
 ### `antenna_discover`
-Get today's global recommendation - the person most similar to you worldwide. 1 per day, no repeats.
-- `sender_id`, `channel`: from context
-- Returns 1 profile (embedding similarity match) that hasn't been recommended before
-- If all users have been recommended, returns a message saying "wait for new people"
-- Use this in the daily cron job, or when user asks "find someone interesting globally"
-
-### `antenna_pass`
-Pass/skip a person. They won't be recommended again.
-- `sender_id`, `channel`: from context
-- `ref`: ref number from scan/discover results (e.g. '1')
-- `target_device_id`: device ID (use ref instead when possible)
-- Use when the user says "skip", "pass", "not interested", etc.
+全球推荐——每天 1 个最匹配的人。
+- `sender_id`, `channel`, `chat_id`
+- 不需要 GPS
+- 如果所有人都推荐过了，返回"等新人加入"
 
 ### `antenna_checkin`
-Check in at a location - update your position so others can find you when they scan.
-- `lat`, `lng`: coordinates (required)
-- `sender_id`, `channel`: from context
-- `place_name`: optional name of the place
-- Use when the user says "I'm at XX" or wants to be discoverable without scanning others
-
-## Data Transparency - what Antenna sends
-
-Antenna only communicates with Supabase (bcudjloikmpcqwcptuyd.supabase.co) via HTTPS.
-
-**Data sent:**
-- GPS coordinates (never stored raw — location is processed server-side)
-- Your three-line profile card (text you wrote yourself)
-- Match status (accept/skip)
-- Contact info you choose to share
-- Profile embedding vector (generated from your 3 lines, used for matching)
-
-**Data NOT sent:**
-- Your conversations with your agent
-- Your files, browsing history, or any other personal data
-- Anything not listed above
+签到——更新你的位置。
+- `lat`, `lng`：必填
+- `sender_id`, `channel`, `chat_id`
+- `place_name`：可选
+- 用于"我在 XX"场景
 
-All data is transmitted over HTTPS and stored in Supabase (Tokyo region).
-Visibility is controlled by time decay — recent event participants are fully visible, older connections gradually fade.
-Source code is open: https://github.com/H1an1/Antenna
-
-## Behavior guidelines
-
-### First-time user - 名片创建原则
-
-具体流程见上方 Onboarding 第二步。以下是 agent 应该遵守的原则:
-
-- **不要让用户填表。** 不要一次性说"请填写 emoji、名字、三句话介绍"--跟用户聊天,你来生成。
-- **每次只问一个问题。** 不要一口气问完所有信息。
-- **用户说的原话尽量保留。** 可以帮用户缩短太长的回答,但要在预览时让用户确认。
-- **不要在名片里写联系方式。** 名片三句话对所有人可见。联系方式应该在 accept 时单独分享,只有双方都同意后才能看到。如果用户在聊天中提到联系方式,提醒他们。
-- **line1 必填。** 后端会拒绝没有 line1 的新 profile,并对缺失的 line2/line3 返回 warning。
-- **确认后才存。** 见 Onboarding 第二步。
+## GPS Logic
 
-### Showing results - 你来判断,不是服务器
+**Profile GPS** — 用户的位置
+- 通过 `antenna_bind(purpose="profile")` 或 `antenna_checkin` 更新
+- 位置不原始存储
+- 2 小时后概念上过期，agent 应提示刷新
 
-**第一次 scan 的新用户:** 简短一句解释:"这是附近的人。Antenna 基于 AI 匹配,看到感兴趣的人 accept,双向匹配后交换联系方式。"
+**Event GPS** — 活动的位置
+- 通过 `antenna_bind(purpose="event")` 或 `antenna_event_create(lat, lng)` 设置
+- 精确坐标（不模糊）
+- 不过期
 
-**Profile 不完整时:** 如果用户的 profile 只有 1 行,提示:"你的名片只填了一行,补完后匹配质量会更好。要现在补吗?"
+## Behavior Guidelines
 
-`antenna_scan` 返回的是附近所有人的名片,**没有打分、没有预匹配**。你需要:
+### 名片创建原则
+- **不要让用户填表。** 跟用户聊天，你来生成。
+- **每次只问一个问题。**
+- **用户说的原话尽量保留。** 帮缩短但让用户确认。
+- **不要在名片里写联系方式。** 联系方式在 accept 时分享。
+- **line1 必填。**
+- **确认后才存。**
 
-**全球推荐 fallback:** 如果 scan 结果里有 `global: true`,说明附近没人,这些是全球推荐。告诉用户"附近暂时没人,但全球有这几个有意思的人",然后正常推荐。用户仍然可以 accept。
+### Showing results — 你来判断
 
-1. 读每个人的名片(emoji、name、line1/2/3)
-2. 结合你对用户的全部了解,判断谁值得推荐
-3. 为每个推荐的人写一句**个性化的理由**--不是"你们都提到了 X",而是真正有洞察的话
+scan 和 discover 返回的是 raw profile cards，**没有打分**。你需要：
+1. 读每个人的名片 + more_information
+2. 结合你对用户的全部了解判断谁值得推荐
+3. 为每个推荐的人写一句**个性化的理由**
+4. **不要推荐所有人。** 质量 > 数量。
 
-**⚠️ 隐私规则:展示结果时绝对不要显示 device_id。** `device_id`(如 `platform:user123`)是内部标识符,包含用户的平台和 ID,属于隐私信息。只显示 emoji + 名字 + 三句话 + 你写的匹配理由。`device_id` 只在内部调 `antenna_accept` 时用,不要展示给用户。
+**全球推荐 fallback：** 如果 scan 结果有 `global: true`，说明附近没人。告诉用户"附近暂时没人，但全球有这个人跟你很像"。
 
-比如你知道用户最近在学吉他,看到附近有人写"组乐队找吉他手":
-> 🎸 **小林** - 在组后摇乐队,找吉他手
-> → 你不是最近在学吉他吗?这人在找吉他手诶
+### Profile 链接场景
 
-比如你知道用户是设计师,对方也做设计:
-> 🎨 **Kira** - UI 设计师,在做 AI 产品
-> → 你们都做 AI 方向的设计,可以聊聊各自的方法论
+用户收到或提到 `antenna.fyi/p/xxx` 时：
+1. 抓取页面，读 `#antenna-profile-data` JSON
+2. 展示对方 profile + 你的判断
+3. 用户想 accept → `antenna_accept(profile_slug="xxx")`
+4. 用户想 skip → `antenna_pass` 或直接不操作
 
-**不要推荐所有人。** 如果附近 5 个人里只有 1 个真的匹配,就只推 1 个。质量 > 数量。
+**这跟 scan 是完全平级的发现路径。**
 
 ### Accepting & contact exchange
-When the user wants to accept a match:
-1. Call `antenna_accept` with the target's device_id
-2. **立刻问**:"想分享什么联系方式给对方?微信号、Telegram、手机号、Instagram......随便哪个都行"
-3. 用户给了联系方式 → call `antenna_accept` again with `contact_info`
-4. 用户不想分享 → "也行,先 accept 着,以后想分享再说"
-5. If mutual match, tell the user the other person's contact info (if they shared)
-6. If not mutual yet, tell the user: "已发出,等对方回应"
-
-**不要跳过第 2 步。** 联系方式是最终目标--不然 accept 了也没用,两个人找不到对方。
-
-### Checking match status
-Use `antenna_check_matches` when:
-- User asks "有人回复我吗" / "匹配状态怎么样"
-- Periodically during conversation if the user has pending matches
-
-### Location sources
-- **Telegram/WhatsApp location**: context will have `LocationLat`, `LocationLon` - use directly
-- **User says a place name**: geocode it first (use web_search or a geocoding service), then call antenna_scan
-- **Live location**: note that it's real-time, tell the user you'll check for new people
+accept 可以从任何路径触发：
+1. 调 `antenna_accept`（用 ref、profile_slug 或 device_id）
+2. **立刻问**："想分享什么联系方式给对方？"
+3. 用户给了 → 再调一次 `antenna_accept` 带 `contact_info`
+4. 用户不想 → "先 accept 着，以后想分享再说"
+5. 如果 mutual match → 展示对方联系方式
+6. 如果还没 mutual → "已发出，等对方回应"
 
-### Privacy
-- Never reveal exact coordinates to other users
-- **Never show device_id to users** (e.g. `telegram:12345`, `discord:67890`) - this is internal only
-- Never share someone's platform or username with another user
-- Only show the profile info (name, emoji, three lines)
-- Contact info is only shared when the user explicitly agrees
-- Location is never stored raw
+**不要跳过第 2 步。**
 
-### Time Decay — 可见性随时间衰减
-
-Profiles 是永久的,但可见性随时间衰减:
-- **Event 后 0-7 天:** 全部参与者互相可见
-- **7-30 天:** 只有互相 scan 过 / 有共同活动的人可见
-- **30 天后:** 需要新事件重新激活
-
-事件(Event)是最强的信任信号——"同一个活动"比"附近"更有意义。
+### Privacy
+- **永远不要显示 device_id**——这是内部标识符
+- 只展示名字 + 三句话 + 你写的匹配理由
+- 不要泄露对方的平台或用户名
+- 联系方式只在用户明确同意时分享
+- GPS 不原始存储
+
+### Time Decay — 可见性衰减
+- Event 后 0-7 天：全部参与者互相可见
+- 7-30 天：只有互相 scan 过 / 有共同活动的人可见
+- 30 天后：需要新事件激活
+
+### Heartbeat — 自动查匹配
+Plugin 后台每 10 分钟查一次新匹配。看到 `[Antenna] 🎉` 时：
+1. 调 `antenna_check_matches`
+2. 告诉用户 + 展示对方名片
+3. 展示联系方式（如果有）
 
-### Heartbeat - 自动查匹配
+## Events
 
-Plugin 自带后台服务,每 10 分钟轮询一次 Supabase 查新的 mutual match。如果发现新匹配,会在用户下次跟 agent 说话时通过 `[Antenna] 🎉` 提示注入 context。
+详见 EVENTS.md。包括：`antenna_event_create`, `antenna_event_join`, `antenna_event_scan`, `antenna_event_end`, `antenna_event_checkin`, `antenna_event_upload_image`, `antenna_event_update`, `antenna_event_approve`, `antenna_event_reject`, `antenna_event_add_host`, `antenna_event_message`。
 
-当你看到 `[Antenna] 🎉 有 X 个新的匹配通知` 时:
-1. 调 `antenna_check_matches` 拿详情
-2. 告诉用户:"有人想认识你!" + 展示对方名片
-3. 如果对方分享了联系方式,一并展示
+## Data Transparency
 
-用户不需要主动问,agent 会自动收到通知。
+Antenna 只跟 Supabase (bcudjloikmpcqwcptuyd.supabase.co) 通信。
 
-## Events
+**发送的数据：** GPS（不原始存储）、名片文本、匹配状态、你选择分享的联系方式、Profile embedding。
+**不发送的数据：** 你跟 agent 的对话、文件、浏览记录。
 
-For event-related tools and behavior (creating, joining, scanning, managing events), see the **antenna-events** skill (`EVENTS.md`). Event tools include: `antenna_event_create`, `antenna_event_join`, `antenna_event_scan`, `antenna_event_end`, `antenna_event_checkin`, `antenna_event_upload_image`, `antenna_event_update`, `antenna_event_approve`, `antenna_event_reject`, `antenna_event_add_host`, `antenna_event_message`.
+Source code: https://github.com/H1an1/Antenna