文档Docs
好友转交防护Friend handover safeguards
好友之间转交任务时，Agent J 自动限次数、防绕圈、限速、管时限；你也可以让某位好友的请求先等你批准。When friends hand tasks to each other, Agent J limits the number of hops, stops loops, caps the rate and times out stuck requests; you can also hold a friend's requests until you approve.
好友可以把任务交给你的 Agent J，你的 Agent 也能再转给别人；同一个主人的几台设备之间也是这样。为了不让任务绕圈、刷屏或一直卡着，Agent J 自动加了几道防护。平时你什么都不用做；请求被拦下或到期时，双方的对话里都会出现一句说明，手机也会收到提醒。好友功能怎么用，看 Agent 好友。
最多转交 4 次，不许绕回
每条请求都带着一个链路编号。转交超过 4 次就停下，你会看到「这条请求已转交超过 4 次，已停止。」；绕回发起它的那台电脑也会停下，提示是「这条转交绕回了原来的电脑，已停止。」。
你自己新说的一句话会重新开一条链。回报结果不算新任务，不会被当成又一次转交。
每位好友每分钟最多 30 条
同一位好友一分钟里发来超过 30 条，多出来的会被拦下，提示「这位好友发得太快，请等一分钟再试。」。策略组里原有的更严的限额照样生效。同一个主人的设备之间例外：不受策略组的两条消息最短间隔（比如「好友」组的 3 秒）和每分钟条数的限制，连着发也不会被拦，只按这里的每分钟 30 条防刷。
认领和过期
- 请求真正交给 Agent 开始处理，才算认领；还在排队的不算。
- 认领后 30 分钟没有回复，请求会被释放，提示「对方认领后一直没回复，已释放请求；可以重新派或取消。」。
- 一直没人认领的请求，24 小时后过期，提示「请求一直没人认领，已过期；可以重新派或取消。」。
- 到期后可以重新派或取消。系统不会自动重做，也不会因为到期就停掉正在跑的工作：已经开始的可能还在跑，重派前先确认一下，免得做两遍。
先压着等我批
在 Agent 好友 → 这位好友 → 详情 打开「先压着等我批」，默认是关的。
打开后，这位好友的新请求不会直接处理，而是先在你手机上弹一张卡，比如「要处理 老王 的请求吗？」，卡上有请求原文和一句「只批准此次转交。敏感动作仍要另外批准。」。点「交给主 Agent」，这一条才交给你的主 Agent 处理；点「拒绝」或者放着让它过期，都不会执行。
- 交过去的仍然算好友的请求，不是你本人说的话。
- 批准只管这一次转交。里面的敏感动作还要逐次批准，管理员命令也不能沿用十分钟免批。
- 请求太长、卡片显示不全的，会直接拒绝，免得你批了没看到的部分。
- 关掉开关，不会放行已经在等的卡。
- 同一个主人的设备也受这个开关管。
- 不打开时，普通好友照旧由隔离的分身接待，不进你的主 Agent。
调整这些数字
每分钟条数、认领时限和过期时限都可以让 Agent J 帮你改：每分钟 1 到 10000 条，两个时限 1 秒到 30 天。Agent J 用 agentj friends relay-policy 查看和修改，用 agentj friends cancel 取消一条你发出、还在等的请求。取消只改请求的状态，不会撤回已经做过的事，也不会停掉正在跑的工作。
A friend can hand a task to your Agent J, and your Agent can pass it on to someone else; the same goes between devices of the same owner. To stop tasks from going in circles, flooding you or getting stuck, Agent J adds a few safeguards on its own. Usually you do nothing. When a request is stopped or times out, both sides see a short note in their conversation and the phone gets a notification. For how friends work in general, see Agent friends.
At most 4 handovers, no loops
Every request carries a chain ID. After more than 4 handovers it stops, and you see "This request was handed on more than 4 times and was stopped." If it comes back to the computer that started it, it also stops: "This request came back to its starting computer and was stopped."
Anything new you say yourself starts a new chain. A reported result is not a new task and never counts as another handover.
At most 30 messages per friend per minute
If one friend sends more than 30 messages within a minute, the extra ones are stopped with "This friend is sending too quickly. Try again in a minute." Stricter limits in the friend's policy group still apply. Same owner devices are the exception: the policy group's shortest gap between two messages (3 seconds for Friends, for example) and its per-minute count do not apply, so messages sent back to back are not stopped; only this limit of 30 per minute guards against flooding.
Claiming and expiry
- A request is claimed only when the Agent actually starts on it; a request still waiting in line is not claimed.
- If there is no reply 30 minutes after it was claimed, the request is released: "No reply after the request was claimed. It is released; you can reassign or cancel."
- A request nobody claims expires after 24 hours: "Nobody claimed this request before it expired. You can reassign or cancel."
- After that you can reassign or cancel. Nothing is redone automatically, and work that is already running is never stopped because time ran out. It may still be running, so check before reassigning to avoid doing it twice.
Hold until I approve
Open Agent friends → the friend → Details and turn on "Hold until I approve". It is off by default.
With it on, new requests from that friend are not handled straight away. A card appears on your phone first, for example "Handle this request from Kai?", showing the request and the line "Approve this handover only. Sensitive actions still need separate approval." Tap "Send to main Agent" and only that request goes to your main Agent. Tap "Decline", or let it expire, and nothing runs.
- What goes through is still the friend's request, not something you said.
- Approval covers this one handover. Sensitive actions inside it still need their own approval, and administrator commands cannot reuse the ten-minute approval window.
- A request too long for the card to show in full is refused, so you never approve a part you did not see.
- Turning the switch off does not approve cards that are already waiting.
- Devices of the same owner follow this switch too.
- With the switch off, ordinary friends keep talking to the separate friend clone and never reach your main Agent.
Changing the numbers
Agent J can change the per-minute limit and both time limits for you: 1 to 10000 messages per minute, and 1 second to 30 days for the time limits. Agent J uses agentj friends relay-policy to read and change them, and agentj friends cancel to cancel a request you sent that is still waiting. Cancelling only changes the request's status; it does not undo anything already done or stop work that is running.