Goal
Make the Windows user-global agmsg environment usable and discoverable across Claude Desktop, Codex, Qwen Code, and future CLI agents.
Current evidence
- Shared agmsg scripts and PowerShell wrapper are installed under
C:\Users\orang\.agents\skills\agmsg.
- Claude ↔ Codex E2E succeeded on 2026-08-01 and 2026-08-04.
agmsg-e2e34 currently has claude-desktop, codex-tui, and qwen-tui.
- Claude → Qwen currently has a PING but no ACK.
- Claude monitor is configured but not running; Qwen and the current Codex project are
off.
- Claude global guidance still says agmsg is not a viable delegation path, which conflicts with the successful Claude ↔ Codex E2E.
- Qwen user settings contain both Standard and Token Plan DashScope endpoints, while the active model is Standard-side.
Ordered work
Acceptance criteria
- A fresh Claude session can discover
/agmsg, join the intended team, and spawn or address Qwen with an explicit stop condition.
- Claude monitor receives messages after the documented restart.
- Qwen uses the intended Token Plan model/endpoint and can execute one model turn.
- A live message sent from
claude-desktop is acknowledged by qwen-tui and the ACK is observable in Claude's inbox/history.
- Local instructions no longer contain contradictory claims that suppress the supported workflow.
Goal
Make the Windows user-global agmsg environment usable and discoverable across Claude Desktop, Codex, Qwen Code, and future CLI agents.
Current evidence
C:\Users\orang\.agents\skills\agmsg.agmsg-e2e34currently hasclaude-desktop,codex-tui, andqwen-tui.off.Ordered work
/agmsgusage and spawn guidance, including bounded boot prompts and the no-idle-wakeup limitation.turndelivery where appropriate and complete a live Claude Desktop → Qwen TUI → Claude Desktop E2E.Acceptance criteria
/agmsg, join the intended team, and spawn or address Qwen with an explicit stop condition.claude-desktopis acknowledged byqwen-tuiand the ACK is observable in Claude's inbox/history.