cross-agent-teams-mcp 0.7.0 → 0.7.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -41,7 +41,7 @@ npx mcpsmgr add jtianling/cross-agent-teams-mcp
41
41
  # 3. Start your coding agent as usual
42
42
  ```
43
43
 
44
- Note: only Claude Code gets push wake out of the box. Codex needs the `--remote` + launcher setup (see section 2 below) for pokes; without it, it has a mailbox but no wake. opencode / cursor / other agents only receive pokes when running inside a tmux pane. If push wake isn't wired up, ask the agent to check its inbox manually ("check my xats inbox").
44
+ Note: Claude Code gets push wake out of the box. Codex and opencode get real push wake too — each after a one-time launcher setup (see section 2 below): Codex over its `--remote` app-server transport, opencode over its HTTP `prompt_async` transport. cursor / other custom agents only receive pokes when running inside a tmux pane. If push wake isn't wired up for an agent, ask it to check its inbox manually ("check my xats inbox").
45
45
 
46
46
  Then talk to your agent in plain language:
47
47
 
@@ -218,6 +218,8 @@ More detail (auth headers, lower-level `register_agent` form): [docs/configs/cod
218
218
 
219
219
  opencode ships a first-class headless HTTP API (`POST /session/{id}/prompt_async`) that the daemon uses as a dedicated wake-up transport — no tmux pane injection required. The transport is activated by registering with `agent_type="opencode"` and a `base_url` pointing at the opencode process's HTTP server.
220
220
 
221
+ When another agent pokes this opencode, the daemon POSTs the wake hint to `prompt_async`, which **starts a fresh opencode agent turn** — the agent wakes on its own and reads its inbox with no manual prompt, the same first-class push-wake that Claude Code and Codex get (not the passive tmux paste that `custom` agents fall back to).
222
+
221
223
  Add a `free-xats-opencode` zsh function to `~/.zshrc` (mirrors the `free-xats-codex` pattern):
222
224
 
223
225
  ```zsh
package/README.zh-CN.md CHANGED
@@ -41,7 +41,7 @@ npx mcpsmgr add jtianling/cross-agent-teams-mcp
41
41
  # 3. 按平时的方式启动对应 coding agent
42
42
  ```
43
43
 
44
- 注意: 只有 Claude Code 默认就能收到 push 唤醒. Codex 需要 `--remote` + launcher 配置 (见下面 section 2) 才能被 poke; 没配的话只有邮箱, 不会自动醒. opencode / cursor 等其它 agent 只有跑在 tmux pane 里才能被 poke. 没接通 push 唤醒的情况下, agent 自己手动收信即可 (跟它说"查一下我的 xats inbox").
44
+ 注意: Claude Code 默认就能 push 唤醒. Codex opencode 也都有真正的 push 唤醒, 各自做一次性 launcher 配置即可 (见下面 section 2) Codex `--remote` app-server 通道, opencode HTTP `prompt_async` 通道. cursor / 其它 custom agent 只有跑在 tmux pane 里才能被 poke. 某个 agent 没接通 push 唤醒时, 让它手动查 inbox 即可 (跟它说"查一下我的 xats inbox").
45
45
 
46
46
  之后用平时跟 agent 对话的语言就能用了:
47
47
 
@@ -218,6 +218,8 @@ free-xats-codex() {
218
218
 
219
219
  opencode 自带一流的 headless HTTP API (`POST /session/{id}/prompt_async`), daemon 用它作为专用唤醒通道 — 不需要 tmux pane 注入. 通过 `agent_type="opencode"` 加 `base_url` (指向 opencode 进程的 HTTP 服务器) 注册即可激活.
220
220
 
221
+ 别的 agent poke 这个 opencode 时, daemon 把 wake hint POST 到 `prompt_async`, **拉起 opencode 一个新的 agent turn** — agent 自己醒来读 inbox, 不需要任何手动提示, 跟 Claude Code 和 Codex 一样是一等公民的 push 唤醒 (而不是 `custom` agent 回落的那种被动 tmux paste).
222
+
221
223
  把下面的 `free-xats-opencode` zsh 函数加到 `~/.zshrc` (镜像 `free-xats-codex` 的模式):
222
224
 
223
225
  ```zsh
package/dist/cli.js CHANGED
@@ -1908,7 +1908,7 @@ async function dispatchOpencodeServerPoke(input, deps = {}) {
1908
1908
  }
1909
1909
  const body = JSON.stringify({
1910
1910
  parts: [{ type: "text", text: input.content }],
1911
- noReply: true
1911
+ noReply: false
1912
1912
  });
1913
1913
  let response;
1914
1914
  try {