# 收件箱，agent 也能帮你处理

> 让 Claude、ChatGPT、Cursor 或你自己的 agent 通过 Hearl 的 MCP 服务器、命令行、Skill 或 REST API，分拣 X、Reddit、Hacker News 上关于你产品的讨论，起草回复，汇总用户反馈。

把 Claude、ChatGPT、Cursor 或你自己的脚本接到 Hearl。它们读取 X、Reddit 和 Hacker News 上关于你产品的讨论，分拣、起草回复、给你汇报。每次改动都会以“你，通过 agent”记在时间线上。

## 大家会这样吩咐自己的 agent

### 早上分拣

agent 读一遍未分配的讨论，把和产品无关的关掉，其余的建议负责人和截止时间。你确认后，它来执行。

Example: "帮我分拣 Hearl 收件箱，把今天的讨论分出去。"

### 起草回复

对没人回的高优先级讨论，agent 读完整个帖子，用帖子的语言起草回复，存成内部备注，由同事审过后发出去。

Example: "给关于同步故障、还没人回的 Reddit 帖子起草回复。"

### 盯住追问

团队回复后用户又追问了，这条讨论会回到收件箱。问 agent 发生了什么、现在谁在跟。

Example: "昨天以来哪些用户追问了？分别是谁在跟？"

### 每周报告

被问得最多和抱怨最多的点（附链接）、解决了什么、哪些逾期、谁负责，几百字，直接发到团队群里。

Example: "根据 Hearl 写一份本周用户反馈周报。"

### 在终端里处理

不离开编辑器就能看队列、认领、带结果关闭；加 --json 还能写进 CI 脚本。

Example: "hearl inbox --view mine"

### 接入自己的采集

已经在抓论坛或 Discord？用 REST API 把这些讨论推进同一个收件箱，交给 Hearl 自动判断。

Example: "POST /api/v1/products/{slug}/threads"

## 四种接入方式，同一套工具

MCP、命令行和 REST API 提供的是同一套操作。在工作空间的“Agent 与 API”里创建密钥，可选只读或读写。

### MCP 服务器

远程 MCP，走 Streamable HTTP。Claude Code、Cursor、Windsurf 等 MCP 客户端都能直接连；Claude Desktop 通过命令行的 stdio 桥接接入。10 个工具，3 个现成的 prompt。

Endpoint: https://hearl.org/mcp (server card: https://hearl.org/.well-known/mcp/server-card.json)

```
claude mcp add --transport http hearl https://hearl.org/mcp --header "Authorization: Bearer $HEARL_TOKEN"
```

### 命令行

npx hearl。登录一次，然后 summary、inbox、show、assign、done、due、note。所有命令都支持 --json，mcp install 帮你配置客户端。

```
npx hearl login
npx hearl inbox --view unassigned
```

### Agent Skill

一份 SKILL.md，告诉任何 agent 什么时候用 Hearl、怎么接入，以及分拣、起草回复、写报告的工作流程。已登记在 agent skills 索引里。

https://hearl.org/.well-known/agent-skills/hearl/SKILL.md

### REST API

普通 HTTPS，Bearer 密钥，附 OpenAPI 3.1 描述。脚本、自动化或你自己的采集器都能用。

OpenAPI: https://hearl.org/api/v1/openapi.json

## 工具

读取类工具任何密钥都能用，修改类工具需要读写密钥。

- `get_summary` (read): Counts of conversations that need action, are unassigned, overdue or need a human check, plus new and closed this week, split by product and platform. Start here to see how the team is doing.
- `list_conversations` (read): List posts and threads from X, Reddit, Hacker News and the other connected channels in a view of the shared inbox, most urgent first. Views: todo (needs action or in progress), unassigned, mine, assisting, overdue, review (the AI was unsure), done, all. Each item has postedAt for date filtering; own_post means the team's own post.
- `get_conversation` (read): Full post with its replies, the thread it answers, the AI judgment with probabilities, whether the team already replied, owner, collaborators, due date, outcome and the activity timeline. Use it before drafting a reply or deciding who should own it.
- `list_products` (read): Products this workspace tracks, with how many conversations need action for each.
- `list_members` (read): Workspace members with id, name, email and role. Use the email or id to assign conversations.
- `assign_conversation` (write): Give a conversation one owner: a member id, their email, "me" (the person who created this token) or null to unassign. An unstarted conversation moves to in_progress.
- `set_state` (write): Move a conversation through the workflow: open, in_progress, waiting_user, waiting_internal or done. When marking done, record the outcome in a sentence (what was replied, fixed or decided).
- `set_due_date` (write): Set when the conversation should be handled by (ISO date or datetime), or null to clear it. Overdue ones show up in the overdue view.
- `add_note` (write): Add a note to the conversation's timeline, visible only to the team inside Hearl (never posted publicly). Use @name to mention a member. Good for leaving a draft reply, a summary or a hand-off.
- `mark_irrelevant` (write): Close a conversation that isn't about the product and record it as filtering feedback. It leaves the inbox; it can be reopened with set_state. Confirm with the user before closing many.

## 现成的 prompt

- `triage_inbox`: Go through unassigned conversations, close the irrelevant ones, and suggest an owner and due date for the rest.
- `draft_replies`: Draft public replies for high-priority posts nobody has answered, and leave each draft as a note for a teammate to post.
- `weekly_report`: Summarize what people said about the product this week and how the team handled it.

## agent 替团队干活，但不替团队公开发言

- Hearl 从不发帖。agent 起草的回复存成内部备注，由人来发。
- 密钥以创建它的成员身份操作，时间线上显示为“这个人，通过 agent”。
- 只读密钥只能查看。任何密钥都可以在“Agent 与 API”里立即撤销。
- “标记为无关”被标成破坏性操作，客户端会先征求你的同意。

## FAQ

### 哪些 AI 客户端能用 Hearl？

支持 MCP 的客户端都可以：Claude Code、Cursor、Windsurf、VS Code 等直接连远程服务器；Claude Desktop 通过 hearl 命令行的 stdio 桥接。不支持 MCP 的 agent 可以用 REST API 或命令行。

### agent 能替我在 X 或 Reddit 上回复吗？

不能。Hearl 不会在任何地方发帖。agent 可以起草回复并存成内部备注，由同事审过后再发。

### 需要付费套餐吗？

不需要。API 密钥、MCP 服务器和命令行在所有套餐里都能用，包括免费版。

### agent 怎么登录？

用以 hl_ 开头的工作空间 API 密钥。在“Agent 与 API”里创建，选只读或读写，再交给客户端。MCP 客户端的 OAuth 登录在计划中。

---
Source: https://hearl.org/zh/agents